25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 42<br />

Troubleshooting and Error Messages<br />

start_job: Job : readLogJobInfo failed: error<br />

readLogJobInfo: Job : can’t read() size size: error<br />

initLog: mkdir() failed: error<br />

: fopen( failed: error<br />

getElogLock: Can’t open existing lock file : error<br />

getElogLock: Error in opening lock file : error<br />

releaseElogLock: unlink() failed: error<br />

touchElogLock: Failed to open lock file : error<br />

touchElogLock: close failed: error<br />

mbatchd failed to create, remove, read, or write the log directory or a file in<br />

the log directory, for the reason given in error. Check that <strong>LSF</strong> administrator<br />

has read, write, and execute permissions on the logdir directory.<br />

If logdir is on AFS, check that the instructions in the document “Installing <strong>LSF</strong><br />

on AFS” on the <strong>Platform</strong> Web site have been followed. Use the fs ls<br />

command to verify that the <strong>LSF</strong> administrator owns logdir and that the<br />

directory has the correct acl.<br />

replay_newjob: File at line : Queue not found, saving<br />

to queue <br />

replay_switchjob: File at line : Destination queue not<br />

found, switching to queue <br />

When mbatchd was reconfigured, jobs were found in queue but that queue is<br />

no longer in the configuration.<br />

replay_startjob: JobId : exec host not found, saving to host<br />

<br />

When mbatchd was reconfigured, the event log contained jobs dispatched to<br />

host, but that host is no longer configured to be used by <strong>LSF</strong>.<br />

do_restartReq: Failed to get hData of host /<br />

mbatchd received a request from sbatchd on host host_name, but that host<br />

is not known to mbatchd. Either the configuration file has been changed but<br />

mbatchd has not been reconfigured to pick up the new configuration, or<br />

host_name is a client host but the sbatchd daemon is running on that host.<br />

Run the following command to reconfigure the mbatchd or kill the sbatchd<br />

daemon on host_name.<br />

% badmin reconfig<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong> 539

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

Saved successfully!

Ooh no, something went wrong!