[solved] Timeout error when calling ss_host_disk.php

[WiredWorm]

Hi there,

I've got a slightly strange issue when monitoring disk usage on a number of our Proliant Servers.

I've checked the configuration and it's really quite strange.

In the log I see this error:

06/13/2011 10:05:10 AM - CMDPHP: Poller[0] WARNING: SNMP Get Timeout for Host:'xxxxxxxxxxxx', and OID:'.1.3.6.1.2.1.25.2.3.1.6.3'

And just prior to this I see this command running:

06/13/2011 10:05:09 AM - PHPSVR: Poller[0] DEBUG: PID[948] CTR[0] INC: 'ss_host_disk.php' FUNC: 'ss_host_disk' PARMS: 'xxxxxxxxx 16 1:161:500:1:10:public:::::: get used 3'

The strange thing is that if I run ss_host_disk.php manually using the parameters given then it works and returns a valid value so i'm a bit at a loss as to why it fails during a normal polling cycle.

My first instinct was to increase the timeout value from 500ms to 1000ms but it doesn't seem to matter what values I put in the UI it still uses a 500ms timeout. Is there somewhere else I need to change it? I've updated the Cacti default and also edited the value on the host.

Grateful for any pointers people might be able to offer.

Cheers

Pete

[noname]

My first instinct was to increase the timeout value from 500ms to 1000ms but it doesn't seem to matter what values I put in the UI it still uses a 500ms timeout.

That's strange.
In "Console -> System Utilities -> View Poller Cache", what do you see for ss_host_disk.php after you changed SNMP timeout?
(Usually the changes will be applied automatically, but try "Rebuild Poller Cache" if that isn't changed).

[WiredWorm]

Ooops, it was a case of PEBKAC.

I had a number of tests which were failing but had only updated the poll interval on one of them - the 'bad' result I was seeing was for one of the remaining tests which i'd failed to update. Doh!!

I've changed them all to 1000ms and now it works perfectly.

Thanks for the pointer on the Poller Cache though. I hadn't looked in there before and it contains all kind of useful stuff.