[SOLVED] Issues after rebooting OPNsense

[sToRmInG]

Hi

I'm not quite sure since when I have the issue, might be since upgrading to 21.1, definitely since 21.1.3.
When I reboot my OPNsense (running on an PC Engines APU2) initially everything is working but after a couple of minutes everything stops responding.

The browser is reporting that there were invalid TLS information making it unable to access the Web UI at all, DHCP / DNS are also not working anymore.

Gladly I am able to access the APU through SSH. From there if I choose "Reload all services" everything works normally until the next reboot.

I tried to gather some logs but wasn't sure where to look for them (tried /var/log/).

Does anyone else experience the same issue? Any advice on how I can grab the relevant logs?

*EDIT*
Might this be RTC related? NTP log is reporting this:

Code: [Select]

Apr  6 17:04:28 OPNsense ntpdate[32553]: step time server offset -7200.589284 sec
Apr  6 17:04:29 OPNsense ntp[49450]: Successfully synced time after 1 attempts.
Apr  6 17:04:29 OPNsense ntp[51637]: Starting NTP Daemon.
Apr  6 17:04:29 OPNsense ntpd[64311]: ntpd 4.2.8p15@1.3728-o Mon Jan 25 04:33:48 UTC 2021 (1): Starting
Apr  6 17:04:29 OPNsense ntpd[64311]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Apr  6 17:04:29 OPNsense ntpd[64311]: ----------------------------------------------------
Apr  6 17:04:29 OPNsense ntpd[64311]: ntp-4 is maintained by Network Time Foundation,
Apr  6 17:04:29 OPNsense ntpd[64311]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
Apr  6 17:04:29 OPNsense ntpd[64311]: corporation.  Support and training for ntp-4 are
Apr  6 17:04:29 OPNsense ntpd[64311]: available at https://www.nwtime.org/support
Apr  6 17:04:29 OPNsense ntpd[64311]: ----------------------------------------------------
Apr  6 17:04:29 OPNsense ntpd[67577]: proto: precision = 0.415 usec (-21)
Apr  6 17:04:29 OPNsense ntpd[67577]: basedate set to 2021-01-13
Apr  6 17:04:29 OPNsense ntpd[67577]: gps base set to 2021-01-17 (week 2141)
Apr  6 17:04:29 OPNsense ntpd[67577]: restrict: 'monitor' cannot be disabled while 'limited' is enabled
[...]
Apr  6 17:04:29 OPNsense ntpd[67577]: Listening on routing socket on fd #33 for interface updates
Apr  6 17:04:29 OPNsense ntpd[67577]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Apr  6 17:04:29 OPNsense ntpd[67577]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Apr  6 17:10:10 OPNsense ntpd[67577]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized


[sToRmInG]

Ok, after I removed os-wireguard (including all firewall rules) and os-api-backup everything is back to normal.

If I should guess what caused the issue I'd suspect os-wireguard.
Since I'm not actually using it I'll leave it uninstalled for now. Let's see how the kmod will perform when it's released.