@c This is part of the Radius manual.@c Copyright (C) 1999,2000,2001,2002,2003 Free Software Foundation, Inc.@c Written by Sergey Poznyakoff@c See file radius.texi for copying conditions.@comment *******************************************************************@node Logging, Problem Tracking, Accounting, Top@chapter Logging@cindex LoggingGNU Radius reports every event worth mentioning. The events aresegregated by their severity level. Radius discerns the followinglevels (in order of increasing severity):@table @code@item DebugThe debug messages (@ref{Debugging}).@item AuthUnder this level every authentication attempt is logged. This is enabledby setting@smallexamplelevel auth;@end smallexample@noindentin the @code{category auth} statement of the @file{config} file.@item ProxyMessages regarding proxy requests (@pxref{Proxying}).@item InfoInformational messages.@item NoticeNormal, but significant conditions.@item WarningWarning conditions. These mean some deviations from normal work.@item ErrorError conditions. Usually these require special attention.@item CRITCritical conditions due to which Radius is no longer able to continueworking. These require urgent actions from the site administrator.@end tableBy default, all messages in all levels are output to the file@file{radlog/radius.log}. In addition, messages in level@code{CRIT} are also duplicated to the system console. These defaultscan be overridden using @code{logging} statement in the@file{raddb/config} file.(@xref{logging,,logging statement}, for the description of loggingstatement syntax; @pxref{Naming Conventions} for information about the locations of different Radius configuration files.)