Administer > Status and notifications > Server log file > View the system log file

View the system log file

Applies to User Roles:

System Administrator

The System log (Syslog) file contains information about system events, such as failed logon attempts.

To view or edit system events in the Syslog file, follow these steps:

  1. Click Tailoring > Database Manager. Or, type db in the command line, and then press Enter or click Execute Command.
  2. Type syslog in the Form field, and then press Enter.
  3. Type any search criteria in the appropriate fields, and then click Search.

    A list of events in the Syslog file is displayed.

  4. Select a system event in the list to display detailed information about the event. To edit the event, make the desired changes to the detailed information, and then click Save.

The Syslog file records the following types of event:

  • Successful logon

    The following event is an example of a successful logon.

    Event Type Start Time Stop Time User Name Terminal Name Current Status IP Address PID
    user 7/15/2013 1:27:56   falcon SOAP-Windows 7 logged on 16.158.154.213 4
  • Failed logon

    The following event is an example of a failed logon.

    Event Type Start Time Stop Time User Name Terminal Name Current Status IP Address PID
    user 7/10/2013 20:12   ddd SOAP-Windows 7 login failed 16.158.154.213 4

    Note Failed logon events are recorded both when a user enters an incorrect password and when a user enters an incorrect user name.

  • Logout

    The following event is an example of a logout.

    Event Type Start Time Stop Time User Name Terminal Name Current Status IP Address PID
    user 7/7/2013 20:36 7/7/2013 22:33 falcon SOAP-Windows 7 logged off 16.158.154.213 4
  • Scheduler starts

    The following event is an example of a scheduler starting.

    Event Type Start Time Stop Time User Name Terminal Name Current Status IP Address PID
    scheduler 7/14/2013 0:25   availability availability started   3

    Note The IP address column is populated only if the event is triggered from a machine that is not the Service Manager server.

  • Scheduler terminates

    The following event is an example of a scheduler terminating.

    Event Type Start Time Stop Time User Name Terminal Name Current Status IP Address PID
    scheduler 7/14/2013 0:25 7/14/2013 0:25 KMUpdate SYSTEM stopped   18

    Note The IP address column is populated only if the event is triggered from a machine that is not the Service Manager server.