Microsemi SyncServer S200, User Manual

Page: 62 / 190

Web Interface
daemon.log : The daemon log contains entries submitted by the daemon processes that
provide the services in the SyncServer. Examples of daemon log entries are NTP changes,
SNMP events, and xinetd events.
messages : The messages file is something of a catchall file. By selecting various priorities, it
is possible to capture large amounts of data regarding system operation. However, the
volume of data becomes impractical to manage quickly. As such, this file is cleared at each
power cycle or reboot.
events : The events log is not configurable. This log is maintained outside syslogd and con-
tains configuration and event data related to operations performed in the web interface.
Log Priorities
In the case of kernel, syslog, auth and daemon logs, the priority specified will cause all mes-
sages less than or equal to the selected priority to be logged. The priorities are defined in des-
cending order.
In the case of the messages log, only the selected priorities are logged. As such, up to four
priority levels are supported.
Debug : This priority level captures debug output from applications designed to produce this
type of output. This level generates a large volume of traffic and is not recommended unless
it is done under the direction of technical support personnel. An example may be a signal
handler called.
Info : This level captures informational output. This level typically provides information regard-
ing successful operations. An example may be a successful file save or a normal application
startup.
Notice : This level captures transactional information. An example of this could be a network
connection or login.
Warning: This level captures information that is not expected by the application or system.
This could be something the system is not configured to handle. An example might be a mal-
formed network packet or a drive change caused by inserting a thumb drive into a USB slot.
Err (deprecated) : The use of this level is deprecated.
Crit : This level captures critical information. This data can often be used to debug the failure
of a system or application under abnormal conditions. An example of this may be a memory
error.
Alert : This level captures information about which the administrator should be made aware.
An example of this could be a failed login attempt.
Emerg : This level captures messages of the highest priority. These are typically last resort
messages before an abnormal exit of the calling application or the system itself. An example
of this would be a hardware error or memory exhausted message.
Remote Log System
It is possible to send a copy of all messages to up to 8 (eight) remote system running syslogd.
This allows centralized management of alarm messages. As the system logs are written to a
RAM based volume, messages may be lost if the system is rebooted or power cycled or
Page 62 .......................................................................... 997-01520-02 Rev. G2