SyferLock Help Center

Message Format

Description of the message format

Message Format

The following processes write events to syslog

  • GridGuard J2EE Server
  • Radius Server
  • Database Server
  • LDAP Server

The format for the messages are as follows:

{Month} {Day} {Time} {Server} {Service} [{Thread}]: {Log-Level} {Description}

Note:

  • The Log-Level is an optional field and may not be always set.
  • All times are in UTC

Given below are a few examples of messages:

Jun 10 12:54:48 ggva-demo slapd[2093]: conn=47699 op=1 UNBIND
Jun 10 12:54:48 ggva-demo slapd[2093]: conn=47699 fd=18 closed
Jun 10 12:54:48 ggva-demo Jun 10 12:54:48 ggva-demo com.syferlock.util.Logger[GridGuard Application Monitor]: WARN Secondary User Store staging-ad-userstore initialized with warnings (AppRealmDef saml)
Jun 10 12:54:48 ggva-demo com.syferlock.util.Logger[GridGuard Application Monitor]: WARN User Info Store staging-ad-userinfostore initialized with warnings (AppRealmDef saml)

Service Field

The following are possible values for the Service field:

  • com.syferlock.* - these are specific to the Java classes these messages are logged from. These are logged by the GridGuard J2EE server
  • slapd & slapd-proxy - these are written out the LDAP server. The messages associated with these services typically do not have a Log-Level associated with them
  • radiusd - these messages are written out by the Radius server. The messages associated with these services typically do not have a Log-Level associated with them
  • GGVA_API - these are written out by the internal server API which are invoked only during the upgrade process & from the Administration & Configuration Console
  • RemoveDeadNonce - a clean up script that runs to delete expired nonces.
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk