Connection Loss

[ednaldojta]

Hello friends,

I have a server that is being monitored, however minutely, it loses the connection to a service. This happens with all the services that specific server. It is a Windows server, and the alert message of the missed connection is: Plugin Critical After 10 seconds.

[bwallace]

Do you mean "CRITICAL - Plugin timed out after 10 seconds"
Depending on the plugin you are using you may be able to increase it's timeout rate, try looking at the plugins help text. Plugins like check_nrpe can use a "-t" flag to increase timeout, such as "-t 30" for 30 seconds.
If in any doubt, please post the full check command and the corresponding error - thanks -

[ednaldojta]

the plugin is NSClient

[bwallace]

NSClient++ -- Ok, but can you post the full check command(s) please?

[ednaldojta]

They are all services. Please find attached the services that are with this problem.
command:
/ Check_nt -H $ HostAddress $ -s "$ ARG1 $" -p 12489 -l -v USEDDISKSPACE C -w 80 -c 95

[bwallace]

Try increasing the timeout to 60 sec using this option in your check command '-t 60'

....-p 12489 -t 60 -l -v USEDDISKSPACE -l C -w 80% -c 90%

[ednaldojta]

Good morning mate,
the problem still persists. Only this server. And as already mentioned, are all services, interleaved times. Any more suggestions?

[rkennedy]

What does the error say now? Is it still timing out after 10 seconds, or now 60 seconds?

[ednaldojta]

Still the same mistake! 10 seconds

[rkennedy]

It sounds like the change @bwallace mentioned wasn't applied, to increase the timeout it's depending on the -t parameter. As it's still saying 10 seconds, I don't think it's being followed. Did you apply configuration after making the change?

Code: Select all

[root@localhost libexec]# ./check_nt -H 192.168.5.47 -p 12489 -v USEDDISKSPACE -d SHOWALL -l c
CRITICAL - Socket timeout after 10 seconds

[root@localhost libexec]# ./check_nt -H 192.168.5.47 -p 12489 -v USEDDISKSPACE -d SHOWALL -l c -t 20
CRITICAL - Socket timeout after 20 seconds

As you can see, the error changed when I adjusted the timeout value to 20.