Email Engine Debug Logging
From ARSWiki
This article covers enabling debug logging for the email engine. This article was written against 7.0.1.
Contents |
Changes to the Email Engine Start Script (emaild.sh)
There are changes required in the email startup script. The important thing to note here is the addition of -Dmail.debug=true to the command that starts the jvm and loads EmailDaemon.jar.
Example
Change from:
exec ${JAVA_BIN}/java -Djava.library.path=${InstallPath} \
-cp ${CP_PATH} com.remedy.arsys.emaildaemon.EmailDaemon \
-d ${InstallPath} > ${LogFile} 2>&1
Change To:
exec ${JAVA_BIN}/java -Djava.library.path=${InstallPath} \
-Dmail.debug=true \
-cp ${CP_PATH} com.remedy.arsys.emaildaemon.EmailDaemon \
-d ${InstallPath} > ${LogFile} 2>&1
Changes to the JRE
The JRE requires certain updates that instruct it what to log and to where it should log. These are specificed in the logging.properies file in the jre installation directory.
Log Levels
In all likelihood, the INFO log level will show you all the information you need to troubleshoot an issue with the email engine. The info level will show full smtp conversations, including data, among many other things. If you enable the logging with ALL or FINEST as the log level, you can expect more than 1gb/day on a busy server (busy server defined as 8k messages per day).
- SEVERE
- WARNING
- INFO
- CONFIG
- FINE
- FINER
- FINEST
- ALL
Changes to logging.properties
The following lines can be appended to the end of the logging.properties file:
handlers=java.util.logging.FileHandler,java.util.logging.ConsoleHandler com.remedy.arsys.emaildaemon.ARSystemHandler.level=INFO com.remedy.arsys.emaildaemon.level=INFO java.util.logging.ConsoleHandler.level = INFO
