Home
  •  

Process Syslog Service Health

Microsoft.Solaris.10.Process.Syslog.Monitor (UnitMonitor)

Solaris 10 Process Syslog Monitor

Knowledge Base article:

Summary

The Syslog daemon is not running. Check the Diagnostic and Recovery results to see if further action is required.

The Syslog daemon implements message logging and forwarding to files and users.

Causes

An unhealthy state indicates that the Syslog daemon is not running.

Resolutions

Check the service on the system by running 'ps -ef | grep syslog' or by viewing the diagnostic in the Operations Manager Console. If it is down, you can start the process using the command '/etc/init.d/syslog start' or by clicking the recovery link in the Operations Manager Console.

For root cause analysis, first check the system log file (/var/adm/messages), and view any related entries at the time of failure. You may also check the system for any process core files. Use '/usr/bin/pstack [corefile]' to print a stack trace which will assist in troubleshooting the cause of failure.

Element properties:

TargetMicrosoft.Solaris.10.OperatingSystem
Parent MonitorSystem.Health.AvailabilityState
CategoryAvailabilityHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Unix.WSMan.Process.Status.MonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Syslog daemon is not running
The syslog daemon on server {0} is not running.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Solaris.10.Process.Syslog.Monitor" Accessibility="Public" Target="Microsoft.Solaris.10.OperatingSystem" TypeID="Unix!Microsoft.Unix.WSMan.Process.Status.MonitorType" Enabled="true" ParentMonitorID="SystemHealth!System.Health.AvailabilityState">

  <Category>AvailabilityHealth</Category>

  <AlertSettings AlertMessage="Microsoft.Solaris.10.Process.Syslog.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Host/Property[Type="Unix!Microsoft.Unix.Computer"]/PrincipalName$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState HealthState="Success" MonitorTypeStateID="Running" ID="Running"/>

    <OperationalState HealthState="Error" MonitorTypeStateID="NotRunning" ID="NotRunning"/>

  </OperationalStates>

  <Configuration>

    <TargetSystem>$Target/Host/Property[Type="Unix!Microsoft.Unix.Computer"]/NetworkName$</TargetSystem>

    <ProcessName>syslogd</ProcessName>

    <Interval>300</Interval>

  </Configuration>

</UnitMonitor>