Current Network Status
Last Updated: Wed May 15 22:34:35 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
409 17 9 0
All Problems All Types
26 435
Service Status Totals
Ok Warning Unknown Critical Pending
2068 3 0 109 0
All Problems All Types
112 2180
Display Filters:
Host Status Types: Unreachable
Host Properties:Any
Service Status Types:All Problems
Service Properties:Any
Service Status Details For Host Group 'no_ping'
Entries sorted by host name (ascending)

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
certgetter01.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 1/3 (No output on stdout) stderr: connect to address 10.3.163.47 port 5666: No route to host 
Swap-Is-Low
CRITICAL 05-15-2024 22:32:50 0d 0h 1m 45s 1/4 (No output on stdout) stderr: connect to address 10.3.163.47 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:21 0d 0h 2m 14s 1/7 (No output on stdout) stderr: connect to address 10.3.163.47 port 5666: No route to host 
dl02.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 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 1m 46s 1/7 (No output on stdout) stderr: connect to address 10.3.163.50 port 5666: No route to host 
dl05.iad2.fedoraproject.org
Disk_Space_/
CRITICAL 05-15-2024 22:33:26 0d 0h 1m 9s 1/3 (No output on stdout) stderr: connect to address 10.3.163.84 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:40 0d 0h 1m 55s 1/7 (No output on stdout) stderr: connect to address 10.3.163.84 port 5666: No route to host 
ipsilon01.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 1/3 (No output on stdout) stderr: connect to address 10.3.163.105 port 5666: No route to host 
Swap-Is-Low
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 1/4 (No output on stdout) stderr: connect to address 10.3.163.105 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 1/7 (No output on stdout) stderr: connect to address 10.3.163.105 port 5666: No route to host 
mailman01.iad2.fedoraproject.org
Rsyslogd Process
CRITICAL 05-15-2024 22:32:50 0d 0h 1m 45s 1/3 (No output on stdout) stderr: connect to address 10.3.163.57 port 5666: No route to host 
check mailman api
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 1/5 (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:32:50 0d 0h 1m 45s 1/3 connect to address 10.3.163.57 and port 80: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 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
Disk_Space_/
CRITICAL 05-15-2024 22:33:51 0d 0h 0m 44s 1/3 (No output on stdout) stderr: connect to address 10.3.163.91 port 5666: No route to host 
Swap-Is-Low
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 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:32:49 0d 0h 1m 46s 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 1m 46s 1/7 (No output on stdout) stderr: connect to address 10.3.163.91 port 5666: No route to host 
rabbitmq03.iad2.fedoraproject.org
Check bus server alarms
CRITICAL 05-15-2024 22:32:50 0d 0h 1m 45s 1/3 (No output on stdout) stderr: connect to address 10.3.163.80 port 5666: No route to host 
Check bus server processes
CRITICAL 05-15-2024 22:32:51 0d 0h 1m 44s 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 1m 45s 1/3 (No output on stdout) stderr: connect to address 10.3.163.80 port 5666: No route to host 
Swap-Is-Low
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 1/4 (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 1m 45s 1/7 (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 1m 44s 1/3 (No output on stdout) stderr: connect to address 10.3.163.110 port 5666: No route to host 
Swap-Is-Low
CRITICAL 05-15-2024 22:32:49 0d 0h 1m 46s 1/4 (No output on stdout) stderr: connect to address 10.3.163.110 port 5666: No route to host 
mail_queue
CRITICAL 05-15-2024 22:32:50 0d 0h 1m 45s 1/7 (No output on stdout) stderr: connect to address 10.3.163.110 port 5666: No route to host 

Results 1 - 26 of 26 Matching Services