Skip to content. Skip to navigation

ICTP Portal

Sections
You are here: Home Manuals on-line PGI Compiler flexuser chap11.htm
Personal tools
Document Actions

chap11.htm

Table of Contents * Index * Previous Chapter * Next Chapter

FLEXlm End User Manual: Appendix E The Debug Log File

Appendix E The Debug Log File

The daemons all generate debug log files in the following format.

hh:mm (DAEMON NAME) message

hh:mm
Time that the message was logged.
DAEMON NAME
Either lmgrd or the vendor DAEMON name. In the case where a single copy of the daemon cannot handle all of the requested licenses, an optional `_' followed by a number indicates that this message comes from a forked daemon.
message
The text of the message.

The debug log files can be used to:

  • Diagnose configuration problems.
  • Diagnose daemon software errors.

The debug log file should not be used for usage reporting.

E.1 Informational Messages

Connected to node

This daemon is connected to its peer on node `node.<p> <p> CONNECTED, master is name<p> <p> The license daemons log this message when a quorum is up and everyone has selected a master.<p> <p> DENIED: N feature to user<p> <p> `user was denied access to `N' licenses of `feature'.

EXITING DUE TO SIGNAL nnn

EXITING with code nnn

All daemons list the reason that the daemon has exited.

EXPIRED: feature

`feature' has passed its expiration date.

IN: feature by user (N licenses)

`user' has checked back in `N' licenses of `feature'.

License Manager server started

The license daemon was started.

Lost connection to host

A daemon can no longer communicate with its peer on node `host', which can cause the clients to have to reconnect, or cause the number of daemons to go below the minimum number, in which case clients may start exiting. If the license daemons lose the connection to the master, they will kill all the vendor daemons; vendor daemons will shut themselves down.

Lost quorum

The daemon lost quorum, so will process only connection requests from other deamons.

MULTIPLE xxx servers running.

Please kill, and restart license daemon

The license daemon has detected that multiple licenses for vendor daemon `xxx' are running. The user should kill all `xxx' daemon processes and re-start the license daemon.

OUT: feature by user (N licenses)

`user' has checked out `N' licenses of `feature'.

RESERVE feature for HOST name

RESERVE feature for USER name

A license of `feature' is reserved for either user `name' or host `name'.

REStarted xxx (internet port nnn)

Vendor daemon `xxx' was restarted at internet port `nnn'.

Retrying socket bind (address in use)

The license servers try to bind their sockets for approximately 6 minutes if they detect `address in use' errors.

Selected (EXISTING) master node.

This license daemon has selected an existing master (node) as the master.

SERVER shutdown requested.

A daemon was requested to shut down via a user-generated kill command.

[NEW] Server started for: feature-list

A new server was started for the features listed.

Shutting down xxx

The license daemon is shutting down the vendor daemon xxx.

SIGCHLD received. Killing child servers.

A vendor daemon logs this message when a shutdown was requested by the license daemon.

Started name

The license daemon logs this message whenever it starts a new vendor daemon.

Trying connection to node

The daemon is attempting a connection to `node'.

E.2 Configuration Problem Messages

hostname: Not a valid server host, exiting

This daemon was run on an invalid hostname.

hostname: Wrong hostid, exiting

The hostid is wrong for `hostname.'

BAD CODE for feature-name

The specified feature name has a bad license key. It was probably typed in wrong, or modified by the end-user.

CANNOT OPEN options file `file'

The options file specified in the license file could not be opened.

license daemon: lost all connections

This message is logged when all the connections to a server are lost, which often indicates a network problem.

lost lock, exiting

Error closing lock file

Unable to re-open lock file

The vendor daemon has a problem with its lock file, usually because of an attempt to run more than one copy of the daemon on a single node. Locate the other daemon that is running via a ps command, and kill it with kill -9.

NO DAEMON line for daemon

The license file does not contain a `DAEMON' line for `daemon.<p> <p> No `license service found

The TCP `license' service did not exist in /etc/services.

No features to serve!

A vendor daemon found no features to serve. This could be caused by a corrupted or incorrectly entered license file.

UNSUPPORTED FEATURE request: feature by user

The `user' has requested a feature that this vendor daemon does not support. This can happen for a number of reasons: the license file is bad, the feature has expired, or the daemon is accessing the wrong license file.

Unknown host: hostname

The hostname specified on a `SERVER' line in the license file does not exist in the network database.

NO DAEMON lines, exiting

The license daemon logs this message if there are no DAEMON lines in the license file. Since there are no vendor daemons to start, there is nothing to do.

NO DAEMON line for name

A vendor daemon logs this error if it cannot find its own DAEMON name in the license file.

E.3 Daemon Software Error Messages

No internet port number specified

A vendor daemon was started without an internet port.

read: error message

An error in a `read' system call was detected.

select: message

An error in a select system call was detected. This is usually a sign of a system networking failure.

Server exiting

The server is exiting. This is normally due to an error.

Table of Contents * Index * Previous Chapter * Next Chapter

Weather
No information available
 

Powered by Plone This site conforms to the following standards: