pping creates multiple RRD files for same data, causing ipdevinfo to display availability as N/A

[Morten Brekkevold]

If a device's sysname/dnsname changes, pping will create a new RRD file for the netbox entry, and also a second entry in the rrd_file table. pping will keep logging to the new file, while the old file turns stale.

Since there are now two pping entries for the device in the rrd_file table, ipdevinfo will not know which file to calculate the device's availability statistics from. Depending on the order things come out of the database, ipdevinfo may choose the stale file, resulting in a "N/A" availability result, even though there is a file with updated stats.

The same thing may happen if a NAV installation is moved and the absolute path to the RRD data directory changes, and the same thing will happen with service statistics collected by servicemon if a server changes its name (since this RRD logic is in the statemon library common to both pping and servicemon).

pping should always check first whether an RRD file is already known in the db, renaming the physical file if necessary and update the database accordingly. I.e. it should work hard to never create multiple rrd_file entries for the same device.

[Morten Brekkevold (mbrekkevold)]

This is in essence related to bug 566574 and bug 733115, which were precursors to this more elaborate problem description.

[Morten Brekkevold (mbrekkevold)]

Fixed on anonymous branch and merged here: http://metanav.uninett.no/hg/series/3.9.x/rev/32e456e3e07f