Specific Problems

This section describes the following problems.

• You Cannot Find the License Debug Log File

• Daemons Are Not Running

• The Hardware or Software Crashes

• An Application Client Cannot Run the Software

• Licenses Not Checked-in after Using lmremove

Daemons Are Not Running

The most common installation problems involve starting the FlexNet license daemon (lmgrd) and the Cadence daemon (cdslmd).

• Use lmstat to verify the daemon status.

• Check the /usr/tmp/license.log file.

• license manager: Not a valid server host, exiting.

• <time>(cdslmd) Wrong hostid, exiting.
  
  
• If you just installed the Cadence products, verify that the previous user or system administrator configured the Cadence licensing software environment with an editor.

• Verify that a symbolic (soft) link exists from install_dir /tools to tools. xxx , where tools. xxx is the platform-specific directory listed below.

• If the link does not exist, see Creating the Tools Link for information on creating the tools link.

• Verify that the host ID given by the lmhostid utility matches the number of a license server listed in the license file.
  If the host ID of the system running the license daemon does not match a SERVER line in the license file, the following error message appears in /usr/tmp/license.log:

invalid host

• Verify that /etc/rc.lic uses the correct license file.
• If the license server rebooted, verify that the file listed below executes /etc/rc.lic so that the daemons start automatically when the system reboots.

You Cannot Find the License Debug Log File

The debug log file records all licensing activity unless the messages are restricted by the options file. In fault-tolerant licensing, the debug log file is on the master server.

The license.log file does not exist under these circumstances.

• The command used to start the license daemons did not specify a log file.
  By default, the license daemons write to a debug log file,
  /usr/tmp/license.log.

• If you started the license daemons using the lmgrd command on the command line, you have a debug log file only if you direct the output to a file.

• If you started the license daemons using /etc/rc.lic, the file could specify a log file different from the default location.

• /etc/rc.lic  does not exist, or is not executable.
  The /etc/rc.lic startup script should start the daemons and specify the debug log file.

• Verify that /etc/rc.lic exists on the license server.
  ls -l /etc/rc.lic

• If it does not exist, create /etc/rc.lic with a text editor.

• If the /etc/rc.lic file is not executable, log in as root and use the chmod command to change the permissions.

• Use lmstat to verify that the lmgrd and cdslmd daemons are running on the license server.
  ./lmstat -a -c license_file
• If the license daemons are not running, verify correct installation of the daemons. List the contents of the install_dir /tools/bin directory on the license server.
  ls -l install_dir/ tools/bin

If you cannot find the license daemons, reinstall them (Lic+Config_+Utils Release ) using Cadence installation software.

• Check that the lmgrd and cdslmd daemons exist and are executable.
  ls -l install_dir /tools/bin
  
  If the daemons are not executable, change their permissions to 755.
  chmod 755 lmgrd cdslmd

• Messages sometimes do not appear in license.log for several minutes. If you cannot locate the license.log file, wait several minutes and try again.

• If the message indicates a socket bind problem, try again.

• The license server rebooted.
  Typically, the computer deletes files in /tmp when it reboots. You can do one of two things to prevent this from happening in the future.
  
  Modify the /etc/rc.lic file to place the debug log file, license.log, in /usr/tmp or another location.

The Hardware or Software Crashes

The Cadence applications become unavailable when

• The license servers become unavailable (through a crash or an intentional shut down)

• The application crashes

• The hardware crashes

• The network fails and the application disconnects from the license daemon

If the application crashes, the license daemons usually return the license to the pool of available licenses. However, if the application does not return the license to the pool, you can use one of the following lmremove  commands to return the license to the pool.

lmremove [ -c license_file ] feature user host display

lmremove [ -c license_file ] -h feature host port handle

Note: If several license servers are in the license file path and the license daemon crashes or the network fails, the feature attempts to reconnect to another license daemon.

An Application Client Cannot Run the Software

If an application client cannot run the Cadence product, follow these steps.

• Verify TCP/IP by typing the command below.

Note: Do not use ping. It does not adequately ensure that the client can reach the license server.

If you are not using .rhosts and you receive a prompt for a password on hostname , the network configuration is correct.

Type Control-d to exit. If the network configuration is not correct, see your operating system documentation.

• If you are using a clients file, follow these steps.

• Verify that the client's host name is the license server's clients file.
  You do not need to add the host name if the clients file contains an asterisk (*) because it indicates that all clients can access the license file.

• Verify that the Cadence product can access the license file as it appears in the clients file on each license server.

• If you are not using a clients file, verify how the application finds the license file. (CDS_LIC_FILE, LM_LICENSE_FILE)

• If you are trying to run Cadence software in the background (you start it with an ampersand, &), verify that the user's workstation allows background jobs to write to the terminal by typing stty.
  If you see tostop without a dash, background programs cannot write to the terminal. The programs hang. To let background programs write to the terminal, type stty - tostop. For more information, see Letting Users Access Cadence Products.

• Occasionally, you are not able to start another instance of an application if its FEATURE line in the license file indicates it is a UHD license. The basis of UHD licensing is the combination of the user, host, and the X display.
  This can happen if you set your DISPLAY variable in your ~/.cshrc and then manually set it again later. Normally, you do this whenever you use a remote computer and direct the display back to your local workstation.
  
  If the two DISPLAYs do not match exactly, the software considers them to be two different users.
  
  To correct this, use one of these methods.

• Remove the setting of the DISPLAY variable from your ~/.cshrc file and source the file. When the X server initially starts, it sets the variable for you.

• Move the setting to a section of your .cshrc file that is only run during interactive sessions. For more information on this, consult your operating system and X Window System documentation.

Licenses Not Checked-in after Using lmremove

Using lmremove does not check the licenses in, so licenses do not return to the license pool for others to use.

• Use lmremove -h to specify the FEATURE's handle, as returned by lmstat.
  lmremove -h feature license_server port handle

• Release the licenses by shutting the daemons down and restarting them.