Critical: Plugin timed out

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
manimurugesan
Posts: 145
Joined: Wed Oct 03, 2018 9:15 am

Critical: Plugin timed out

Post by manimurugesan »

Hi Team,

We are monitoring linux using ssh ,and frequently getting plugin timed out error ,some times it's clearing automatically.

but some times it's never clearing and showing critical plugin timed out(check_by_ssh) .when i check script which we are using that's fine and it's working for other servers but some servers it's showing Critical: plugin timed out .

i tried increasing time out and checked but that's not working

'could you please clarify what it's exactly referring critical:Plugin timed out,what will be the trouble shooting steps for this in linux?
User avatar
kfanselow
Posts: 254
Joined: Tue Aug 31, 2021 3:25 pm

Re: Critical: Plugin timed out

Post by kfanselow »

Hi manimurugesan,

The timeout means that the plugin did not receive data in the expected time window. Causes can include network issues, extended authentication delays (e.g. name resolution problems on the target system) or the command/script on the target system is taking too long to run. For example:

1) Example of a timeout while trying to connect to a system that is down ( note the 2 second timeout for brevity sake)

Code: Select all

/usr/local/nagios/libexec/check_by_ssh -t 2 -H xxx.xxx.xxx.235 -l testuser -C 'uname -a '
CRITICAL - Plugin timed out

2) Example of an authentication delay causing the timeout.

Code: Select all

/usr/local/nagios/libexec/check_by_ssh -t 10 -H xxx.xxx.xxx.227 -l testuser -C 'sleep 3' 
[email protected]'s password: CRITICAL - Plugin timed out

3) Example of a command taking longer than the timeout value (note the timeout is 10 and the sleep command is 12).

Code: Select all

/usr/local/nagios/libexec/check_by_ssh -t 10 -H xxx.xxx.xxx.227 -l testuser -C 'sleep 12' 

[email protected]'s password:
CRITICAL - Plugin timed out

So the next steps for troubleshooting to is to look and see if there is a pattern such as time of day, system load, and network activity that correlates with the problem and then run the check commands manually (as done above) during those windows to see if you can identify where the problem is occurring.

Please let us know how it goes.

P.S. - I am sending you a PM with some specific information for your organization ***
Locked