On 03/27/2013 07:16 PM, Rob J. Epping wrote:
I'm planning to test with the old isPingable in the very near future to verify if this change is the cuase.
I changed isPingable back to how it was implemented before r3728 and it it has been quiet since ... So quiet I verified isPingable really did what it was supposed to do, which it did. 1 host down/up in 1,5 hours instead of many.
Any hints / help how to debug this?
One ping commonly fails, it is recommended to use 3 ping. Use config options: // PING Settings - Retries/Timeouts #$config['ping_retries'] = 3; // How many times to retry ping #$config['ping_timeout'] = 500; // Timeout in milliseconds
For debug uncomment line 421 in file includes/functions.php (look for line "Uncomment this line for DEBUG isPingable") and then see errors in the file /tmp/pings_debug.log
Difference in function isPingable() before r3728 that it did not show the response time and now there are options ping retries and timeout.
I would appreciate if you send me output of your debug, if you have an ongoing problem with the frequent change of status. And tell if situation will improve if you set the option $config['ping_timeout'] = 1000 (or more).
My oberservium install has 262 devices and 3281 ports and runs on a VM with Debian 6, 4 cores and 1,5G RAM all software is recent.