I am running CheckMK 2.0 and trying to monitor some old Windows machines which are Windows Server 2003. However, CheckMK agent reports this issue constantly:
"[agent] Communication failed: [Errno 104] Connection reset by peer**CRIT** , Got no information from host, execution time 0.1 sec"
From the doc, it seems CheckMK 2.0 does not support Windows Server 2003 and there is one suggestion is to use old version of CheckMK agent 1.2.8. I tried with this agent version and it works for few days and then, it backs to the same issue.
Could you please give me some advices how I could tackle with this issue? Thank you so much!
Well, you shouldn’t have to go back to the 1.2.8 version of the agent. I believe the 1.6 versions will work as well (and at least they’re still in support).
When you get the error message, can you verify that the Check MK Service is running? Even if so you may want to give it a restart and see if that fixes your issue.
Also, if possible upgrade to a more recent version of Windows, as running Win 2003 is a security risk.
Unfortunately, there is no compatibily mode available. I figure out that there is an exe file for CheckMK agent 2003 but when i run with install, it says this:
Hmmm, that’s annoying indeed. So, the 1.6 version’s not going to work. So you’re stuck using the legacy agent then (pre 1.6). You can download 1.5.25 from the archive:
From the Debian or RPM package you can extract the installer for the client. Hopefully that will solve your issue.
This is actually “working” or lets say " ‘not working’ as designed" - there is officially no support for Windows 2003 from 1.6 on ward The agent for Windows in detail
I managed to install version 1.5 agent and it worked an hour after that. However, it then died
“[agent] Communication failed: [Errno 104] Connection reset by peerCRIT , Got no information from host, execution time 0.1 sec”
Then, after i restarted the service, it works nicely until now (more than 1 day already).
May i know what do you think about this? Would it be the issue with CheckMK agent itself or connectivity?
Well, at least glad to hear that it’s working now.
As for the cause, I can’t be sure. But I suspect the agent. If the connectivity dies and comes back, CheckMK should pick that up and report everything OK again. Since just restarting the agent service (and assuming you changed nothing connection wise) fixed the issue I believe your connectivity is OK.
Still, my best advise would be to upgrade that Win2003 server to a more recent version if that’s possible. Such unsupported operating systems are a huge security risk.
For now, I do hope it’ll keep on running without any more problems for you.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.
