Migrated install, RRD graphs historic data reset for some items

Help
1

Due to an old and neglected Ubuntu 18.04 server, without support for PHP 7.3, my LibreNMS install has been down since the v1.70.0 release updated the minimum PHP requirement. Rather than upgrade the existing server, I’ve completed a new Ubuntu 20.04.1 install & followed the documentation for a new LibreNMS install and migration.

Immediately following the migration everything appears OK, full graph history etc is still available, until the poller first runs, at which point a large number of my graphs seem to be reset and lose all historic data. It’s mainly disk usage history that I’m interested in.

The data that has been reset doesn’t appear to be consistent against one specific target, or operating system. i.e. I have two file servers, both running Windows Server 2016 Core, on the same virtual hosts:

  • A has reset memory data, but B has retained it
  • Both have retained their CPU data
  • both have reset all disk usage data, for all disks

I did notice the FAQ for migrating mentioned the RRDs potentially needing migrating if you’re changing CPU architecture, however I don’t believe this should apply to me as this is just a new VMware VM on the same host.

I also noticed that the v1.70.0 release post mentions that memory polling has been reworked and may result in loss of history, but I assume that shouldn’t affect storage usage, which is what I’m most interested in retaining history for.

I’ve already cleared the data and re-processed the migration copying the old data across again, and I got either the same or similar results, I didn’t keep specific enough notes to confirm whether the items which were/weren’t reset were identical or not.

Any advice / assistance in troubleshooting this would be appreciated.

2

./validate.php output:

====================================
Component | Version
--------- | -------
LibreNMS  | 1.70.1-21-g9126e0f00
DB Schema | 2020_11_02_164331_add_powerstate_enum_to_vminfo (191)
PHP       | 7.4.3
Python    | 3.8.5
MySQL     | 10.3.25-MariaDB-0ubuntu0.20.04.1
RRDTool   | 1.7.2
SNMP      | NET-SNMP 5.8
====================================

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

This because you upgraded to a newer version… In the latest releases, memory rrd were unified but only some could be migrated.

Not sure about the disk usage data, maybe something changed with the rrd names.

4

This topic was automatically closed 730 days after the last reply. New replies are no longer allowed.