Monitoring Gateway
-
@hendi that doesn't look right to be honest, mine is the same as @stephenw10
root 52663 0.0 0.0 11600 3096 - IN 3Nov22 8:33.17 |-- /bin/sh /var/db/rrd/updaterrd.sh root 58705 0.0 0.0 10576 2212 - INC 12:07 0:00.00 | `-- sleep 60 -
I'm in a different time zone.
It seems to be working now. I have no idea why it didn't work after two reboots. After the third reboot it works!
-
Mmm, you see any RRD errors at boot? Anything like:
Nov 15 14:32:25 php-cgi 524 rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/system-sensors.rrd N:U:U:U:U:U' returned exit code '1', the output was 'ERROR: /var/db/rrd/system-sensors.rrd: expected 6 data source readings (got 5) from N'Edit: Cross-posted. Good to see!
-
@stephenw10 No errors
-
Some errors here
-
Those are only because it booted in verbose mode. None of that is actually in use. Not a problem.
-
Any idea why the graphics didn't work?
-
Not really. It looked like the update script was stalled on some sub-process. Whatever it was it got past that and started logging data again.
-
Thank you all for your support!
-
I don't know what is wrong with the pfsense configuration, but the monitoring keeps stopping. It runs for a few days and then stops. For example, now I see that it has stopped since 21.11
-
You see any errors in the logs when it stops?
Does the gateway fail when it stops? The WAN reconnect?
-
This post is deleted! -
Is it all the monitoring data that stops each time? Not just gateway monitoring?
Nothing else in the system log at the time it appears to stop?
-
@stephenw10 Monitoring stopped again. This time without any restart. Nothing works in monitoring, not just the gateway.
-
And still nothing in the system log when it happened?
-
@stephenw10 I cleared all logs, unninstalled all packages.
drwxr-xr-x 2 nobody wheel 20 Jan 8 11:35 . drwxr-xr-x 16 root wheel 27 Jan 8 08:57 .. -rw-r--r-- 1 root wheel 147848 Jan 8 11:42 WANGW-quality.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 ipsec-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 ipsec-traffic.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 lan-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 lan-traffic.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 opt1-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 opt1-traffic.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 ovpns1-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 ovpns1-traffic.rrd -rw-r--r-- 1 nobody wheel 49720 Jan 8 11:42 ovpns1-vpnusers.rrd -rw-r--r-- 1 nobody wheel 588592 Jan 8 11:42 system-mbuf.rrd -rw-r--r-- 1 nobody wheel 735320 Jan 8 11:42 system-memory.rrd -rw-r--r-- 1 nobody wheel 245976 Jan 8 11:42 system-processor.rrd -rw-r--r-- 1 nobody wheel 275648 Jan 8 11:42 system-sensors.rrd -rw-r--r-- 1 nobody wheel 245976 Jan 8 11:42 system-states.rrd -rw-r--r-- 1 root wheel 8493 Jan 8 11:35 updaterrd.sh -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 wan-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 8 11:42 wan-traffic.rrdEverytime i run
sh ./updaterrd.shA recording appears in the graphics. Then nothing appears. I run it again, it appears again. Then nothing. Can I run that command in crontab to update the graphs every 1 minute?
-
You probably could but you definitely shouldn't need to. That script should be running continually anyway:
[23.01-BETA][root@1100.stevew.lan]/root: ps -auxwwd | grep rrd root 28762 0.0 0.3 13336 2844 u0- IN 13:53 0:00.11 |-- /bin/sh /var/db/rrd/updaterrd.shSteve
-
[2.6.0-RELEASE][admin@ccia1.home.arpa]/root: ps -auxwwd | grep rrd root 96131 0.0 0.1 11212 2484 0 S+ 16:08 0:00.00 | `-- grep rrd root 30031 0.0 0.1 11584 2664 v0- IN 11:35 0:00.03 |-- /bin/sh /var/db/rrd/updaterrd.sh root 23555 0.0 0.1 11584 2660 - IN 11:54 0:00.00 | `-- /bin/sh /var/db/rrd/updaterrd.shI don't know why it appears twice
-
Mmm, me either. I don't see that anywhere here. Did you already start it manually or add it to some script?
-
@stephenw10 I haven't added it to cron yet and haven't run updaterrd.sh yet. This morning I deleted everything with .rrd from /var/db/rrd. Then reboot. It still doesn't update.
