Fast ping check problem

Help
1

I enabled “fast ping check” according to the documentation by doing the following steps:

Adding $config[‘ping_rrd_step’] = 60; to the config-file

Running ./scripts/rrdstep.php -h all to fix the rrd steps

Adding the required cron-job

          • librenms /opt/librenms/ping.php >> /dev/null 2>&1

After this I checked the ping-perf.rrd files with rrdinfo and checked that the correct steps were changed

After this the poller “ping response” graphs were unreliable…
Running ping.php manually (with -v) I noticed that it reported this output:

Attempting to record data for 10.110.7.26… Success
Device 10.110.7.26 changed status to , running alerts
Rule #2 (Devices up/down): Status: NOCHG
Rule #3 (Port errors on important switchport): Status: NOCHG
Rule #4 (Palo Alto Networks passive firewall changed to active): Status: NOCHG
Rule #5 (Processor usage over 75%): Status: NOCHG
Rule #6 (Broadcast/Multicast Storm): Status: NOCHG
RRDtool Output: Attempting to record data for 10.110.7.10… Success
Device 10.110.7.10 changed status to , running alerts
Rule #4 (Palo Alto Networks passive firewall changed to active): Status: NOCHG
Rule #5 (Processor usage over 75%): Status: NOCHG
RRDtool Output: OK u:0.00 s:0.01 r:0.00
Attempting to record data for 10.110.5.10… Success
Device 10.110.5.10 changed status to , running alerts
Rule #4 (Palo Alto Networks passive firewall changed to active): Status: NOCHG
Rule #5 (Processor usage over 75%): Status: NOCHG
RRDtool Output: OK u:0.00 s:0.01 r:0.04
Attempting to record data for 10.110.7.37… Deferred
Attempting to record data for 10.110.5.18… Deferred
Attempting to record data for 10.110.5.17… Deferred

if i run ping.php -d -v it will show a report at the end that says:
Leftover devices, this shouldn’t happen: 10.110.7.37, 10.110.5.17, 10.110.5.16, 10.110.5.15, 10.110.5.14, 10.110.5.13, 10.110.5.31, 10.110.5.22,

It seems like it manages to record data for the first 2-4 devices when I run it… but the rest are Deferred…

Any idea what may be causing this ?

====================================

Component Version
LibreNMS 1.63-82-g1dd0d46ed
DB Schema 2020_04_19_010532_eventlog_sensor_reference_cleanup (164)
PHP 7.2.24-0ubuntu0.18.04.4
Python 3.6.9
MySQL 10.1.44-MariaDB-0ubuntu0.18.04.1
RRDTool 1.7.0
SNMP NET-SNMP 5.7.3

====================================

[OK] Composer Version: 1.10.6
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database schema correct

2

This means you have set up device dependencies. It will not record results until all parent devices have recorded results. Check that your device dependency is set up correctly within LibreNMS.

3

Ok, that explains parts of my question…
What about the latency graphs ? After I enable 1 minute pinging all latency graphs show random gaps, or no data at all…

4

So I noticed a few things…
if I add $config[‘ping_rrd_step’] = 60; to the config as per the instructions I kill all latency graphs. Looks like it assumes I’ll run the full poller every minute…
Is this a issue with dependencies ? The article does not mention that fast ping would not draw latency graphs if dependencies are in use ?

Also, It may be good to add that shutting down rrdcached while running ./scripts/rrdstep.php -h all is a good idea :smiley:

5

And to respond to my own problem…
Seems I solved this now.

The problem seems to have been that since rrdcached was running, and I changed the ping rrd files to 60 second steps, something broke… I temporarily put them back to 5 minute steps, shut down the rrdcached daemon, and changed them to 60 second steps, and then it worked…

May be a good idea to add that part to the guide…

6

Documentation updates are appreciated.