An essential resource for troubleshooting Kerio issues is the Debug log, which outputs verbose details of specific activities. This is helpful when administrators want to perform an analysis of some activity that may not be working correctly.
For example, the name resolution takes longer than usual. In this case, DNS messages can be enabled to review the queries and their responses.
This article provides information on how to access, set, and analyze the Debug logs.
Accessing the Debug Window
The Debug log window can be accessed from the Logs tab in the admin Dashboard using the following path:
Webadmin > Logs > Debug
Setting the Debug Log
- Right-click on the Debug window and select the Messages option.
- In the Logging Messages window, select the specific options you wish to monitor.
Check the article: Debug Log in Kerio Control for additional information on generating and analyzing the Kerio Control logs.
Analyzing the Debug Logs
- You can search for a string of text or enable highlighting to identify the occurrences of a string.
- You can also save the log output to your local computer for additional analysis.
- The Debug log events are in a human-readable format to simplify the troubleshooting process. However, a raw analysis of the routed packets may be required.
- Right-click on the Debug log window to enable Packet Logging.
Kerio Control accepts all the regular expressions under the POSIX standard. Good knowledge of this standard will be advantageous to understand problematic situations pointed in the logs.