Service Availability Report
Last Updated: Sun May 19 19:00:50 GMT 2024
Nagios® Core™ 4.4.9 - www.nagios.org
Logged in as guest
Service 'Sigul bridge Process' On Host 'sign-bridge01.iad2.fedoraproject.org'

Availability Report
04-25-2024 21:43:25 to 04-26-2024 21:43:25
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 22h 18m 52s92.977%92.977%
Scheduled0d 1h 21m 8s5.634%5.634%
Total0d 23h 40m 0s98.611%98.611%
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 20m 0s1.389%1.389%
Total0d 0h 20m 0s1.389%1.389%
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 args 'sigul/bridge.py', UID = 991 (sigul)
04-22-2024 00:00:0004-23-2024 00:00:001d 0h 0m 0sSERVICE OK (HARD)PROCS OK: 1 process with args 'sigul/bridge.py', UID = 991 (sigul)
04-23-2024 00:00:0004-24-2024 00:00:001d 0h 0m 0sSERVICE OK (HARD)PROCS OK: 1 process with args 'sigul/bridge.py', UID = 991 (sigul)
04-24-2024 00:00:0004-25-2024 00:00:001d 0h 0m 0sSERVICE OK (HARD)PROCS OK: 1 process with args 'sigul/bridge.py', UID = 991 (sigul)
04-25-2024 00:00:0004-25-2024 01:01:200d 1h 1m 20sSERVICE OK (HARD)PROCS OK: 1 process with args 'sigul/bridge.py', UID = 991 (sigul)
04-26-2024 00:00:0004-26-2024 20:02:170d 20h 2m 17sSERVICE OK (HARD)PROCS OK: 1 process with args 'sigul/bridge.py', UID = 991 (sigul)
04-26-2024 20:02:1704-26-2024 20:07:050d 0h 4m 48sHOST DOWNTIME STARTStart of scheduled downtime
04-26-2024 20:07:0504-26-2024 20:27:050d 0h 20m 0sSERVICE CRITICAL (HARD)(No output on stdout) stderr: connect to address 10.3.169.120 port 5666: Connection refused
04-26-2024 20:27:0504-26-2024 22:02:020d 1h 34m 57sSERVICE OK (HARD)PROCS OK: 1 process with args 'sigul/bridge.py', UID = 989 (sigul)
04-26-2024 22:02:0204-30-2024 21:34:063d 23h 32m 4sHOST DOWNTIME ENDEnd of scheduled downtime