System Logs-Gateways: no entries after 24.11 update
-
I am troubleshooting a 5 minute outage, which was reported as such by uptimerobot. it's April 14th at the time of writing. When I check the Gateways logs, the last entry is from March 26th, which is exactly the last netgate 2100 reboot and 1 day after the upgrade from 24.03 to 24.11.
The free version of uptimerobot reports every 5 minutes, so in this case it may just have missed a beat and reported false positive.
However, this event made me aware that Gateway logging has paused. May I assume no Gateway logs have been recorded since March 26th if I don't see them? Or could there be something wrong with displaying the log?
FTR I do have other logs from today and last week for the System/General logs, the DNS resolver, Firewall, DHCP, etc. The system appears to be working normally.
The last System/Routing log is from November.
Any help highly appreciated.
-
@Cabledude said in System Logs-Gateways: no entries after 24.11 update:
if I don't see them?
Go ssh, or console, and ask if 'dpinger', the one who adds log lines to the Status >System Logs >System > Gateways log file is still running.
And also check if you want it to run ?
After all, if this one is checked (for all WANs) => then case solved ^^On the command line :
ps aux | grep 'dpinger'and you should find one (if you only have one WAN, typical IPv4) or two (and IPv4 and IPv6 dual stack), or even more instances (like the above, and a VPN 'WAN').
Also : dpinger has another job : it fills up the monitoring graphs :( my example shows both the IPv4 and IPv6 gateway monitoring )
I had a look at my own gateway logs, and saw something ... strange .. new :
no more entries since april,7, and that can't be right, as I use the latest beta version build on "Wed Apr 9 22:49:02 UTC 2025" and logically installed after that date - so after April 9 and updating will reboot pfSEnse which will restart dpinger processes for sure.
I know they did - they are running right now.
Not logging ? -
@Gertjan Thank you for your help and insights. As it happens, we just had a 3 minute power outage an hour ago and the unit has powered up nicely afterwards.
Now when I check the Gateway logs, I see new entries as from the time of outage:
Apr 15 14:43:57 dpinger 34231 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr fe80:%mvneta0 bind_addr fe80::c1%mvneta0 identifier "WAN_DHCP6 " Apr 15 14:43:57 dpinger 33814 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 80.x.x.1 bind_addr 80.x.x.x identifier "WAN_DHCP " Apr 15 14:43:57 dpinger 69771 exiting on signal 15 Apr 15 14:43:57 dpinger 70339 exiting on signal 15 Apr 15 14:42:08 dpinger 70339 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr fe80:%mvneta0 bind_addr fe80:mvneta0 identifier "WAN_DHCP6 " Apr 15 14:42:08 dpinger 69771 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 10% alarm_hold 10000ms dest_addr 80.x.x.1 bind_addr 80.x.x.x identifier "WAN_DHCP " Apr 15 14:42:08 dpinger 73887 exiting on signal 15 Apr 15 14:39:36 dpinger 73887 WAN_DHCP6 fe80::%mvneta0: Alarm latency 0us stddev 0us loss 100% Apr 15 14:39:34 dpinger 73887 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr fe80:%mvneta0 bind_addr fe80::mvneta0 identifier "WAN_DHCP6 " Apr 15 14:39:34 dpinger 52175 exiting on signal 15 Apr 15 14:39:30 dpinger 52175 WAN_DHCP6 fe80::%mvneta0: Alarm latency 0us stddev 0us loss 100% Apr 15 14:39:28 dpinger 52175 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr fe80:mvneta0 bind_addr fe80::%mvneta0 identifier "WAN_DHCP6 " Mar 26 12:16:37 dpinger 38497 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr fe80:%mvneta0 bind_addr fe80::%mvneta0 identifier "WAN_DHCP6 "The outage occurred at 14:38/39 and it lasted for 3 minutes. Judging from the logs and seeing 14:39:28 etc. dpinger lines, should I assume that the dpinger was in fact running at the time the outage started?
So I don't think it will be useful anymore to check if dpinger is running, as it must at this point or I'd have no logs. Still, here is the output:
[24.11-RELEASE][root@SPK.home.arpa]/root: ps aux | grep 'dpinger' root 82858 0.0 0.1 12952 2540 0 S+ 16:00 0:00.01 grep dpinger [24.11-RELEASE][root@SPK.home.arpa]/root:I don't see any WANs listed, so I wonder what's going on here. I have dual stack, so I'd expect a IPv4 and IPv6 WAN. I am online atm so there's no question that the WANs are up.
-
@Cabledude I also had this after upgrading from 24.11.
Reseting log system fixed it
status/ system logs/system/general/settingsreset log files.
-
@Cabledude said in System Logs-Gateways: no entries after 24.11 update:
[24.11-RELEASE][root@SPK.home.arpa]/root: ps aux | grep 'dpinger'
root 82858 0.0 0.1 12952 2540 0 S+ 16:00 0:00.01 grep dpinger
[24.11-RELEASE][root@SPK.home.arpa]/root:means : no dpinger process is running !
You should see : see above, previous post,w where I gave 1 for IPv4 and 1 for IPv6. You should see the same thing.
No dpinger running == totally normal that there are no gateway logs ;)I just restarted my pfSense this morning as I upgraded to 25.03.b.20250414.1838 which came out yesterday and :
[25.03-BETA][root@pfSense.bhf.tld]/root: ps aux | grep 'dpinger' root 7412 0.0 0.1 14692 3084 - Is 08:10 0:00.62 /usr/local/bin/dpinger -S -r 0 -i WAN_DHCP6 -B 2a01:dead:beef:a600:92ec:7 root 7653 0.0 0.1 14692 3084 - Is 08:10 0:00.56 /usr/local/bin/dpinger -S -r 0 -i WAN_DHCP -B 192.168.10.4 -p /var/run/d root 51651 0.0 0.1 14076 2684 0 S+ 09:23 0:00.00 grep dpingerand logs do show up for me now.
Btw : the beta releases are really good ... no issues what so ever for me (vanilla dual stack pfSense. with captive portal, FreeRadius, minimal pfBlocker and some other small gadgets).