Web Interface
LOGS Tab
System Event Log
The Logs page provides access to system activity and messages that are generated by the
various subsystems in the SyncServer. The logs are separated by function. The logging
behavior can be configured using the ADMIN - Logs Config page. Each of the logs records a
series of time-stamped events.
In the case of the system, auth, daemon, kern and messages logs, the entries take the stand-
ard form defined by the syslog daemon. These entries are:
date time system facility message: Here "system" is the hostname that generated the mes-
sage. The "facility" is a component of the system generating the message. This could be any-
thing like the kernel itself, system daemons and even applications. Finally, there is the text of
the message itself. Here are two messages on the system SyncServer. One is from dae-
mon.log and the other from the kernel:
Sep 19 19:20:26 SyncServer ntpd[3577]: ntpd 4.2.0b@1.1396-o Tue Aug 9
01:05:42 UTC 2005 (7)
Sep 10 00:06:18 SyncServer kernel: Jida-Driver installed
In the case of the event log, the entries take the form of:
Date time user source description
Here "user" is the user logged into the web interface, "source" is the IP address of the remote
system using the web interface and "description" provides information regarding the nature
of the event. Here is a message showing a successful remote login along with the user id and
IP address of the contact.
10/01/2005 22:36:28 admin 192.168.7.16 Successful login
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.
syslog: syslog holds messages about system level events. Examples of system events are
privilege changes (e.g., sudo) and messages about regularly schedules events such as cron.
auth.log: The authentication log contains entries regarding authentication events from login or
PAM (Pluggable Authentication Module).
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.
kern.log: The kernel log contains entries submitted by the kernel. Examples of kernel events
are network errors or hardware changes.
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.
Page 68..........................................................................997-01520-02 Rev. G2
To Next Page
Loading...
