LSF Logs

[upadhi]

hello All,

I have scheduled some SAS codes visa LSF and want to scan the same.

i want to know the format and structure of LSF logs. Can anyone please share sample LSF logs generated?

[rabindrakumar1]

Hi,

You can find the logs on the compute server where the agent is running. Please see the logs on this path
 in Linux sever

<server path>/ps_sas/pm/work/history*.*

[gwootton]

Are you asking about the logs generated by LSF / Process Manager or those generated by SAS when running SAS code via LSF/Process Manager?

Typically when scheduling SAS programs to run as jobs on LSF you are using Process Manager as the scheduler to submit a job to LSF that uses the SAS DATA Step Batch Server to actually run the SAS code. As such, the logs are located here.

Process Manager:
JS_TOP/log/

LSF:
LS_TOP/log/

SAS DATA Step Batch Server:
<sas-configuration-directory>/SASApp/BatchServer/Logs

The format for the Batch Server's SAS log is the same as if you were running in base SAS.

[upadhi]

hello Greg, 

I am talking about the logs generated by LSF (LS_TOP/log/)

the issue is we do not have any sample logs and client is taking time to give sanitized version of logs. For scanning the logs, we wanted to create a python script, hence asked if some one can help me with the format. 

So that i can start working on the script. 

Thanks!

[gwootton]

The log format varies depending on the log, here is an example line from each.

LSF:
==> mbatchd.log.<hostname> <==
May 8 16:45:44 2020 1363:1363 3 10.1 periodicCheck(): Unable to contact LIM: LIM is down; try later; quit master
==> res.log.<hostname> <==
Dec 19 16:25:12 2019 7377 3 10.1 term_handler: Received signal 15, exiting
==> sbatchd.log.<hostname> <==
Jan 17 12:12:18 2020 17964 3 10.1 acctMapTo: No valid user name found for job <21629>, userName <sasdemo>. getpwnam() failed:Bad user ID
==> mbschd.log.<hostname> <==
Dec 20 09:50:18 2019 6488:6488 3 10.1 SCH_FM_readPacket: readDecodeHdr_() failed, lserrno=2
==> lim.log.<hostname> <==
Dec 20 10:04:55 2019 1070 4 3.4.0 initNewMaster: This is now the master host.

EGO:
==> pem.log.<hostname> <==
2019-12-19 16:27:02.000 EST WARN [5349:140300655433536] System daemon PEM is up on host <grid.demo.sas.com> in cluster <sas_cluster>

==> vemkd.log.<hostname> <==
2020-05-11 09:25:34.000 EDT WARN [5319:140092457252672] initparams: EGO_TOPOLOGY_PLUGIN is not defined; will load default topology plug-in (topology_ego_default).