opnsense
RRD not collecting data after reboot
The DB (/var/db/rrd/(*.rrd|*.sh)) is touched at bootup. But then never updates with any new data.
Something that may be a small clue is that updaterrd.sh is a couple seconds newer than the DB files (*.rrd).
Seems that would be the other way around.
Four consecutive reboots all with this same result.
REPORTING: SETTINGS: Reset RRD Data will occasionally get it going. Though even that sometimes takes numerous attempts.
24.7.1
Thank you for creating an issue. Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.
For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
The easiest option to gain traction is to close this ticket and open a new one using one of our templates.
Sounds like #7753 which has a lot more info, probably best to continue there.
At boot up... /var/db/rrd/updaterrd.sh
Sun Aug 11 02:07:59 PDT 2024 TP0 counter: 1 While forever loop begins Sun Aug 11 02:07:59 PDT 2024 TP1 TP2 ... bunch of test points ... TP12 TP13 Sun Aug 11 02:08:02 PDT 2024 counter: 1
This is where it should be doing the 60 second wait for loop.
tail /var/db/rrd/updaterrd.sh echo "TP13" >> '/vvar/rrdupdatesh.txt'
date >> '/vvar/rrdupdatesh.txt' echo "counter: $counter" >> '/vvar/rrdupdatesh.txt' for UNUSED in $(seq 1 60); do sleep 1; done ---- Crashing hanging etc. on this. The while forever loop never runs again. echo "TP14" >> '/vvar/rrdupdatesh.txt' date >> '/vvar/rrdupdatesh.txt' echo "counter: " >> '/vvar/rrdupdatesh.txt' done echo "TP15" >> '/vvar/rrdupdatesh.txt' date >> '/vvar/rrdupdatesh.txt'
Waiting a minute or so before logging in after reboot seems to improve chances that it will continue running.
This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.