IBM Spectrum LSF Application Center log files and log levels
Location of the IBM Spectrum LSF Application Center, configuration levels, and how to change them.
Use the IBM Spectrum LSF Application Center log file to troubleshoot errors that occur in the graphical user interface. Errors from other IBM Spectrum LSF family products may also be written to the log file.
Log file locations
- $GUI_CONFDIR/../logs/host_name/messages.log
- $GUI_TOP/work
- $GUI_TOP/logs
- $PERF_TOP/work
- $PERF_TOP/log
Tip: The
IBM Spectrum LSF Application Center log and event files contain personal information (for example, UNIX usernames and email
addresses). OS-level access control is one level of protecting this persona data; for further
protection, you can use encryption software tools to encrypt the disk partition or volume used to
store the log and events files. IBM Spectrum LSF Application Center log and event files are located at GUI_TOP/work,
GUI_TOP/logs, PERF_TOP/work, and
PERF_TOP/log.
Logging configuration file
Properties file location
The location of the logging configuration properties file is:
- $GUI_CONFDIR/log4j2.xml
File format customization
The format of the log-file entries can be changed. For more information about file formats, see the log4cxx documentation under "Configuration" at http://logging.apache.org/log4cxx/.
Log levels
The default log level is INFO.
| Level | Description |
|---|---|
| DEBUG | Logs all debug-level messages. At this log level, all DEBUG, INFO, WARN, ERROR, and FATAL messages are logged. |
| INFO | Logs all informational messages about events that occurred. For example, IBM Spectrum LSF Application Center successfully started. At this log level, all INFO, WARN, ERROR, and FATAL messages are logged. |
| WARN | Logs only those messages that are potentially harmful. The system can tolerate this error. Features and performance are not affected. At this log level, all WARN, ERROR, and FATAL messages are logged. |
| ERROR | Logs only those messages that indicate error conditions. Includes system errors and user errors. These error conditions might allow the application to continue running. Features and performance might be partially affected. For example, cannot create a process to execute a job, failed to create directories because of disk quota. At this log level, all ERROR and FATAL messages are logged. |
| FATAL | Logs only those messages in which the system is unusable. The whole system cannot work normally. For example, the database connection failed. At this log level, all FATAL messages are logged. |
Changing a log level
- Open the log4j2.xml file, located in the gui configure directory (GUI_CONFDIR).
- Navigate to the section that you want to change. For example:, to change the log level of the customLevel:
<!-- You can change the log level. Possible values: fatal, error, warn, info, debug --> <Property name="customLevel">error</Property> - Change customLevel to a new logging level.
- Save and close the log4j2.xml file
- Restart the pmc service.