SecureTransport 5.5 Administrator Guide Save PDF Selected topic Selected topic and subtopics All content Admin log file audit.log – This log file contains information on configuration changes made by Java components of the SecureTransport Administration Tool and database starts and stops. When the configuration changes are logged to the database (the default), failed administrator login attempts and database starts, stops, and configuration changes are still logged to this file. The format and content of this file is controlled by the <FILEDRIVEHOME>/conf/admin-log4j.xml file. This file uses the log4j format. By default, the logs are in the following format: %d %s %m Where: %d is the date %s is the subcomponent %m is the log message admin_tomcat<date>.log – This log file contains Tomcat-specific error messages. The file contains the Java stack traces for the errors. Related topics: Log4j files Database log files FTPD log file General log files Modify the log4j files Redirect log4j output from the database Control log fallback from database to file Server log rotation and monitor scheduling More SecureTransport 5.5 docs All docs | HTML only | PDF only Related Links
Admin log file audit.log – This log file contains information on configuration changes made by Java components of the SecureTransport Administration Tool and database starts and stops. When the configuration changes are logged to the database (the default), failed administrator login attempts and database starts, stops, and configuration changes are still logged to this file. The format and content of this file is controlled by the <FILEDRIVEHOME>/conf/admin-log4j.xml file. This file uses the log4j format. By default, the logs are in the following format: %d %s %m Where: %d is the date %s is the subcomponent %m is the log message admin_tomcat<date>.log – This log file contains Tomcat-specific error messages. The file contains the Java stack traces for the errors. Related topics: Log4j files Database log files FTPD log file General log files Modify the log4j files Redirect log4j output from the database Control log fallback from database to file Server log rotation and monitor scheduling More SecureTransport 5.5 docs All docs | HTML only | PDF only
Admin log file audit.log – This log file contains information on configuration changes made by Java components of the SecureTransport Administration Tool and database starts and stops. When the configuration changes are logged to the database (the default), failed administrator login attempts and database starts, stops, and configuration changes are still logged to this file. The format and content of this file is controlled by the <FILEDRIVEHOME>/conf/admin-log4j.xml file. This file uses the log4j format. By default, the logs are in the following format: %d %s %m Where: %d is the date %s is the subcomponent %m is the log message admin_tomcat<date>.log – This log file contains Tomcat-specific error messages. The file contains the Java stack traces for the errors. Related topics: Log4j files Database log files FTPD log file General log files Modify the log4j files Redirect log4j output from the database Control log fallback from database to file Server log rotation and monitor scheduling More SecureTransport 5.5 docs All docs | HTML only | PDF only