Current Network Status
Last Updated: Mon Nov 10 22:34:26 UTC 2025
Updated every 90 seconds
Nagios® Core™ 4.4.14 - www.nagios.org
Logged in as guest
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
71 1 0 0
All Problems All Types
1 72
Service Status Totals
Ok Warning Unknown Critical Pending
364 0 0 8 0
All Problems All Types
8 372
Display Filters:
Host Status Types:All
Host Properties:Any
Service Status Types: Critical
Service Properties:Any
Service Status Details For Host Group 'hardware'
Entries sorted by service status (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
bvmhost-p10-01.rdu3.fedoraproject.org
This host problem has been acknowledgedThis host has 1 comment associated with it
Cron Daemon
CRITICAL 11-10-2025 22:24:36 4d 17h 59m 49s 1/3 (No output on stdout) stderr: connect to address 10.16.163.135 port 5666: No route to host 
Disk Space /boot
CRITICAL 11-10-2025 22:04:36 4d 17h 59m 49s 1/3 (No output on stdout) stderr: connect to address 10.16.163.135 port 5666: No route to host 
Disk_Space_/
CRITICAL 11-10-2025 22:04:36 4d 17h 59m 49s 1/3 (No output on stdout) stderr: connect to address 10.16.163.135 port 5666: No route to host 
Rsyslogd Process
CRITICAL 11-10-2025 22:24:36 4d 17h 59m 49s 1/3 (No output on stdout) stderr: connect to address 10.16.163.135 port 5666: No route to host 
SSH-virtservers
CRITICAL 11-10-2025 22:24:36 4d 17h 59m 49s 1/3 connect to address 10.16.163.135 and port 22: No route to host 
Total Processes
CRITICAL 11-10-2025 22:24:36 4d 17h 59m 49s 1/3 (No output on stdout) stderr: connect to address 10.16.163.135 port 5666: No route to host 
Zombie Processes
CRITICAL 11-10-2025 22:24:36 4d 17h 59m 49s 1/3 (No output on stdout) stderr: connect to address 10.16.163.135 port 5666: No route to host 
mail_queue
CRITICAL 11-10-2025 22:24:36 4d 17h 59m 49s 1/7 (No output on stdout) stderr: connect to address 10.16.163.135 port 5666: No route to host 

Results 1 - 8 of 8 Matching Services