LSF Version 7.3 - Platform LSF Configuration Reference

the name of the fields being read when parsing failed.
Examples
Errors like the following are logged to the mbatchd log file when mbatchd fails to read
lsb.events:
Dec 28 14:25:30 2007 9861 3 7.02 init_log: Reading event file </home/user1/
LSF7/work/LSF7/logdir/lsb.events>: Bad event format at line 15: JOB_NEW
1198869866 offset[28:3]: First 10 fields: jobId userId options numProcessors
subTime beginTime termTime sigValue chkpntPeriod restartPid
Dec 28 14:25:30 2007 9861 3 7.02 init_log: Reading event file </home/user1/
LSF7/work/LSF7/logdir/lsb.events>: Bad event format at line 16: bad
eventVersion
Dec 28 14:25:30 2007 9861 3 7.02 switch_log(): reading event file </home/
user1/LSF7/work/LSF7/logdir/lsb.events>: Bad event format at line 15: JOB_NEW
1198869866
offset[28:2]: First 10 fields: jobId userId options numProcessors subTime
beginTime termTime sigValue chkpntPeriod restartPid
Dec 28 14:25:30 2007 9861 3 7.02 switch_log(): reading event file </home/
user1/LSF7/work/LSF7/logdir/lsb.events>: Bad event format at line 16: bad
eventVersion
Batch event format errors like the following are displayed by LSF batch commands:
bhist -l 309
Dec 28 16:04:53 2007 8146 3 7.02 File /home/user1/LSF7/work/LSF7/logdir/
lsb.events: Bad event format at line 20: JOB_EXECUTE 1198888660 offset[48:1]:
execCwd
badmin mbdhist
File /home/user1/LSF7/work/LSF7/logdir/lsb.events: Bad event format at line
19: JOB_EXECUTE 1198888660 offset[48:1]: execCwd
File /home/user1/LSF7/work/LSF7/logdir/lsb.events: Bad event format at line
20: bad eventVersion
EGO command messages
You cannot run the egosh command because the administrator has chosen
not to enable EGO in lsf.conf: LSF_ENABLE_EGO=N.
If EGO is disabled, the egosh command cannot find ego.conf or cannot contact vemkd (not
started).
Troubleshooting and error messages
608 Platform LSF Configuration Reference