|
Service Status Details For All Host Groups
|
|
Host   | Service   | Status   | Last Check   | Duration   | Attempt   | Status Information |
|
|
OK |
07-03-2025 16:55:36 |
0d 0h 13m 9s |
1/3 |
CHECK_NRPE: Invalid packet version received from server. |
|
|
OK |
07-03-2025 16:48:55 |
0d 0h 9m 49s |
1/3 |
Charge CPU 0% (1 moyenne minimale) 0% (5 moyenne minimale) 0% (15 moyenne minimale) |
|
|
OK |
07-03-2025 16:55:36 |
0d 0h 13m 9s |
1/3 |
C: - total: 278,81 Gb - utilisé: 154,75 Gb (56%) - libre 124,06 Gb (44%) |
|
|
OK |
07-03-2025 16:53:45 |
0d 0h 14m 59s |
1/3 |
D: - total: 837,97 Gb - utilisé: 744,32 Gb (89%) - libre 93,65 Gb (11%) |
|
|
OK |
07-03-2025 16:55:35 |
0d 0h 13m 9s |
1/3 |
nscp.exe: Running |
|
|
OK |
07-03-2025 16:55:35 |
0d 0h 13m 9s |
1/3 |
e.magnus.exe: Running, e.magnus.exe: Running, e.magnus.exe: Running, e.magnus.exe: Running, e.magnus.exe: Running |
|
|
OK |
07-03-2025 16:48:45 |
0d 0h 9m 59s |
1/3 |
Memory usage: total:56190,60 MB - used: 25263,79 MB (45%) - free: 30926,80 MB (55%) |
|
|
OK |
07-03-2025 16:55:36 |
0d 0h 13m 9s |
1/3 |
nscp: Started |
|
|
OK |
07-03-2025 16:54:05 |
0d 0h 14m 39s |
1/3 |
System Uptime - 0 day(s) 18 hour(s) 48 minute(s) |
|
|
OK |
07-03-2025 16:53:45 |
0d 0h 14m 59s |
1/3 |
NSClient++ 0.5.2.35 2018-01-28 |
|
|
OK |
07-03-2025 16:54:06 |
0d 0h 14m 38s |
1/3 |
OK - no pending updates. |
|
|
|
|
OK |
07-03-2025 16:56:55 |
0d 6h 23m 59s |
1/3 |
"Volume 1" status:Normal |
|
|
OK |
07-03-2025 16:56:37 |
0d 1h 59m 10s |
1/3 |
Synology model: "RS819" |
|
|
OK |
07-03-2025 16:54:44 |
0d 0h 46m 15s |
1/3 |
Number of disks: 4 |
|
|
OK |
07-03-2025 16:56:55 |
0d 6h 23m 59s |
1/3 |
DSM Version: "DSM 7.2-72806" |
|
|
|
|
OK |
07-03-2025 16:58:05 |
0d 0h 10m 39s |
1/3 |
OK - load average: 0.00, 0.00, 0.00 |
|
|
OK |
07-03-2025 16:48:55 |
0d 0h 9m 49s |
1/3 |
DISK OK - free space: / 5274 MB (52% inode=93%): |
|
|
CRITICAL |
07-03-2025 16:53:45 |
36d 16h 47m 8s |
3/3 |
APT CRITICAL: 11 packages available for upgrade (11 critical updates). |
|
|
OK |
07-03-2025 16:57:26 |
0d 0h 11m 19s |
1/3 |
PROCS OK: 63 processes |
|
|
OK |
07-03-2025 16:58:40 |
0d 0h 10m 4s |
1/3 |
PROCS OK: 0 processes with STATE = Z |
|
|
OK |
07-03-2025 16:56:55 |
0d 0h 11m 49s |
1/3 |
SSH OK - OpenSSH_8.4p1 Debian-5+deb11u5 (protocol 2.0) |
|
|
OK |
07-03-2025 16:57:05 |
0d 0h 11m 39s |
1/3 |
SWAP OK - 100% free (975 MB out of 975 MB) |
|
|
|
|
OK |
07-03-2025 16:48:55 |
0d 0h 9m 49s |
1/3 |
CHECK_NRPE: Invalid packet version received from server. |
|
|
OK |
07-03-2025 16:55:15 |
0d 0h 13m 29s |
1/3 |
Charge CPU 0% (1 moyenne minimale) 0% (5 moyenne minimale) 0% (15 moyenne minimale) |
|
|
OK |
07-03-2025 16:55:25 |
0d 0h 13m 19s |
1/3 |
C: - total: 119,46 Gb - utilisé: 98,33 Gb (82%) - libre 21,13 Gb (18%) |
|
|
OK |
07-03-2025 16:55:25 |
0d 0h 13m 19s |
1/3 |
Memory usage: total:3583,58 MB - used: 1446,93 MB (40%) - free: 2136,65 MB (60%) |
|
|
OK |
07-03-2025 16:55:15 |
0d 0h 13m 29s |
1/3 |
System Uptime - 14 day(s) 14 hour(s) 53 minute(s) |
|
|
OK |
07-03-2025 16:55:25 |
0d 0h 13m 19s |
1/3 |
NSClient++ 0.5.2.35 2018-01-28 |
|
|
OK |
07-03-2025 16:51:38 |
0d 0h 17m 6s |
1/3 |
OK - no pending updates. |
|
|
|
|
OK |
07-03-2025 16:56:00 |
0d 0h 12m 44s |
1/3 |
Charge CPU 1% (1 moyenne minimale) 2% (5 moyenne minimale) 2% (15 moyenne minimale) |
|
|
OK |
07-03-2025 16:55:15 |
0d 0h 13m 29s |
1/3 |
C: - total: 499,46 Gb - utilisé: 417,74 Gb (84%) - libre 81,73 Gb (16%) |
|
|
OK |
07-03-2025 16:58:40 |
0d 0h 10m 4s |
1/3 |
Memory usage: total:24063,69 MB - used: 16954,79 MB (70%) - free: 7108,91 MB (30%) |
|
|
OK |
07-03-2025 16:55:10 |
0d 0h 13m 34s |
1/3 |
System Uptime - 3 day(s) 22 hour(s) 35 minute(s) |
|
|
OK |
07-03-2025 16:48:55 |
0d 0h 9m 49s |
1/3 |
NSClient++ 0.5.2.35 2018-01-28 |
|
|
CRITICAL |
07-03-2025 16:52:57 |
0d 0h 35m 48s |
3/3 |
Updates: 39 critical, 0 optional |
|
|
|
|
OK |
07-03-2025 16:58:40 |
0d 0h 10m 4s |
1/3 |
OK - load average: 0.00, 0.00, 0.00 |
|
|
OK |
07-03-2025 16:48:40 |
0d 0h 10m 4s |
1/3 |
DISK OK - free space: / 12227 MB (91% inode=96%): |
|
|
OK |
07-03-2025 16:58:40 |
0d 0h 10m 4s |
1/3 |
APT OK: 0 packages available for upgrade (0 critical updates). |
|
|
OK |
07-03-2025 16:55:15 |
0d 0h 13m 29s |
1/3 |
PROCS OK: 96 processes |
|
|
OK |
07-03-2025 16:55:15 |
0d 0h 13m 29s |
1/3 |
PROCS OK: 0 processes with STATE = Z |
|
|
OK |
07-03-2025 16:56:35 |
0d 0h 12m 9s |
1/3 |
SSH OK - OpenSSH_7.9p1 Debian-10+deb10u2 (protocol 2.0) |
|
|
OK |
07-03-2025 16:56:24 |
0d 0h 12m 20s |
1/3 |
SWAP OK - 100% free (2045 MB out of 2045 MB) |
|
|
|
|
OK |
07-03-2025 16:58:25 |
919d 22h 8m 27s |
1/3 |
L'onduleur est alimenté par le secteur |
|
|
OK |
07-03-2025 16:48:55 |
919d 22h 8m 22s |
1/3 |
OK - Batterie restantee = % |
|
|
|
|
OK |
07-03-2025 16:54:55 |
919d 22h 46m 1s |
1/3 |
L'onduleur est alimenté par le secteur |
|
|
OK |
07-03-2025 16:56:55 |
919d 22h 52m 47s |
1/3 |
OK - Batterie restantee = % |
|
|
|
|
OK |
07-03-2025 16:54:26 |
919d 23h 3m 41s |
1/3 |
L'onduleur est alimenté par le secteur |
|
|
OK |
07-03-2025 16:54:55 |
920d 0h 6m 46s |
1/3 |
OK - Batterie restantee = % |
|
|
|
|
OK |
07-03-2025 16:55:45 |
919d 1h 51m 5s |
1/3 |
L'onduleur est alimenté par le secteur |
|
|
OK |
07-03-2025 16:54:40 |
919d 1h 50m 58s |
1/3 |
OK - Batterie restantee = % |
|
|
|
|
UNKNOWN |
07-03-2025 16:35:14 |
0d 0h 23m 30s |
1/2 |
ERROR: No snmp response from 192.168.1.123 (alarm) |
|
|
|
|
UNKNOWN |
07-03-2025 16:57:35 |
0d 0h 31m 9s |
1/2 |
ERROR: No snmp response from 192.168.1.121 (alarm) |
|
|
|
|
UNKNOWN |
07-03-2025 16:38:24 |
0d 0h 20m 20s |
1/2 |
ERROR: No snmp response from 192.168.6.210 (alarm) |
|
|
|
|
UNKNOWN |
07-03-2025 16:29:20 |
0d 0h 29m 24s |
1/2 |
ERROR: No snmp response from 192.168.1.122 (alarm) |
|
|
|
|
CRITICAL |
07-03-2025 16:55:55 |
0d 0h 32m 49s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:57:25 |
0d 0h 31m 19s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:34 |
0d 0h 32m 10s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:57:25 |
0d 0h 31m 19s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:57:45 |
0d 0h 30m 59s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:51:55 |
0d 0h 26m 49s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. |
|
|
|
|
CRITICAL |
07-03-2025 16:56:25 |
0d 0h 32m 19s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:55:45 |
0d 0h 32m 59s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:55:15 |
0d 0h 33m 29s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:55:45 |
0d 0h 32m 59s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:54:35 |
0d 0h 34m 9s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:54:06 |
0d 0h 34m 38s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. |
|
|
|
|
CRITICAL |
07-03-2025 16:55:45 |
0d 0h 32m 59s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:58:25 |
0d 0h 30m 19s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:48:50 |
0d 0h 29m 54s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:57:05 |
0d 0h 31m 39s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:55 |
0d 0h 31m 49s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:00 |
0d 0h 32m 44s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. |
|
|
|
|
CRITICAL |
07-03-2025 16:56:45 |
0d 0h 31m 59s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:55:35 |
0d 0h 33m 9s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:45 |
0d 0h 31m 59s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:15 |
0d 0h 32m 29s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:00 |
0d 0h 32m 44s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:15 |
0d 0h 32m 29s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. |
|
|
|
|
CRITICAL |
07-03-2025 16:57:49 |
0d 0h 30m 55s |
1/3 |
(No output on stdout) stderr: connect to address 192.168.3.35 port 5666: No route to host |
|
|
CRITICAL |
07-03-2025 16:56:34 |
0d 0h 32m 10s |
1/3 |
(No output on stdout) stderr: connect to address 192.168.3.35 port 5666: No route to host |
|
|
CRITICAL |
07-03-2025 16:53:45 |
0d 0h 35m 9s |
3/3 |
(No output on stdout) stderr: connect to address 192.168.3.35 port 5666: No route to host |
|
|
CRITICAL |
07-03-2025 16:55:35 |
0d 0h 33m 9s |
3/3 |
(No output on stdout) stderr: connect to address 192.168.3.35 port 5666: No route to host |
|
|
CRITICAL |
07-03-2025 16:56:34 |
0d 0h 32m 10s |
1/3 |
(No output on stdout) stderr: connect to address 192.168.3.35 port 5666: No route to host |
|
|
CRITICAL |
07-03-2025 16:55:15 |
0d 0h 33m 29s |
1/3 |
connect to address 192.168.3.35 and port 22: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
07-03-2025 16:57:25 |
0d 0h 31m 19s |
1/3 |
(No output on stdout) stderr: connect to address 192.168.3.35 port 5666: No route to host |
|
|
|
|
CRITICAL |
07-03-2025 16:56:55 |
0d 0h 31m 49s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:55:35 |
0d 0h 33m 9s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:55 |
0d 0h 31m 49s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:55:45 |
0d 0h 32m 59s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:36 |
0d 0h 32m 8s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:48:48 |
0d 0h 29m 56s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. |
|
|
|
|
CRITICAL |
07-03-2025 16:57:35 |
0d 0h 31m 9s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:56:45 |
0d 0h 31m 59s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:55:45 |
0d 0h 32m 59s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:55:45 |
0d 0h 32m 59s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:57:25 |
0d 0h 31m 19s |
1/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
07-03-2025 16:52:25 |
0d 0h 26m 19s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. |
|
|
|
|
CRITICAL |
07-03-2025 16:55:35 |
0d 0h 33m 9s |
3/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
CRITICAL |
07-03-2025 16:56:00 |
0d 0h 32m 44s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
CRITICAL |
07-03-2025 16:57:05 |
0d 0h 31m 39s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
CRITICAL |
07-03-2025 16:54:35 |
0d 0h 34m 9s |
1/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
Results 0 - 100 of 787 Matching Services