Current Network Status
Last Updated: Wed May 15 22:21:12 GMT 2024
Updated every 90 seconds
Nagios® Core™ 4.4.9 - www.nagios.org
Logged in as guest
- Notifications are disabled
Host Status Totals
Up Down Unreachable Pending
215 2 4 0
All Problems All Types
6 221
Service Status Totals
Ok Warning Unknown Critical Pending
1644 2 0 129 0
All Problems All Types
131 1775
Display Filters:
Host Status Types: Pending | Up
Host Properties:Any
Service Status Types: Critical
Service Properties: Not In Scheduled Downtime & Has Not Been Acknowledged & Active Checks Enabled
Service Status Details For Host Group 'nomail'
Entries sorted by host name (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
vmhost-x86-03.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:11:44 0d 0h 9m 28s 3/3 (No output on stdout) stderr: connect to address 10.3.163.13 port 5666: No route to host 
Disk_Space_/
CRITICAL 05-15-2024 22:14:55 0d 0h 6m 17s 1/3 (No output on stdout) stderr: connect to address 10.3.163.13 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:51 0d 0h 8m 21s 1/3 (No output on stdout) stderr: connect to address 10.3.163.13 port 5666: No route to host 
SSH-virtservers
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 connect to address 10.3.163.13 and port 22: No route to host 
Total Processes
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 (No output on stdout) stderr: connect to address 10.3.163.13 port 5666: No route to host 
Zombie Processes
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 (No output on stdout) stderr: connect to address 10.3.163.13 port 5666: No route to host 
tang02.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:10:22 0d 0h 10m 50s 1/3 (No output on stdout) stderr: connect to address 10.3.163.38 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 (No output on stdout) stderr: connect to address 10.3.163.38 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/7 (No output on stdout) stderr: connect to address 10.3.163.38 port 5666: No route to host 
sundries01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:10:20 0d 0h 10m 52s 1/3 (No output on stdout) stderr: connect to address 10.3.163.81 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 (No output on stdout) stderr: connect to address 10.3.163.81 port 5666: No route to host 
sign-bridge01.iad2.fedoraproject.org
Sigul bridge Process
CRITICAL 05-15-2024 22:12:49 0d 0h 54m 8s 3/3 PROCS CRITICAL: 0 processes with args 'sigul/bridge.py', UID = 989 (sigul) 
secondary01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:11:36 0d 0h 9m 36s 3/3 (No output on stdout) stderr: connect to address 10.3.163.86 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 (No output on stdout) stderr: connect to address 10.3.163.86 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:12:51 0d 0h 8m 21s 1/7 (No output on stdout) stderr: connect to address 10.3.163.86 port 5666: No route to host 
rabbitmq02.iad2.fedoraproject.org
Check bus server alarms
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 (No output on stdout) stderr: connect to address 10.3.163.79 port 5666: No route to host 
Disk_Space_/
CRITICAL 05-15-2024 22:10:13 0d 0h 10m 59s 1/3 (No output on stdout) stderr: connect to address 10.3.163.79 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 (No output on stdout) stderr: connect to address 10.3.163.79 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/7 (No output on stdout) stderr: connect to address 10.3.163.79 port 5666: No route to host 
rabbitmq01.iad2.fedoraproject.org
Check bus cluster
CRITICAL 05-15-2024 22:14:55 0d 0h 6m 17s 3/3 RABBITMQ_CLUSTER CRITICAL - 1 failed cluster node: rabbit@rabbitmq02.iad2.fedoraproject.org 
qvmhost-x86-02.iad2.fedoraproject.org
Check_Raid
CRITICAL 05-15-2024 22:10:04 0d 0h 11m 8s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Cron Daemon
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Disk Space /boot
CRITICAL 05-15-2024 22:10:05 0d 0h 11m 7s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Disk_Space_/
CRITICAL 05-15-2024 22:14:30 0d 0h 6m 42s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
SSH-virtservers
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 CRITICAL - Socket timeout 
Total Processes
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
mail_queue
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/7 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
qvmhost-x86-01.iad2.fedoraproject.org
Cron Daemon
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Disk_Space_/
CRITICAL 05-15-2024 22:11:35 0d 0h 9m 37s 3/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
SSH-virtservers
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 CRITICAL - Socket timeout 
Total Processes
CRITICAL 05-15-2024 22:11:34 0d 0h 9m 38s 3/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Zombie Processes
CRITICAL 05-15-2024 22:12:50 0d 0h 8m 22s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
mail_queue
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/7 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
openqa01.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:13:18 0d 0h 7m 54s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
mail_queue
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/7 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
openqa-lab01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:09:32 0d 0h 11m 40s 3/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
mail_queue
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/7 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
mm-frontend01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:09:49 0d 0h 11m 23s 3/3 (No output on stdout) stderr: connect to address 10.3.163.61 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 (No output on stdout) stderr: connect to address 10.3.163.61 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/7 (No output on stdout) stderr: connect to address 10.3.163.61 port 5666: No route to host 
mm-crawler02.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:08:39 0d 0h 12m 33s 1/3 (No output on stdout) stderr: connect to address 10.3.163.96 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 (No output on stdout) stderr: connect to address 10.3.163.96 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/7 (No output on stdout) stderr: connect to address 10.3.163.96 port 5666: No route to host 
memcached01.iad2.fedoraproject.org
Check for the presence of the memcached daemon
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 (No output on stdout) stderr: connect to address 10.3.163.59 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 (No output on stdout) stderr: connect to address 10.3.163.59 port 5666: No route to host 
mbs-backend01.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 21:25:00 0d 0h 56m 12s 3/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
log01.iad2.fedoraproject.org
Check Merged Log
CRITICAL 05-15-2024 22:09:40 0d 0h 11m 32s 1/3 (No output on stdout) stderr: connect to address 10.3.163.39 port 5666: No route to host 
Disk space /var/log
CRITICAL 05-15-2024 22:09:22 0d 0h 11m 50s 1/3 (No output on stdout) stderr: connect to address 10.3.163.39 port 5666: No route to host 
Disk_Space_/
CRITICAL 05-15-2024 22:13:45 0d 0h 7m 27s 1/3 (No output on stdout) stderr: connect to address 10.3.163.39 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 (No output on stdout) stderr: connect to address 10.3.163.39 port 5666: No route to host 
koji02.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 21:23:05 0d 0h 58m 7s 3/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
http-koji-frontend
CRITICAL 05-15-2024 22:19:50 0d 0h 1m 22s 3/3 (Service check timed out after 60.01 seconds) 
ipa02.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:08:24 0d 0h 12m 48s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Disk_Space_/
CRITICAL 05-15-2024 22:12:47 0d 0h 8m 25s 1/3 (No output on stdout) stderr: connect to address 10.3.163.55 port 5666: No route to host 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 (No output on stdout) stderr: connect to address 10.3.163.55 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:12:48 0d 0h 8m 24s 1/7 (No output on stdout) stderr: connect to address 10.3.163.55 port 5666: No route to host 
github2fedmsg01.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:09:23 0d 0h 11m 49s 3/3 (No output on stdout) stderr: connect to address 10.3.163.53 port 5666: No route to host 
Disk_Space_/
CRITICAL 05-15-2024 22:12:22 0d 0h 8m 50s 1/3 (No output on stdout) stderr: connect to address 10.3.163.53 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/7 (No output on stdout) stderr: connect to address 10.3.163.53 port 5666: No route to host 
flatpak-cache01.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:13:47 0d 0h 7m 25s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
mail_queue
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/7 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
dl01.iad2.fedoraproject.org
mail_queue
CRITICAL 05-15-2024 22:12:39 0d 0h 8m 33s 1/7 (No output on stdout) stderr: connect to address 10.3.163.49 port 5666: No route to host 
db-openqa01.iad2.fedoraproject.org
Disk Space /boot
CRITICAL 05-15-2024 22:12:07 0d 0h 9m 5s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Disk_Space_/
CRITICAL 05-15-2024 22:12:30 0d 0h 8m 42s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
Rsyslogd Process
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
mail_queue
CRITICAL 05-15-2024 22:12:49 0d 0h 8m 23s 1/7 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 
buildvm-ppc64le-osbuild02.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 21:23:31 0d 0h 57m 41s 3/3 CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. 

Results 1 - 72 of 72 Matching Services