ConSol-Monitoring
BUG REPORT: snclient UNKNOWN
Describe the bug
It is a client server, I have several servers and what is happening to this server does not happen to them and I cannot find the error. Expected behavior
[2025-05-29 12:49:20.332][Debug][pid:8048][listener:411] http(s) request finished from: 192.168.0.5:58064 | duration: 1.0358236s | code: 200 | GET /query/check_process [2025-05-29 12:49:21.204][Debug][pid:8048][listen_web:357] failed to parse timeout: expandDuration: cannot parse duration, unknown format in 35.00 [2025-05-29 12:49:22.254][Debug][pid:8048][listen_web:357] failed to parse timeout: expandDuration: cannot parse duration, unknown format in 35.00 [2025-05-29 12:49:22.256][Debug][pid:8048][checkdata:142] filter: none [2025-05-29 12:49:22.256][Debug][pid:8048][checkdata:143] condition warning: state != 'running' [2025-05-29 12:49:22.256][Debug][pid:8048][checkdata:144] condition critical: state != 'running' [2025-05-29 12:49:22.256][Debug][pid:8048][checkdata:145] condition ok: none [2025-05-29 12:49:22.256][Debug][pid:8048][listener:411] http(s) request finished from: 192.168.0.5:58194 | duration: 1.8013ms | code: 200 | GET /query/check_service [2025-05-29 12:49:34.292][Debug][pid:8048][listen_web:357] failed to parse timeout: expandDuration: cannot parse duration, unknown format in 35.00 [2025-05-29 12:49:55.401][Debug][pid:8048][listen_web:357] failed to parse timeout: expandDuration: cannot parse duration, unknown format in 35.00
Name InterfaceDescription ifIndex Status MacAddress LinkSpeed
Ethernet Red Hat VirtIO Ethernet Adapter 8 Up BC-24-11-70-47-A3 10 Gbps
Screenshots
Only when I restart the client it is corrected for a few minutes and then the status changes again
and only passes 3 services
Software (please complete the following information): PS C:\Program Files\snclient> .\snclient.exe -V SNClient v0.34 (Build: 86853c0, go1.23.8) Architecture x86 Naemon 1.4.3 Almalinux 8.10 PVE: 8.3.0 Windows Server 2022 STD
Additional context PS C:\Program Files\snclient> .\snclient.exe run check_network device=Ethernet ←[0;37m[12:44:54.615][D] filter: none←[0m ←[0;37m[12:44:54.643][D] condition warning: total > 80GB←[0m ←[0;37m[12:44:54.647][D] condition critical: total > 90GB←[0m ←[0;37m[12:44:54.647][D] condition ok: none←[0m OK - Ethernet >0 B/s <0 B/s |'Ethernet_traffic_in'=63807023949c 'Ethernet_traffic_out'=161466465294c
i fixed the failed to parse timeout: expandDuration issue yesterday, but i am not sure if it's related to this issue. Could you give the currently development build a try?
@sistemmsn Now the 0.35 is also available: https://github.com/ConSol-Monitoring/snclient/releases/tag/v0.35
I already performed the update and there was no change
It's strange
[2025-06-18 17:17:05.348][Debug][pid:12344][checkdata:142] filter: none [2025-06-18 17:17:05.348][Debug][pid:12344][checkdata:143] condition warning: total > 80GB [2025-06-18 17:17:05.348][Debug][pid:12344][checkdata:144] condition critical: total > 90GB [2025-06-18 17:17:05.348][Debug][pid:12344][checkdata:145] condition ok: none [2025-06-18 17:17:05.348][Debug][pid:12344][listener:415] http(s) request finished from: 192.168.0.5:52592 | duration: 3h44m30.216372s | code: 200 | GET /query/check_network [2025-06-18 17:17:06.121][Debug][pid:12344][checkdata:142] filter: none [2025-06-18 17:17:06.121][Debug][pid:12344][checkdata:143] condition warning: count < 1 || count > 150 [2025-06-18 17:17:06.121][Debug][pid:12344][checkdata:144] condition critical: count < 0 || count > 200 [2025-06-18 17:17:06.121][Debug][pid:12344][checkdata:145] condition ok: none [2025-06-18 17:17:06.122][Debug][pid:12344][checkdata:466] metric count is WARNING [2025-06-18 17:17:06.122][Debug][pid:12344][listener:415] http(s) request finished from: 192.168.0.5:58860 | duration: 3h43m47.8797244s | code: 200 | GET /query/check_process [2025-06-18 17:17:06.254][Debug][pid:12344][checkdata:142] filter: none [2025-06-18 17:17:06.254][Debug][pid:12344][checkdata:143] condition warning: total > 80GB [2025-06-18 17:17:06.254][Debug][pid:12344][checkdata:144] condition critical: total > 90GB [2025-06-18 17:17:06.254][Debug][pid:12344][checkdata:145] condition ok: none [2025-06-18 17:17:06.255][Debug][pid:12344][listener:415] http(s) request finished from: 192.168.0.5:38158 | duration: 3h43m31.1149124s | code: 200 | GET /query/check_network [2025-06-18 17:17:07.016][Debug][pid:12344][checkdata:142] filter: none [2025-06-18 17:17:07.016][Debug][pid:12344][checkdata:143] condition warning: count < 1 || count > 150 [2025-06-18 17:17:07.016][Debug][pid:12344][checkdata:144] condition critical: count < 0 || count > 200 [2025-06-18 17:17:07.016][Debug][pid:12344][checkdata:145] condition ok: none [2025-06-18 17:17:07.018][Debug][pid:12344][checkdata:466] metric count is WARNING [2025-06-18 17:17:07.018][Debug][pid:12344][listener:415] http(s) request finished from: 192.168.0.5:41996 | duration: 5h39m48.7890745s | code: 200 | GET /query/check_process [2025-06-18 17:17:28.503][Debug][pid:12344][check_ntp_offset:97] failed: timedatectl: timedatectl is a linux command [2025-06-18 17:17:28.503][Debug][pid:12344][check_ntp_offset:109] failed: chronyc: chronyc is a linux command [2025-06-18 17:17:28.503][Debug][pid:12344][check_ntp_offset:121] failed: ntpq: ntpq is not available on windows [2025-06-18 17:17:28.506][Debug][pid:12344][checkdata:142] filter: none [2025-06-18 17:17:28.506][Debug][pid:12344][checkdata:143] condition warning: total > 90 [2025-06-18 17:17:28.506][Debug][pid:12344][checkdata:144] condition critical: total > 95 [2025-06-18 17:17:28.506][Debug][pid:12344][checkdata:145] condition ok: none [2025-06-18 17:17:28.506][Debug][pid:12344][checkdata:142] filter: none [2025-06-18 17:17:28.506][Debug][pid:12344][checkdata:143] condition warning: state != 'running' [2025-06-18 17:17:28.506][Debug][pid:12344][checkdata:144] condition critical: state != 'running' [2025-06-18 17:17:28.506][Debug][pid:12344][checkdata:145] condition ok: none [2025-06-18 17:17:28.506][Debug][pid:12344][listener:415] http(s) request finished from: 192.168.0.5:41354 | duration: 0s | code: 200 | GET /query/check_cpu_utilization
i am unable to reproduce this here. It also seems not related to a specific check, since different checks all run into a timeout. Could this be a firewall issue?
Hi, just a guess and I might be wrong, but I would check locales (aka "regional settings") on affected server and compare it with other working servers. Seems to me, there is a problem with DATE parsing (and crappy win localize all dates using "regional settings" ).
