Current Network Status
Last Updated: Wed May 15 22:42:27 GMT 2024
Updated every 90 seconds
Nagios® Core™ 4.4.9 - www.nagios.org
Logged in as guest
- Notifications are disabled
View Service Status Detail For All Host Groups
View Host Status Detail For This Host Group
View Status Overview For This Host Group
View Status Summary For This Host Group
View Status Grid For This Host Group
Host Status Totals
Up Down Unreachable Pending
141 2 4 0
All Problems All Types
6 147
Service Status Totals
Ok Warning Unknown Critical Pending
996 0 4 56 0
All Problems All Types
60 1056
Display Filters:
Host Status Types:All
Host Properties:Any
Service Status Types: Critical
Service Properties:Any
Service Status Details For Host Group 'distro_RedHat'
Entries sorted by state duration (descending)

Host Sort by host name (ascending)Sort by host name (descending)Service Sort by service name (ascending)Sort by service name (descending)Status Sort by service status (ascending)Sort by service status (descending)Last Check Sort by last check time (ascending)Sort by last check time (descending)Duration Sort by state duration (ascending)Sort by state duration time (descending)Attempt Sort by current attempt (ascending)Sort by current attempt (descending)Status Information
db03.iad2.fedoraproject.org
Check MySQL Backup
This service has 1 comment associated with itThis service problem has been acknowledged
CRITICAL 05-15-2024 22:38:08 1d 1h 13m 31s 3/3 FILE_AGE CRITICAL: File not found - /backups/fpo-mediawiki-latest.xz 
busgateway01.iad2.fedoraproject.org
Check datanommer for recent fedbadges messages
This service has 1 comment associated with itThis service problem has been acknowledged
CRITICAL 05-15-2024 22:32:49 0d 8h 30m 20s 3/3 CRIT: no fedbadges messages in 259200 seconds 
sign-bridge01.iad2.fedoraproject.org
Sigul bridge Process
CRITICAL 05-15-2024 22:32:49 0d 1h 15m 23s 3/3 PROCS CRITICAL: 0 processes with args 'sigul/bridge.py', UID = 989 (sigul) 
log01.iad2.fedoraproject.org
Check Merged Log
CRITICAL 05-15-2024 22:09:40 0d 0h 32m 47s 1/3 (No output on stdout) stderr: connect to address 10.3.163.39 port 5666: No route to host 
qvmhost-x86-02.iad2.fedoraproject.org
Check_Raid
CRITICAL 05-15-2024 22:10:04 0d 0h 32m 23s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
github2fedmsg01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:12:22 0d 0h 30m 5s 1/3 (No output on stdout) stderr: connect to address 10.3.163.53 port 5666: No route to host 
db-openqa01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:12:30 0d 0h 29m 57s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
noc02.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:12:46 0d 0h 29m 41s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
ipa02.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:12:47 0d 0h 29m 40s 1/3 (No output on stdout) stderr: connect to address 10.3.163.55 port 5666: No route to host 
log01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:13:45 0d 0h 28m 42s 1/3 (No output on stdout) stderr: connect to address 10.3.163.39 port 5666: No route to host 
flatpak-cache01.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:13:47 0d 0h 28m 40s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
qvmhost-x86-02.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:14:30 0d 0h 27m 57s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
smtp-mm-ib01.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:14:41 0d 0h 27m 46s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
vmhost-x86-03.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:14:55 0d 0h 27m 32s 1/3 (No output on stdout) stderr: connect to address 10.3.163.13 port 5666: No route to host 
download-ib01.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:17:03 0d 0h 25m 24s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Disk_Space_/
CRITICAL 05-15-2024 22:21:26 0d 0h 21m 1s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
ibiblio02.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:25:52 0d 0h 16m 35s 1/3 (No output on stdout) stderr: connect to address 152.19.134.169 port 5666: Connection refused 
dl05.iad2.fedoraproject.org
mail_queue
CRITICAL 05-15-2024 22:32:40 0d 0h 9m 47s 1/7 (No output on stdout) stderr: connect to address 10.3.163.84 port 5666: No route to host 
dl02.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:32:49 0d 0h 9m 38s 1/3 (No output on stdout) stderr: connect to address 10.3.163.50 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:49 0d 0h 9m 38s 1/7 (No output on stdout) stderr: connect to address 10.3.163.50 port 5666: No route to host 
mailman01.iad2.fedoraproject.org
check mailman api
CRITICAL 05-15-2024 22:32:49 0d 0h 9m 38s 1/5 (No output on stdout) stderr: connect to address 10.3.163.57 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:49 0d 0h 9m 38s 1/7 (No output on stdout) stderr: connect to address 10.3.163.57 port 5666: No route to host 
mm-frontend-checkin01.iad2.fedoraproject.org
Swap-Is-Low
CRITICAL 05-15-2024 22:37:49 0d 0h 9m 38s 1/4 (No output on stdout) stderr: connect to address 10.3.163.91 port 5666: No route to host 
http-mm-publiclist-internal
CRITICAL 05-15-2024 22:37:49 0d 0h 9m 38s 1/3 connect to address 10.3.163.91 and port 80: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:49 0d 0h 9m 38s 1/7 (No output on stdout) stderr: connect to address 10.3.163.91 port 5666: No route to host 
rabbitmq03.iad2.fedoraproject.org
Swap-Is-Low
CRITICAL 05-15-2024 22:37:49 0d 0h 9m 38s 1/4 (No output on stdout) stderr: connect to address 10.3.163.80 port 5666: No route to host 
value02.iad2.fedoraproject.org
Swap-Is-Low
CRITICAL 05-15-2024 22:37:49 0d 0h 9m 38s 1/4 (No output on stdout) stderr: connect to address 10.3.163.110 port 5666: No route to host 
vmhost-x86-04.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:32:49 0d 0h 9m 38s 1/3 (No output on stdout) stderr: connect to address 10.3.163.14 port 5666: No route to host 
vmhost-x86-07.iad2.fedoraproject.org
Zombie Processes
CRITICAL 05-15-2024 22:32:49 0d 0h 9m 38s 1/3 (No output on stdout) stderr: connect to address 10.3.163.17 port 5666: No route to host 
mailman01.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/3 (No output on stdout) stderr: connect to address 10.3.163.57 port 5666: No route to host 
http-mailman-internal
CRITICAL 05-15-2024 22:37:50 0d 0h 9m 37s 1/3 connect to address 10.3.163.57 and port 80: No route to host 
rabbitmq03.iad2.fedoraproject.org
Check bus server alarms
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/3 (No output on stdout) stderr: connect to address 10.3.163.80 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/3 (No output on stdout) stderr: connect to address 10.3.163.80 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/7 (No output on stdout) stderr: connect to address 10.3.163.80 port 5666: No route to host 
value02.iad2.fedoraproject.org
mail_queue
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/7 (No output on stdout) stderr: connect to address 10.3.163.110 port 5666: No route to host 
vmhost-x86-04.iad2.fedoraproject.org
SSH-virtservers
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/3 connect to address 10.3.163.14 and port 22: No route to host 
Total Processes
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/3 (No output on stdout) stderr: connect to address 10.3.163.14 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/7 (No output on stdout) stderr: connect to address 10.3.163.14 port 5666: No route to host 
vmhost-x86-07.iad2.fedoraproject.org
Cron Daemon
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/3 (No output on stdout) stderr: connect to address 10.3.163.17 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/3 (No output on stdout) stderr: connect to address 10.3.163.17 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:50 0d 0h 9m 37s 1/7 (No output on stdout) stderr: connect to address 10.3.163.17 port 5666: No route to host 
rabbitmq03.iad2.fedoraproject.org
Check bus server processes
CRITICAL 05-15-2024 22:32:51 0d 0h 9m 36s 1/3 (No output on stdout) stderr: connect to address 10.3.163.80 port 5666: No route to host 
value02.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:32:51 0d 0h 9m 36s 1/3 (No output on stdout) stderr: connect to address 10.3.163.110 port 5666: No route to host 
vmhost-x86-04.iad2.fedoraproject.org
Cron Daemon
CRITICAL 05-15-2024 22:32:51 0d 0h 9m 36s 1/3 (No output on stdout) stderr: connect to address 10.3.163.14 port 5666: No route to host 
vmhost-x86-07.iad2.fedoraproject.org
SSH-virtservers
CRITICAL 05-15-2024 22:32:51 0d 0h 9m 36s 1/3 connect to address 10.3.163.17 and port 22: No route to host 
dl05.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:33:26 0d 0h 9m 1s 1/3 (No output on stdout) stderr: connect to address 10.3.163.84 port 5666: No route to host 
mm-frontend-checkin01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:33:51 0d 0h 8m 36s 1/3 (No output on stdout) stderr: connect to address 10.3.163.91 port 5666: No route to host 
value02.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:36:01 0d 0h 6m 26s 1/3 (No output on stdout) stderr: connect to address 10.3.163.110 port 5666: No route to host 
vmhost-x86-07.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:36:18 0d 0h 6m 9s 1/3 (No output on stdout) stderr: connect to address 10.3.163.17 port 5666: No route to host 
rabbitmq01.iad2.fedoraproject.org
Check bus cluster
CRITICAL 05-15-2024 22:36:56 0d 0h 5m 31s 3/3 RABBITMQ_CLUSTER CRITICAL - 1 failed cluster node: rabbit@rabbitmq03.iad2.fedoraproject.org 
dl05.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:38:17 0d 0h 4m 10s 1/3 (No output on stdout) stderr: connect to address 10.3.163.84 port 5666: No route to host 
mm-frontend01.iad2.fedoraproject.org
http-mm-publiclist-internal
CRITICAL 05-15-2024 22:41:54 0d 0h 0m 33s 3/3 HTTP CRITICAL: HTTP/1.1 500 INTERNAL SERVER ERROR - 521 bytes in 2.823 second response time 
vmhost-x86-08.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:41:54 0d 0h 0m 33s 3/3 (No output on stdout) stderr: connect to address 10.3.163.28 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:41:57 0d 0h 0m 30s 3/3 (No output on stdout) stderr: connect to address 10.3.163.28 port 5666: No route to host 
db-fas01.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:42:04 0d 0h 0m 23s 1/3 (No output on stdout) stderr: connect to address 10.3.163.42 port 5666: No route to host 
db03.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:42:07 0d 0h 0m 20s 1/3 (No output on stdout) stderr: connect to address 10.3.163.44 port 5666: No route to host 

Results 1 - 56 of 56 Matching Services