Troubleshooting
Problem
You are sure that you have sourced the correct LSF environment, and this job was executed in the cluster, but when searching for the job using "bhist -n 0
Symptom
For example:
$ . $LSF_TOP/conf/profile.lsf
$ bhist -n 0 29694722
No matching job found
Cause
By default, the "-n 0" option of "bhist" command only searches up to a maximum of 100 lsb.events* files, i.e. lsb.events.[1-99] and lsb.events. If the job ID of interest is located inside lsb.events.100 and above, the "bhist" command with "-n 0" option would not be able to find it.
Resolving The Problem
In order to search for a job which is not inside the first 100 lsb.events* file, you can customize the "-n" option of "bhist" command to search in more than 100 lsb.events* files. For example:
$ bhist -n 150 29694722
No matching job found
$ bhist -n 200 29694722
JOBID USER JOB_NAME PEND PSUSP RUN USUSP SSUSP UNKWN TOTAL
29694722 user1 sleepjob 22420 0 368 0 0 0 22788
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
isg3T1024071