Display Filters: | Host Status Types: | All | Host Properties: | Any |
Service Status Types: | All Problems | Service Properties: | Any |
|
|
Service Status Details For All Hosts
Entries sorted by service status (descending)
|
|
Host | Service | Status | Last Check | Duration | Attempt | Status Information |
|
|
CRITICAL |
05-02-2024 18:58:06 |
7d 6h 10m 5s |
3/3 |
PROCS CRITICAL: 0 processes with command name 'fedmsg-hub', UID = 995 (fedmsg) |
|
|
|
|
CRITICAL |
05-02-2024 18:56:07 |
2d 4h 52m 4s |
3/3 |
CRIT: no fedbadges messages in 259200 seconds |
|
|
|
|
CRITICAL |
05-02-2024 18:56:23 |
0d 0h 1m 48s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
CRITICAL |
05-02-2024 18:51:31 |
0d 0h 16m 40s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
CRITICAL |
05-02-2024 18:48:47 |
0d 0h 19m 24s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
CRITICAL |
05-02-2024 18:56:25 |
0d 0h 11m 46s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
CRITICAL |
05-02-2024 18:51:27 |
0d 0h 16m 44s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
CRITICAL |
05-02-2024 18:48:50 |
0d 0h 19m 21s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
CRITICAL |
05-02-2024 18:49:02 |
0d 0h 19m 9s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
CRITICAL |
05-02-2024 18:55:57 |
0d 0h 17m 14s |
1/3 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:53:59 |
0d 0h 19m 12s |
1/3 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:53:58 |
0d 0h 19m 13s |
1/3 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:54:36 |
0d 0h 18m 35s |
1/10 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:54:46 |
0d 0h 18m 25s |
1/10 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:54:14 |
0d 0h 18m 57s |
8/8 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:57:13 |
0d 0h 15m 58s |
1/3 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:56:14 |
0d 0h 16m 57s |
1/8 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:55:48 |
0d 0h 17m 23s |
1/8 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:55:50 |
0d 0h 17m 21s |
1/3 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:55:21 |
0d 0h 17m 50s |
1/8 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:55:24 |
0d 0h 17m 47s |
1/8 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:52:43 |
0d 0h 15m 28s |
1/8 |
CRITICAL - Socket timeout |
|
|
CRITICAL |
05-02-2024 18:48:58 |
0d 0h 19m 13s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
CRITICAL |
05-02-2024 18:49:06 |
0d 0h 19m 5s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
|
|
|
|
CRITICAL |
05-02-2024 18:54:09 |
0d 20h 4m 2s |
3/3 |
RABBITMQ_QUEUE CRITICAL - messages CRITICAL (99192), messages_ready OK (99142) messages_unacknowledged OK (50) consumers OK (2) |
|
|
|
|
UNKNOWN |
05-02-2024 18:51:33 |
7d 2h 56m 58s |
3/3 |
UNKNOWN - ZMQ timeout. No message received in 20000 ms |
|
|
UNKNOWN |
05-02-2024 18:56:36 |
7d 6h 11m 55s |
3/3 |
UNKNOWN - ZMQ timeout. No message received in 20000 ms |
|
|
UNKNOWN |
05-02-2024 18:51:48 |
7d 6h 16m 44s |
3/3 |
UNKNOWN - ZMQ timeout. No message received in 20000 ms |
|
|
|
|
WARNING |
05-02-2024 18:54:40 |
13d 12h 33m 31s |
3/3 |
DISK WARNING - free space: / 85460 MiB (11.99% inode=100%): |
|
|
|
|
WARNING |
05-02-2024 18:32:15 |
0d 0h 25m 56s |
3/3 |
DISK WARNING - free space: /srv/registry 701677 MiB (19.99% inode=97%): |