25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 42<br />

Troubleshooting and Error Messages<br />

Set the <strong>LSF</strong> binaries to be owned by root with the setuid bit set, or define<br />

<strong>LSF</strong>_AUTH=ident and set up an ident server on all hosts in the cluster. If the<br />

binaries are on an NFS-mounted file system, make sure that the file system is<br />

not mounted with the nosuid flag.<br />

userok: Forged username suspected from /:<br />

/<br />

The service request claimed to come from user claimed_user but ident<br />

authentication returned that the user was actually actual_user. The request<br />

was not serviced.<br />

userok: ruserok(,) failed<br />

<strong>LSF</strong>_USE_HOSTEQUIV is defined in the lsf.conf file, but host has not been<br />

set up as an equivalent host (see /etc/host.equiv), and user uid has not set<br />

up a .rhosts file.<br />

init_AcceptSock: RES service(res) not registered, exiting<br />

init_AcceptSock: res/tcp: unknown service, exiting<br />

initSock: LIM service not registered.<br />

initSock: Service lim/udp is unknown. Read <strong>LSF</strong> Guide for help<br />

get_ports: service not registered<br />

The <strong>LSF</strong> services are not registered. See “Registering Service Ports” on page 85<br />

for information about configuring <strong>LSF</strong> services.<br />

init_AcceptSock: Can’t bind daemon socket to port : error, exiting<br />

init_ServSock: Could not bind socket to port : error<br />

These error messages can occur if you try to start a second <strong>LSF</strong> daemon (for<br />

example, RES is already running, and you execute RES again). If this is the<br />

case, and you want to start the new daemon, kill the running daemon or use<br />

the lsadmin or badmin commands to shut down or restart the daemon.<br />

Configuration errors<br />

The messages listed in this section are caused by problems in the <strong>LSF</strong><br />

configuration files. General errors are listed first, and then errors from specific<br />

files.<br />

file(line): Section name expected after Begin; ignoring section<br />

file(line): Invalid section name name; ignoring section<br />

The keyword begin at the specified line is not followed by a section name, or<br />

is followed by an unrecognized section name.<br />

file(line): section section: Premature EOF<br />

The end of file was reached before reading the end section line for the<br />

named section.<br />

file(line): keyword line format error for section section; Ignore this section<br />

The first line of the section should contain a list of keywords. This error is<br />

printed when the keyword line is incorrect or contains an unrecognized<br />

keyword.<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong> 535

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!