Your Kerio Connect logs have grown too large, and you cannot open them for review, or your server may become sluggish when opening or viewing the logs. You receive the error “Log Exceeded the limit of 2147483647 lines. No more content of log will be seen until the log will be cleared or rotated (see Log Setting in context menu)” when opening your server logs.
Kerio Connect has a built-in limit of 2147483647 lines within your logs; however, you will likely begin to see performance trouble opening them well before that limit is hit. It is suggested that admins enable some form of log rotation within their server logs to help mitigate this trouble before it appears.
If your server logs have already grown too large, however, it may be necessary to manually remove these on the back end using the steps below:
- Stop Kerio Connect
- Navigate to the log directory by OS:
- Windows —
- Mac OS X —
- Linux —
- Windows —
- Identify the most recent copy of the affected log file:
Note: The most recent log will not contain a rotation number after it. If rotation is not enabled, you will see only the main log file and IDX file.
- Remove the affected large logs and their IDX file.
Note: You can alternatively rename or move them if you intend to keep a copy.
- Restart Kerio Connect
After restarting Kerio Connect, the server will automatically recreate the new log and IDX files, and you are once again able to open the log within the WebAdmin without any issues: