Joseph,
same questions.. you get this issue on latest stable (r5889) or latest trunk?
if yes, then send me debug output for any device with high polling time: ./poller.php -d -h your_device
changes in r5884, can't create such problems.
On Tue, Oct 21, 2014 at 6:27 PM, Joseph Zancocchio joseph@nyi.net wrote:
I believe I have been experiencing the same issue with the latest stable update, and have narrowed down the problem I have seen to the changes made in revision 5884. Can you try to svn up -r 5883 (make sure to switch to the current branch if you are using the stable currently) and see if everything works, and if so, svn up -r 5884 to see if the behavior returns?
-Joe
On 10/21/2014 06:26 AM, Mike Stupalov wrote:
On 21.10.2014 14:03, Rutger Bevaart wrote:
Hi,
Updated to the latest svn version yesterday, after which I immediately had issues with the poller. Updated from a release about two weeks older. Now I get up/down for different devices, sometimes complete BGP neighbours down on others. Device down alerts on snmp, etc.
I increased the number of poller processes in the crontab and increased snap timeout values etc. However, I still have graphs with large parts missing because of this. Checked poller times, kept an eye on the processes running and logs. Some devices take 120s to poll completely, but all polling is done in about 2 minutes. Still I get these errors, other than the upgrade no changes have been made to firewalls, policies, etc.
Any clues? Do I need to upgrade php?
Show your crontab. How many memory on observium host.
Send debug output for one device (with long polling time): ./poller.php -d -h some_device > /tmp/debug_poller
(Do not sent this output to list) ;)
Regards, Rutger
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium