Service Check Timeout

[RDMaroto]

Good morning,
For different monitorings of my remote machines, the following error appears:
Service Check Out Time.

I have read that the way to solve it was changing the value in nagios.cfg
service check time out

And in my remote machine in nrpe.cfg, the value of
command_timeout.
Is this correct?
What values ​​get?

[RDMaroto]

Actually my service_check_timeout=60

[tmcdonald]

What specific check are you running? Sometimes you need to set a higher timeout value for the plugin itself.

[RDMaroto]

Good morning,

The problem is that in the network where nagios monitors, every night, the backup of all machines is done.
The flow of information is enormous and is saturated.

Think convenient xinetd restart every night, before the backup?

Last night, I changed the service_check_timeout to 600.
There are less alert, but should not skip any.

Thanks for you reply.
Regards

[sreinhardt]

Considering the timespan and regular timing of this, would you be open to using scheduled downtimes to avoid the additional and somewhat misleading alerts?

[RDMaroto]

Good morning,

The Monitoring should be 24 hours all days.
Tonight I scheduled a restart of xinetd, but have continued to appear alerts check_nrpe socket timeout.

It is very important not to have this type of alert.
How I can solve it?

Thanks for your time.
Regards

[slansing]

That is why you have the ability to schedule downtime, if you can reliably find the time that this happens at you can schedule downtime for a short period then. You will still be able to see what happened on the remote host, you will just not be notified about it. There is no real easy way to exclude critical notifications that have a certain wording, in this case, a timeout, because to nagios, a critical is a critical.