C    Log File Management

This appendix provides information about the log files generated by the AlphaServer Management Station applications and the cmfd daemon.

C.1    Console logs

The console logs are located in the following directory, which contains the current and archived console logs generated by the cmfd daemon.

• /usr/opt/ams/logs/cmf.dated

The following directory is a link to the current logs.

• /usr/opt/ams/logs/cmf.dated/current

All other directories contain archived logs. The current and archived logs are preserved during AMS upgrade installations. You may move or delete the archived logs at any time.

C.2    AMS application logs

AMS components generate many logs that are used mainly for debugging purposes. The following list describes those files:

• The directory /usr/opt/ams/logs contains the following:

  • amsmgr.log

    This file is from the amsmgr component. It contains all of the commands sent to amsmgr for updating the AMS data store with new or modified configurations.

    This file is automatically archived by amsmgr when the file size reaches 1 MB. When this happens the amsmgr process renames amsmgr.log to amsmgr.log.old and creates a new log file. If an amsmgr.log.old file already exists, it is overwritten. Therefore, it is not necessary to manage this log file.

  • apw -date-#.txt

    This file is from the APW, which creates one log per APW session. The logs contain mostly platform data that is retrieved during an APW session. These files are never archived and can be removed at any time. The current session's file should be removed after the APW session has ended.

  • cmfd.log

    This file is from the cmfd daemon . Normally cmfd is run with no debugging options, so this file will not accumulate data. Should debugging be turned on, the file can be safely managed only when the cmfd daemon has been stopped.

• The directory /usr/opt/ams/tomcat/logs contains files generated by the Tomcat Web Server.

  • catalina.out

    This file, created when Tomcat starts, contains all the Java exceptions and error messages sent to System.out or System.err by Tomcat and the AMS Java server components (SPM/AMU/APW servers).

    When the file becomes large you can move it or delete it after you stop Tomcat. If the file is deleted while Tomcat is running, it will not be re-created until the next time you restart Tomcat.

  • catalina_log.date.txt

  • localhost_access_log.date.txt

  • localhost_log.date.txt

  These files contain mainly http session request information. Archived files can be removed at any time. For current files, follow same guideline as for catalina.out.

• The directory /usr/opt/ams/tomcat/webapps/spm/WEB-INF/log holds all of the log files generated by the AMU application. These files are as follows:

  • ServerCore.date.log

    This file contains AMU server errors

  • SMLANLib.errors.date.log

    This file contains errors generated by the interface library to the ES47, ES80, and GS1280 AlphaServer SMLAN

  • SMLANLib.events.date.log

    This file contains all the events received by the SMLAN

  • Logs.MV-(hex)IPaddress.data.log

    This file contains MBM log entries for ES47, ES80, and GS1280 systems configured with a NAT box with the IP address that is included in the log name.

  • platformName.errlog

    This file is generated only if you select to generated a CDL file for the platform. One file will contain all the CDL entries for each platform partition.

  These log files should be managed after the Tomcat Web server has been stopped. If you delete some or all files, new files will be created when the Tomcat server is restarted.