Platform LSF Reference Version 6.2

Troubleshooting and Error Messages
Platform LSF Reference
647
userok: Forged username suspected from <host>/<port>:
<claimed_user>/<actual_user>
The service request claimed to come from user claimed_user but ident authentication
returned that the user was actually actual_user. The request was not serviced.
userok: ruserok(<host>,<uid>) failed
LSF_USE_HOSTEQUIV=Y is defined in the lsf.conf file, but host has not been set
up as an equivalent host (see
/etc/host.equiv), and user uid has not set up a
.rhosts file.
init_AcceptSock: RES service(res) not registered, exiting
init_AcceptSock: res/tcp: unknown service, exiting
initSock: LIM service not registered.
initSock: Service lim/udp is unknown. Read LSF Guide for help
get_ports: <serv> service not registered
The LSF services are not registered. See Administering Platform LSF for information
about configuring LSF services.
init_AcceptSock: Can’t bind daemon socket to port <port>: error, exiting
init_ServSock: Could not bind socket to port <port>: error
These error messages can occur if you try to start a second LSF daemon (for example,
RES is already running, and you execute RES again). If this is the case, and you want to
start the new daemon, kill the running daemon or use the
lsadmin or badmin
commands to shut down or restart the daemon.
Configuration errors
The messages listed in this section are caused by problems in the LSF configuration files.
General errors are listed first, and then errors from specific files.
file(line): Section name expected after Begin; ignoring section
file(line): Invalid section name name; ignoring section
The keyword begin at the specified line is not followed by a section name, or is
followed by an unrecognized section name.
file(line): section section: Premature EOF
The end of file was reached before reading the end section line for the named
section.
file(line): keyword line format error for section section; Ignore this section
The first line of the section should contain a list of keywords. This error is printed when
the keyword line is incorrect or contains an unrecognized keyword.
file(line): values do not match keys for section section; Ignoring line
The number of fields on a line in a configuration section does not match the number of
keywords. This may be caused by not putting
() in a column to represent the default
value.
file: HostModel section missing or invalid
file: Resource section missing or invalid
file: HostType section missing or invalid