Configuration Problem Messages
The following table lists configuration problem messages found in FlexNet Publisher.
|
Message |
Description |
|
host: Not a valid server host, exiting |
This daemon was run on an invalid host name. |
|
host: Wrong hostid, exiting |
The hostid is wrong for host. |
|
BAD CODE for feature |
The specified feature name has a bad license key or signature. It was probably typed in wrong, or modified by the end user. |
|
CANNOT OPEN options file |
The options file specified in the license file could not be opened. |
|
Couldn’t find a master |
The daemons could not agree on a master. |
|
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 |
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 vendor |
The license file does not contain a DAEMON or VENDOR line for vendor. |
|
No DAEMON lines, exiting |
The license daemon logs this message if there are no DAEMON or VENDOR lines in the license file. Because there are no vendor daemons to start, there is nothing for the license daemon to do. |
|
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: host |
The host name specified on a SERVER line in the license file does not exist in the network database (probably /etc/hosts). |