Hi Alex,
> TBH, I'm really not sure. Those settings look fine to me. If I had to
> guess I'd say this was caused by network issues, where the plugin, for
> some reason, is unable to connect to the host every so often. I'm not
> sure a longer timeout would help. Are there any unreliable points in t
TBH, I'm really not sure. Those settings look fine to me. If I had to
guess I'd say this was caused by network issues, where the plugin, for
some reason, is unable to connect to the host every so often. I'm not
sure a longer timeout would help. Are there any unreliable points in the
network bet
Hi,
> How are you connecting to these boxes (what check commands are you using)?
For clamd, I'm using "check_nrpe!check_procs_clamd" on the nagios side
and the following on the client side:
command[check_procs_clamd]=/usr/lib64/nagios/plugins/check_clamd -H
/var/spool/amavisd/clamd.sock
For smt
How are you connecting to these boxes (what check commands are you using)?
Alex Griffin
---
Tech Team
agrif...@nagios.com
Alex wrote:
> Hi,
>
> I have a few fc16 boxes and often times alerts are generated for
> timeouts while connecting to a remote service on a client such as
> clamd or smtpd:
>
Hi,
I have a few fc16 boxes and often times alerts are generated for
timeouts while connecting to a remote service on a client such as
clamd or smtpd:
PROCS CRITICAL: 0 processes with command name 'smtpd', UID = 89 (postfix)
Why is it that this happens? It doesn't happen all the time. I know
the
