LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 207
Managing LSF on Platform EGO
◆ For troubleshooting purposes, set your log level to LOG_DEBUG. Because of
the quantity of messages you will receive when subscribed to this log level,
change the level back to LOG_WARNING as soon as you are finished
troubleshooting.
TIP: If your log files are too long, you can always rename them for archive purposes. New, fresh log
files will then be created and will log all new events.
How often should I
maintain log files?
The growth rate of the log files is dependent on the log level and the complexity of
your cluster. If you have a large cluster, daily log file maintenance may be required.
We recommend using a log file rotation utility to do unattended maintenance of
your log files. Failure to do timely maintenance could result in a full file system
which hinders system performance and operation.
Troubleshoot using multiple EGO log files
EGO log file
locations and
content
If a service does not start as expected, open the appropriate service log file and
review the run-time information contained within it to discover the problem. Look
for relevant entries such as insufficient disk space, lack of memory, or network
problems that result in unavailable hosts.
Log file Default location What it contains
catalina.out Linux: LSF_LOGDIR/gui/catalina.out
Windows: LSF_LOGDIR\gui\catalina.out
Logs system errors and
debug information from
Tomcat web server startup.
esc.log
Linux:
LSF_LOGDIR/ego/cluster_name/eservice/esc/l
og/esc.log.hostname
Windows: LSF_LOGDIR\ego\cluster_name\
eservice\esc\log\esc.log.hostname
Logs service failures and
service instance restarts
based on availability plans.
Errors surrounding Platform
Management Console
startup are logged here.
named.log
Linux:
LSF_LOGDIR/ego/cluster_name/eservice/esd/c
onf/named/namedb/named.log.hostname
Windows: LSF_LOGDIR\ego\cluster_name\
eservice\esd\conf\named\namedb\
named.log.hostname
Logs information gathered
during the updating and
querying of service instance
location; logged by BIND, a
DNS server.
pem.log Linux:
LSF_LOGDIR/pem.log.hostname
Windows: LSF_LOGDIR\pem.log.hostname
Logs remote operations
(start, stop, control activities,
failures). Logs tracked results
for resource utilization of all
processes associated with
the host, and information for
accounting or chargeback.