25.07.r.20250709.2036 First Boot WireGuard Service not running
-
Hmm, try adding it there or to loader.conf.local and see if that changes anything at boot.
-
@stephenw10 said in 25.07.r.20250709.2036 First Boot WireGuard Service not running:
or to loader.conf.local and see if that changes anything at boot.
WG-problem still there. Or did you mean something different?
-
Nope that's what I meant, the delay at boot could have impacted a race condition at boot.
Looking at that boot log there is a lot of stuff happening during boot. Some of that might be better suppressed but that can cause other issues.
What was the last version that booted correctly?
-
@stephenw10 said in 25.07.r.20250709.2036 First Boot WireGuard Service not running:
What was the last version that booted correctly?
It looks like 25.07.r.20250715.1733 is most problematic with every reboot.
25.07.r.20250709.2036 only had this problem on the first boot after the upgrade.I just booted through all the snapshots to verify this. Although my network is evolving all the time, but it looks like 25.07.r.20250715.1733 is the reason.
-
Hmm, OK those dpinger error logs above are not in the given systen log txt. I assume those do appear in the system log? But not at boot?
-
@stephenw10 I can wait 20 minutes and post again if this helps. Can I upload to another place than the public forum? And I guess I should post the logfile and not copying stuff from the browser.
-
Yup you can upload here: https://nc.netgate.com/nextcloud/s/rLWRrGHTF6MoNaW
-
@stephenw10 This dpinger stuff is only in the log after I "enabled" the gateways by hand.
This time, I had halted pfSense before, kea-dhcp4 wasn't running according to service status widget. -
Hmm, so in that log after 'Bootup complete' none of the WG tunnels or gateways were up?
-
@stephenw10 I dropped you some pictures what I actually see and this is interesting, at least to me. I just rebooted to have the same problem.
- Dashboard shows none of the WireGuard Gateways and Service Status shows WireGuard not running. If I push the button to start WireGuard, nothing happens.
- WireGuard Status shows that only the connection to Debian is not running, others do. (Others in red are expected to not run and are not of interest.)
- In Gateways I enable all of the WireGuard Gateways by hand, they are for whatever reason not enabled.
- Going back to WireGuard Status I now see a warning that WireGuard is not running (why not before?). Then I press the button to start the WireGuard Service and this time it does.
- Everything is running and working like it should.
-
@stephenw10 I made some further changes. I removed the gateway for that problematic tunnel and also removed keep alive etc so that it is not expected to be running at start.
That didn't changed anything for me. At next reboot, gateways are down as is WireGuard. So it seems more of a general problem, although no one else is reporting it... -
@stephenw10 Today I rebooted the host (Hyper-V) and had no problem at all. Don't know if this points towards being a weird virtualization issue... But then, why would WireGuard be effected...
-
Running /etc/pppoe_restart_pppoe0 via Command Prompt fixes the issue after reboot for me, maybe other things do too...
Edit: Interestingly, doing it as a Services: Shellcmd Settings like shown below doesn't do it, so I removed that after testing (it one time).
Edit2: So to me it is looking like a timing problem between 25.07.r.20250709 and 25.07.r.20250715.
-
Yup it does look like a timing issue or race condition. You have quite a lot of stuff running there. I'm not able to replicate it here. Yet.
Are you using failover or loadbalance with those WG gateways? If not you might try disabling the monitoring action on them. That will significantly reduce the boot processes.
-
@stephenw10 said in 25.07.r.20250709.2036 First Boot WireGuard Service not running:
Are you using failover or loadbalance with those WG gateways? If not you might try disabling the monitoring action on them.
Not with them but with others. Disabling the monitoring action only on them didn't make a difference.
Edit: Disabling it on all but WAN also made no difference.
