Troubleshooting Topics

This section presents a troubleshooting guide for the license manager. Use the topic questions as guidelines. For example, for installation problems, begin at topic 1 and follow the directions in topic 2.

No

You can find the setup script in your Builder Xcessory system directory 1 . Consult the BX PRO Installation Notes and continue to "Did you receive a full feature license key from ICS?" . We recommend that you run this script as root. Running the setup file creates a license.dat file. When you examine the license.dat file, you will notice a SERVER line.

The DAEMON ICSBX should contain a pathname to the location of the ICSBX vendor daemon. This is usually {BX}/bin/ICSBX . On Solaris 2, it is {INSTALL}/ICS/bin/ICSBX . The SERVER lines contain the hostnames and hostids (and port numbers) on which you have to run the license manager software in order for you to be able to run Builder Xcessory.

Topic 3

"Did you run the addbxkey.lm script and install the full feature BX activation key?"

Yes

Check that the license .dat file contains the new line:


FEATURE BuilderXcessory ICSBX


	3.000 01-jan-00 numberoflicenses


	youractivationkey "ICS Builder


	Xcessory"

Continue to "Did you start the license manager daemon?" .

No

Go to the {BX} directory and run the addbxkey .lm shell script. Consult the Builder Xcessory PRO Installation Notes . We recommend running this script as root. Continue to Topic 4 .

Topic 4

"Did you start the license manager daemon?"

Yes

You can check and see if the lmgrd is running by running the lmstat command found in {LM}/bin/lmstat . If lmgrd is up and ICSBX is up continue to Topic 5 . If lmgrd or ICSBX is not up, then refer back to Topic 1 and check your system.

No

Do a ps command and make sure no lmgrd or ICSBX processes are running. If you see an lmgrd process running, use the {LM}/bin/lmdown command to stop it. If the lmdown command fails for any reason you may kill lmgrd with a -15 signal (signal 15 stands for sigterm and will cause lmgrd to shutdown gracefully and cleanly). Remove the log file for the current lmgrd session. If you have the license.dat file in /usr/local/flexlm/licenses then go to {BX}/bin and type:


/lmgrd > /tmp/lmgrd

log

If you have the license .dat file in another location set the LM_LICENSE_FILE environment variable (consult the Builder Xcessory PRO Installation Notes ) and then start lmgrd as described. If you have the LM_LICENSE_FILE environment variable already set (do a printenv command) make sure it is correct (on a single line):


LM_LICENSE_FILE =


	/pathname_to_license.dat


	/license.dat)

Note: You must run


lmgrd

on each machine specified on each SERVER line in the


license.dat

file. There can only be one


lmgrd

and


ICSBX

process running on each machine using the same


license.dat

file and TCP/IP port. Continue to "Examine the contents of the log file." .

Topic 6

"Is there an entry in the log file that says ICSBX cannot establish lock /usr/tmp/lockICSBX?"

Yes

Go to /usr/tmp and remove lockICSBX . Using ps , check for any lmgrd processes running, use the {LM}/bin/lmdown command to stop them. If the lmdown command fails for any reason you may kill lmgrd with a -15 signal (signal 15 stands for sigterm and will cause lmgrd to shutdown gracefully and cleanly). Refer to Topic 2 , No .

No

Continue to Topic 7 .

Topic 7

"Is there an entry in the log file that says port address already in use?"

Yes

Edit the port number in the license .dat file for the server on which you are trying to run. The default is 1700. You can change this value to be any port number you are not using. Consult the /etc/services file or the equivalent NIS services file to find the list of ports in use. Remember that port numbers less than 1024 are privileged port numbers and thus not usable for the license manager since all users must be able to access the port. After you edit the license.dat file, save it. Do a ps , check for any lmgrd processes running, use the {LM}/bin/lmdown command to stop them. If the lmdown command fails for any reason you may kill lmgrd with a -15 signal (signal 15 stands for sigterm and will cause lmgrd to shutdown gracefully and cleanly). Remove /tmp/lmgrd.log . Refer to topic Topic 2 , No .

No

Continue to Topic 8 .

Topic 8

"Is there an entry in the log file that says bad code for BuilderXcessory?"

Yes

Basically the key you have installed is incorrect. Using ps , check for any lmgrd processes running and kill them with a -15 signal (kill -15 lmgrdpid ). Go to /tmp and remove lmgrd.log . Go to the license.dat file and compare the key on your fax to the key in the license.dat file.

Verify also that the SERVER information in license.dat matches the information your fax.

You can manually edit the license.dat file to correct the activation key. Refer back to No . If the key on the fax is identical to the one in your license .dat file and you continually get this message in your log file please call ICS at 617.621.0060 and ask for ICS Technical Support.

No

Continue to Topic 9 .

Topic 9

"Is there an entry in the log file that says no licenses found?"

Yes

If you do not have license.dat in /usr/local/flexlm/licenses you must make sure the LM_LICENSE_FILE environment variable is set to {pathname}/license.dat . After you set the environment variable correctly (check this by doing a printenv and looking for the LM_LICENSE_FILE variable), do a ps , check for any lmgrd processes running, use the {LM}/bin/lmdown command to stop them. If the lmdown command fails for any reason you may kill lmgrd with a -15 signal (signal 15 stands for sigterm and will cause lmgrd to shutdown gracefully and cleanly). Refer to Topic 2 , No .

No

Continue to Topic 10 .

Topic 10

"Is there an entry in the log file that says not a valid server host?"

Yes

Do a ps , check for any lmgrd processes running and kill them with a -15 signal (kill -15 lmgrdpid ). Check the SERVER lines in the license .dat file. Each server should be spelled correctly and each should have the correct lmhostid for the appropriate SERVER hostname. You may want to compare SERVER lines listed on your fax with what is actually in your license.dat file 2 . Also make sure that the hostname is in the /etc/hosts file (or NIS equivalent) and that the hostname is spelled the same in both the hosts file and license.dat file. You may want to check the IP address of the hostname and make sure the value is valid. After you verify all of this, refer to No .

No

Continue to Topic 11 .

Topic 11

"Is there an entry in the log file that says cannot find ICSBX?"

Yes

Do a ps , check for any lmgrd processes running and kill them with a -15 signal (kill -15 lmgrdpid ). Remove lmgrd.log . Go to your license.dat and examine the DAEMON ICSBX line. Go to where ICSBX exists (identified on the DAEMON line). In the same directory as ICSBX there should be a link called lmgrd . This lmgrd link should point to {BX}/bin/lmgrd . If the DAEMON line is wrong, correct it. Refer to No .

No

Continue to Topic 12 .

Topic 12

"Is there an entry in the log file that says adding full feature license for Builder Xcessory?"

Yes

It seems that you are ready to run Builder Xcessory. Go to {BX}/bin and type:


./bx &

A process id will be returned. If the Palette window appears with the Motif widget set inside and there are no error messages in the Browser's message window then everything is fine. If a dialog box saying Can't Run Demo or Full Feature BX appears, refer to "When starting BX does a dialog appear with the message: Cannot Run Demo Or Full Feature BX?" . If a dialog box saying No Full Feature Licenses Found - Do you wish to continue in Demo mode? appears, refer to Topic 13 . If a dialog reading "All Licenses In Use (with a detailed description of who is using which Builder Xcessory license at which workstation " appears, then refer to Topic 13 . If no BX windows come up when you start the application, then refer to Topic 16 . If when you start BX you receive the error message Cannot open display , refer to Topic 17 . If you have started BX and the Browser messages window displays "Cannot find app-defaults file ", then refer to Topic 18 .

No

You may have installed your activation key improperly. Refer to Topic 2 and review diagnostics.

Topic 13

"When starting BX does a dialog appear with the message: Cannot Run Demo Or Full Feature BX?"

If you are running Builder Xcessory and lmgrd on the same machine, this means the license manager software is not running. Check the lmgrd.log file for any errors and go to the appropriate topic heading in this document. If any lmgrd processes are running, use the {LM}/bin/lmdown command to stop them. If the lmdown command fails for any reason you may kill lmgrd with a -15 signal (signal 15 stands for sigterm and will cause lmgrd to shutdown gracefully and cleanly). If there are no familiar errors, refer to No and try restarting the license manager daemon. If you still get this error when starting BX, refer to "I'm still having trouble getting the software to work." .

If you are trying to run Builder Xcessory off a machine which is not one of the workstations listed on the SERVER lines in the license.dat file, then the problem is likely that you cannot access the license.dat file from the workstation on which you are trying to run BX. Builder Xcessory, therefore, cannot find a license server. Either NFS mount the directory where the license.dat file exists on the workstation trying to run BX or copy the license.dat file to a directory local to the workstation trying to run Builder Xcessory and set the LM_LICENSE_FILE environment variable on that workstation to {pathname}/license.dat . Then refer to Yes .

Topic 14

"When starting BX, does a dialog appear with the message: No Full Feature Licenses Found - Do You Wish To Continue In Demo Mode?"

The license software is running. If you do not have a full feature license to run Builder Xcessory you will always get this message and you will only be able to run the product in demo mode. If you wish to purchase a key after running the demo please contact your ICS sales representative at 617.621.0060 to purchase a full feature activation key.

If you have a full feature license, make sure you can get to the license.dat file from your workstation. If you cannot get to the license.dat file, follow the second part of Topic 13 or else continue on in this topic. If you have a full feature license, verify that the contents of the feature line in your license.dat file are the same as the contents of the fax. You will see a section on the fax saying this line should now appear in your license.dat file. Try running {BX}/bin/lmreread . When you run lmreread it should tell you that the nodes on the SERVER lines in the license.dat file were informed. If this is true, than refer to topic 12.1 and follow those directions. If lmreread tells you that it cannot connect to the license server, then the license manager daemon software is not running. Do a ps and kill any lmgrd processes running, use the {LM}/bin/lmdown command to stop it. If the lmdown command fails for any reason you may kill lmgrd with a -15 signal (signal 15 stands for sigterm and will cause lmgrd to shutdown gracefully and cleanly). Then refer to No .

Topic 16

"I've read my license.dat file and I see the line which tells me a full feature Builder Xcessory license was added. I've started Builder Xcessory but no windows come up and no messages appear. What am I doing wrong?"

If your workstation is a stand-alone and is not connected to a network you might try setting the hostname on the SERVER line in the license.dat file to be localhost and then save the license.dat file. After changing this in the license.dat file do a ps command and if any lmgrd processes are running, use the {LM}/bin/lmdown command to stop them. If the lmdown command fails for any reason you may kill lmgrd with a -15 signal (signal 15 stands for sigterm and will cause lmgrd to shutdown gracefully and cleanly). Refer to No and work forwards.

If you repeatedly get the same results after trying the above, refer to Topic 22 .

Topic 18

"The Palette comes up but Builder Xcessory can't find my app-defaults file."

If you are running under Open Windows, copy the Builder Xcessory app-defaults file which is found in the directory {BX}/BuilderXcessory.<hostname> into the file /usr/openwin/lib/app-defaults/BuilderXcessory .

If you are running under X, copy the Builder Xcessory app-defaults file found in {BX}/BuilderXcessory to /usr/lib/X11/app-defaults/BuilderXcessory .

Restart the Builder Xcessory application. Refer to Yes .

Topic 21

"I have multiple license.dat files or I'm running two programs that use lmgrd. What do I do?"

You may combine the license .dat files into one license file. Append the contents of each license .dat file into one master file called license.dat . Make sure all of the licenses in the file use the GLOBEtrotter Software Flexible License Manager. Make sure you run the newest version of the Flexible License Manager. Version 3.0 is shipped with the Builder Xcessory.

1. On Solaris 2 systems, there is no setup program. The equivalent steps are taken when you install the flexlm package.

2. The importance here lies in the fact that the lmhostids on the fax have to be identical to the lmhostids for each appropriate server in the license.dat file. The spelling of the server in the fax is not important in the key generation but the lmhostids are critical.

Troubleshooting Topics

Topic 1

"Did you run the setup script?"

Yes

No

Topic 2

Yes

No