Home
  •  

Process Cron Service Health

Microsoft.Solaris.11.Process.Cron.Monitor (UnitMonitor)

Solaris 11 Process Cron Monitor

Knowledge Base article:

Summary

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

The Cron daemon facilitates scheduled command execution.

Causes

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

Resolutions

Check the service on the system by running 'ps -ef | grep cron' 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/cron 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.11.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
Cron daemon is not running
The cron daemon on server {0} is not running.
RunAsDefault

Source Code:

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

  <Category>AvailabilityHealth</Category>

  <AlertSettings AlertMessage="Microsoft.Solaris.11.Process.Cron.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>cron</ProcessName>

    <Interval>300</Interval>

  </Configuration>

</UnitMonitor>