Xeams Home » Products » Xeams » Knowledge Base
Document information
| Document ID: | 1034 |
|---|---|
| Subject: | Logging options in Xeams |
| Creation date: | 9/29/09 8:19 AM |
| Last modified on: | 6/7/10 5:47 AM |
Different logging options in Xeams
Several logs files are created in Xeams that help users troubleshoot different problems. The easiest way to access these logs files is through the Admin Console by clicking View Logs under the Tool menu. Alternatively, you can also view these log files manually by looking at the contents of the $XEAMS_PATH/logs folder.
There are approximately 16 different log files available. If you do not see all of them on the screen, click the Modify Logging Configuration link on the top and enable the logs you wish to create.
Searching for errors in a log file
The most important log file is Xeams.log, which typically appears at the bottom (file names are alphabetically sorted). The server will log every error, warning and information messages to this file. This should be the first location to look for the cause of any unexpected behavior in the server. To search for error, type the word ERROR in the Filter string field and click show content. Refer to the image below.

Reading the log files
Every log file in Xeams uses the following convention to write log lines in the fileTimestamp LogType Location MessageTimestamp - Represents the time this log was generated
LogType - This represents the severity level of the log. An can be any one of the following:
- ERROR - This type of log appears when an unexpected error occurs in the system
- WARN - This represents less severe or temporary errors. For example, if the DNS server takes a long time to resolve a domain name, you will see a WARNing message.
- INFO - These represents informational message. For example, several informational messages are generated when the server starts up.
- DEBUG - These messages do no appear in production server. However, if needed they can be turned on
Message - This is the actual message containing a description of the event.




