After I upgraded from 24.1.10_8, my Health reporting has stopped working. See screenshot – in this case, the reporting worked for a while after the reboot but then stopped. After the next reboot, the reporting did not even capture anything. This is true of all the reports – the States reporting is just one example.
Also, the end time in the chart (in this case 16:55) never updates – after you have called up the graph the first time, the time remains the same.
Any pointers welcome on ways to track down the issue.
I am having the same issue. I was told to reset the RRD data in Report > Settings but that did not work for me. You can try it. I already posted about this issue. Here is the link to that original post.
https://forum.opnsense.org/index.php?topic=42060.0
Please let us know your result. FYI, I am using a Protectli FW6D. Just purchased it. Interested to hear your results.
Quote from: EvilAchmed on August 09, 2024, 06:13:28 PM
I am having the same issue. I was told to reset the RRD data in Report > Settings but that did not work for me.
Thanks for responding. I have reset my RRD data and so far (🤞) it is working. I will monitor and if it should stop collecting, I will post back here.
(I am running on a PCEngines APU2E4, as you can see from my signature. Very happy with the hardware.)
https://github.com/opnsense/core/issues/7753
Tickets on GitHub are always nice.
Cheers,
Franco
Quote from: franco on August 09, 2024, 09:56:31 PM
https://github.com/opnsense/core/issues/7753
Tickets on GitHub are always nice.
Thanks Franco. I'll keep my eye on that ticket as well. I have decided to just disable it for now until a fix is found and track my packet lost status via Smokeping.
Unfortunately, the fix did not stick. Reporting was recorded for about two hours and then stopped. This is definitely an issue.
Thanks Franco for pointing to Github, great that it is logged.
this should temp fix it till next reboot:
/usr/sbin/daemon -f -p '/var/run/updaterrd.pid' '/var/db/rrd/updaterrd.sh'
Having installed 24.7.2, I can confirm the issue is fixed by this update.