Service Availability Report
Last Updated: Sat May 18 21:23:19 GMT 2024
Nagios® Core™ 4.4.9 - www.nagios.org
Logged in as guest
Service 'Cron Daemon' On Host 'bvmhost-p09-04.iad2.fedoraproject.org'

Availability Report
04-25-2024 00:39:07 to 04-26-2024 00:39:07
Duration: 1d 0h 0m 0s
First assumed service state:
Report period:Backtracked archives:
[ Availability report completed in 0 min 0 sec ]


Service State Breakdowns:

Service State Trends

StateType / ReasonTime% Total Time% Known Time
OKUnscheduled0d 23h 30m 10s97.928%97.928%
Scheduled0d 0h 17m 56s1.245%1.245%
Total0d 23h 48m 6s99.174%99.174%
WARNINGUnscheduled0d 0h 0m 0s0.000%0.000%
Scheduled0d 0h 0m 0s0.000%0.000%
Total0d 0h 0m 0s0.000%0.000%
UNKNOWNUnscheduled0d 0h 0m 0s0.000%0.000%
Scheduled0d 0h 0m 0s0.000%0.000%
Total0d 0h 0m 0s0.000%0.000%
CRITICALUnscheduled0d 0h 0m 0s0.000%0.000%
Scheduled0d 0h 11m 54s0.826%0.826%
Total0d 0h 11m 54s0.826%0.826%
UndeterminedNagios Not Running0d 0h 0m 0s0.000%
Insufficient Data0d 0h 0m 0s0.000%
Total0d 0h 0m 0s0.000%
AllTotal1d 0h 0m 0s100.000%100.000%


Service Log Entries:
[ View full log entries ]
Event Start TimeEvent End TimeEvent DurationEvent/State TypeEvent/State Information
04-21-2024 00:00:0004-22-2024 00:00:001d 0h 0m 0sSERVICE OK (HARD)PROCS OK: 1 process with command name 'crond', UID = 0 (root)
04-22-2024 00:00:0004-23-2024 00:00:001d 0h 0m 0sSERVICE OK (HARD)PROCS OK: 1 process with command name 'crond', UID = 0 (root)
04-23-2024 00:00:0004-24-2024 00:00:001d 0h 0m 0sSERVICE OK (HARD)PROCS OK: 1 process with command name 'crond', UID = 0 (root)
04-24-2024 00:00:0004-25-2024 00:00:001d 0h 0m 0sSERVICE OK (HARD)PROCS OK: 1 process with command name 'crond', UID = 0 (root)
04-25-2024 00:00:0004-25-2024 01:01:200d 1h 1m 20sSERVICE OK (HARD)PROCS OK: 1 process with command name 'crond', UID = 0 (root)
04-26-2024 00:00:0004-26-2024 00:09:170d 0h 9m 17sSERVICE OK (HARD)PROCS OK: 1 process with command name 'crond', UID = 0 (root)
04-26-2024 00:09:1704-26-2024 00:27:130d 0h 17m 56sHOST DOWNTIME STARTStart of scheduled downtime
04-26-2024 00:27:1304-26-2024 00:57:140d 0h 30m 1sSERVICE CRITICAL (HARD)(No output on stdout) stderr: connect to address 10.3.171.18 port 5666: Connection refused
04-26-2024 00:57:1404-26-2024 02:09:070d 1h 11m 53sSERVICE OK (HARD)PROCS OK: 1 process with command name 'crond', UID = 0 (root)
04-26-2024 02:09:0704-26-2024 17:21:180d 15h 12m 11sHOST DOWNTIME ENDEnd of scheduled downtime
04-26-2024 17:21:1804-26-2024 17:27:430d 0h 6m 25sHOST DOWNTIME STARTStart of scheduled downtime
04-26-2024 17:27:4304-26-2024 17:57:130d 0h 29m 30sSERVICE CRITICAL (HARD)CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds.
04-26-2024 17:57:1304-26-2024 19:21:060d 1h 23m 53sSERVICE OK (HARD)PROCS OK: 1 process with command name 'crond', UID = 0 (root)
04-26-2024 19:21:0604-30-2024 21:34:064d 2h 13m 0sHOST DOWNTIME ENDEnd of scheduled downtime