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.

System Event Log<br />

CAUTION<br />

Chapter 41<br />

Error and Event Logging<br />

The <strong>LSF</strong> daemons keep an event log in the lsb.events file. The mbatchd<br />

daemon uses this information to recover from server failures, host reboots, and<br />

mbatchd restarts. The lsb.events file is also used by the bhist command to<br />

display detailed information about the execution history of batch jobs, and by<br />

the badmin command to display the operational history of hosts, queues, and<br />

daemons.<br />

By default, mbatchd automatically backs up and rewrites the lsb.events file<br />

after every 1000 batch job completions. This value is controlled by the<br />

MAX_JOB_NUM parameter in the lsb.params file. The old lsb.events file<br />

is moved to lsb.events.1, and each old lsb.events.n file is moved to<br />

lsb.events.n+1. <strong>LSF</strong> never deletes these files. If disk storage is a concern,<br />

the <strong>LSF</strong> administrator should arrange to archive or remove old lsb.events.n<br />

files periodically.<br />

Do not remove or modify the current lsb.events file. Removing or<br />

modifying the lsb.events file could cause batch jobs to be lost.<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong> 523

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

Saved successfully!

Ooh no, something went wrong!