On Dec 15, 2007 11:13 AM, Paul Lathrop <[EMAIL PROTECTED]> wrote:
> Roger,
>
> What kernel version are you running? When I was using Nagios on some
> rather old kernels, there was a kernel bug that made this happen after
> the system had been up for a certain amount of time. The easiest way
> to check for this is to reboot the machine and see if the message goes
> away.
>
> The fix for this was to upgrade our kernel. Since that wasn't an
> option for us at the time we settled for rebooting the machine every
> few months when this started happening. Inelegant, but it worked.
Thank you, Paul. This makes sense, considering the fact that this is on
some really old RHEL boxes. I, like you, can't easily upgrade them while
they're in production. I suppose that if the cluster (via Coyote Point) is
working ok, then traffic should be diverted to other boxes for the duration
of the bounce.
(fingers crossed!)
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
