RRD graphs not showing up after NIC failure?
-
Hi all!
I'm having what is (to me) a very odd issue with my pfSense 1.2.3-RELEASE install. Less than a week ago, the LAN side NIC stopped being recognized, so I replaced it with a spare Intel Pro/1000T NIC I had handy. All was well and good until a couple of days later when I tried to check out the RRD graphs page in the WebUI. Since the NIC failure, all of the graphs have been reporting no data, with 'nan' for the numerical values. The 'Traffic' tab does not load at all.
Is there an RRD config file that I need to update to reflect the new NIC? It's odd to me that ALL of the graphs stopped working, even the non-networking ones.
Thanks in advance for any help!
Update:
After playing around with things a bit more, I noticed that the updaterrd.sh script is giving the following output:
ERROR: illegal attempt to update using time 1282814946 when last update time is 1285027680 (minimum one second step) ERROR: illegal attempt to update using time 1282814946 when last update time is 1285027680 (minimum one second step) ERROR: illegal attempt to update using time 1282814946 when last update time is 1285027680 (minimum one second step) ERROR: illegal attempt to update using time 1282814946 when last update time is 1285027680 (minimum one second step) ERROR: illegal attempt to update using time 1282814946 when last update time is 1285027680 (minimum one second step) ERROR: illegal attempt to update using time 1282814946 when last update time is 1285027680 (minimum one second step) ERROR: illegal attempt to update using time 1282814947 when last update time is 1285027680 (minimum one second step) ERROR: illegal attempt to update using time 1282814948 when last update time is 1285027681 (minimum one second step) ERROR: illegal attempt to update using time 1282814950 when last update time is 1285027684 (minimum one second step)
The time is set properly on the router, how could the last update time be set almost a month out? I know from this that I could probably regain graphing functionality by resetting the graph history files, but I'd rather keep them if possible. I fail to understand how replacing a NIC could have triggered this, it seems like an issue that would have popped up earlier.