Administrator's Guide - Kerio Software Archive

22.13 Warning Log
Events causing display of warning messages in this log do not greatly affect Kerio Control’s
operation. They can, however, indicate certain (or possible) problems. The Warning log can
help if for example a user is complaining that certain services are not working.
Each warning message is identified by its numerical code (code xxx:). The following warning
categories are defined:
• 1000-1999 — system warnings (e.g. an application found that is known as conflicting)
• 2000-2999 — Kerio Control configuration issues (invalid values retrieved from the
configuration file)
• 3000-3999 — warning from operations of Kerio Control Engine (e.g. DHCP, DNS,
anti-virus check, user authentication, etc.)
• 4000-4999 — license warnings (subscription expiration, forthcoming expiration of
Kerio Control’s license, Kerio Web Filter license, or the anti-virus license)
Note: License expiration is considered to be an error and it is logged into the Error
log.
• 5000-5099 — Bandwidth Limiter warnings
• 5100-5199 — Kerio Web Filter warnings
• 5200-5299 — crashdumps
Examples of Warning logs:
[15/Apr/2008 15:00:51] (3004) Authentication subsystem warning:
Kerberos 5 auth: user james@company.com not authenticated
[15/Apr/2008 15:00:51] (3004) Authentication subsystem warning:
Invalid password for user admin
[16/Apr/2008 10:53:20] (3004) Authentication subsystem warning:
User jflyaway doesn’t exist
• The first log informs that authentication of user jsmith by the Kerberos system in
the company.com domain failed
• The second log informs on a failed authentication attempt by user admin (invalid
password)
• The third log informs on an authentication attempt by a user which does not exist
(johnblue)
305