reseeded devices have no availability data

[Lars Kulseng]

If a device is removed, and then added again, det rrd data seems to be lost or disconnected from the rrd file. By digging in the database I found that it seems that devices that are removed then added again, do not contain any netboxid. If the netboxid is added manually, the availability and response time both appear in the web interface.

There are two problems here:

1. devices should be removed from the rrd_file table when they are deleted in NAV
2. the mechanism which performs the reporting should place the netboxid in the rrd_file table entry if it is missing.

One workaround I have found is to manually update the database to give the rrd_file entry a netboxid, which can be found elsewhere.

[Morten Brekkevold (mbrekkevold)]

This basically boils down to a single issue: pping will only add an RRD file to the rrd_file database table if it needs to create the RRD file on the file system.

If the RRD file already exists on the file system (as it will for a re-seeded IP device), it won't care whether that RRD file is registered in the database. Thus, the rest of NAV doesn't know that this file exists.

A more technical under-the-hood detail is that the rrd_file row still exists, but its foreign key reference to the netbox table has been NULLed since the netbox was deleted.

[Morten Brekkevold (mbrekkevold)]

Fix committed to series/3.5.x: http://metanav.uninett.no/hg/series/3.5.x/rev/41f45951ce87