Monitoring Gateway
-
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.
-
Clearly something in your install is starting that script incorrectly or the script is getting hung up on something trying to update it. I would have expected clearing the RRD data to remove whatever that might be though.
I'd probably look at reinstalling at this point. At least that would narrow it to a config problem or something specific to your install.Steve
-
@stephenw10 I concur with the reinstall.. If there was something amiss with it in general you would think the forums would be a fire with people having issues with their monitoring. So it has to be something odd with the install or issue with something being monitored that is unique to the setup that is causing the issue.
-
I will reinstall pfsense at some point. After installation, monitoring worked until a certain point. Unfortunately, I don't have all the logs anymore, but I think it coincided with the moment when I added another network card for a separate network. Thanks
-
I have now installed ntopng. Monitoring has started to work.
Let's see for how long. -
Huh. That's.... interesting
-
He stopped again. I don't know what or how I should search in the logs.
-
It appears the update script is hitting something it's failing to process but it doesn't do it immediately. So what changes when it fails? Is there anything logged at all at that time?
-
[2.6.0-RELEASE][admin@ccia1.home.arpa]/root: ls -lt /var/db/rrd total 402 -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 ovpns1-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 ovpns1-traffic.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 ipsec-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 ipsec-traffic.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 opt1-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 opt1-traffic.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 lan-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 lan-traffic.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 wan-packets.rrd -rw-r--r-- 1 nobody wheel 393168 Jan 10 17:05 wan-traffic.rrd -rw-r--r-- 1 root wheel 147848 Jan 10 17:04 WANGW-quality.rrd -rw-r--r-- 1 nobody wheel 882048 Jan 10 17:04 ntpd.rrd -rw-r--r-- 1 nobody wheel 275648 Jan 10 17:04 system-sensors.rrd -rw-r--r-- 1 nobody wheel 588592 Jan 10 17:04 system-mbuf.rrd -rw-r--r-- 1 nobody wheel 735320 Jan 10 17:04 system-memory.rrd -rw-r--r-- 1 nobody wheel 245976 Jan 10 17:04 system-processor.rrd -rw-r--r-- 1 nobody wheel 245976 Jan 10 17:04 system-states.rrd -rw-r--r-- 1 nobody wheel 49720 Jan 10 17:04 ovpns1-vpnusers.rrd -rw-r--r-- 1 root wheel 9205 Jan 10 15:48 updaterrd.sh[2.6.0-RELEASE][admin@ccia1.home.arpa]/root: grep "rrd" /var/log/system.log Jan 8 11:35:05 ccia1 php[415]: rc.bootup: Creating rrd update script Jan 8 16:46:33 ccia1 php[415]: rc.bootup: Creating rrd update script Jan 8 17:29:28 ccia1 php-fpm[367]: /services_ntpd.php: Creating rrd update script Jan 8 17:36:42 ccia1 php-fpm[368]: /status_monitoring.php: Creating rrd update script Jan 8 17:37:29 ccia1 php-fpm[367]: /status_monitoring.php: Creating rrd update script Jan 8 17:40:40 ccia1 php-fpm[367]: /status_monitoring.php: Creating rrd update script Jan 8 17:42:29 ccia1 php-fpm[367]: /status_monitoring.php: Creating rrd update script Jan 8 17:45:32 ccia1 php-fpm[4876]: /status_monitoring.php: Creating rrd update script Jan 8 17:46:03 ccia1 php-fpm[368]: /status_monitoring.php: Creating rrd update script Jan 8 18:00:17 ccia1 php-fpm[368]: /status_monitoring.php: Creating rrd update script Jan 8 18:39:20 ccia1 php-fpm[367]: /status_monitoring.php: Creating rrd update script Jan 8 19:02:27 ccia1 php-fpm[368]: /status_monitoring.php: Creating rrd update script Jan 8 19:04:55 ccia1 php-fpm[367]: /status_monitoring.php: Creating rrd update script Jan 10 15:48:02 ccia1 php-fpm[368]: /status_monitoring.php: Creating rrd update script[2.6.0-RELEASE][admin@ccia1.home.arpa]/root: ps -auxwwd | grep rrd root 21285 0.0 0.1 11212 2484 0 S+ 19:57 0:00.00 | `-- grep rrd root 90514 0.0 0.1 11592 2860 - IN 15:48 0:00.62 |-- /bin/sh /var/db/rrd/updaterrd.sh root 56237 0.0 0.1 11592 2856 - IN 17:05 0:00.00 | `-- /bin/sh /var/db/rrd/updaterrd.shIs the problem because updaterrd.sh is duplicated? It seems to coincide with the time when the logs stop. But why does it run twice?
