Messages

I get same issue, the widgets all fail one by one within a few seconds of opening home page.  After a while the entire system fails and I have to power cycle it.  Testing it right now but so far I don't feel comfortable deploying this in production. I'm testing something right now, to see if the failure only happen when the webui is left open. Right now it's just sitting at the login screen and I hit refresh once in a while to see if it's still up.   The failures seem to happen overnight, but I'm not positive on an exact time line. I have a continuous ping setup as well, so I might be able to figure it out from there once it stops pinging.

I had the same issue, with the dashboard widgets failing and the system crashing and rebooting. Checked the system logs, and noticed lighttpd clock errors reported under Web GUI. Strange, the only thing I could think of would be the CMOS battery, so I checked it, and sure enough it was very low voltage. Changed the battery with a new one, and haven't had the problem since. This was 3 days ago. 

Same here, Wireguard is working fine for me, the upgrade was problem-free.

Like the OP, I was holding back from upgrading as well, due to what seemed like a higher than normal quantity of upgrade-related issues with 20.7.  Did a backup and went ahead and upgraded from 20.1.x to 20.7 and then 20.7.2, all "in-place" upgrades using the built-in script from current version.  No issues thus far.  Wireguard works as well, which is what I was most concerned about breaking. 

I had a very stable machine (HP 290 w/Celeron G4900 3.1GHz 4GB RAM 16GB NVME) running 20.1.1, CPU use was typically about 15% and would occasionally bump up to 60%. The system ran for 60 days continuous uptime, no issues. 

I upgraded to 20.1.5 today, and it is now running at 60% CPU (idle) and spiking up to 100%, with temps 10-15 degrees C higher than before. 

The activity log shows the culprit is syslog-ng which is using 60+% of WCPU. 

Anyone else having this problem?  Wondering how to fix it, other than just shutting down the syslog service.

I've been using the Wireguard setup to connect local clients on the LAN to the internet via my VPN provider.  While we've had issues with some websites and streaming services that don't like the VPN connection, we've had zero issues with iCloud or Apple mail services. 

When I go to System > Log Files > General, the script fails, no log files appear, and CPU usage spikes.  Under 'Backend" the logs show this:

Code Select Expand

configd.py: [753axxxx-xxx-xxxx-xxxx-xxxxxxxx3b65] Script action failed with Command '/usr/local/opnsense/scripts/systemhealth/queryLog.py --limit '20' --offset '0' --filter '' --module 'core' --filename 'system'' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 484, in execute stdout=output_stream, stderr=error_stream) File "/usr/local/lib/python3.7/subprocess.py", line 363, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/systemhealth/queryLog.py --limit '20' --offset '0' --filter '' --module 'core' --filename 'system'' returned non-zero exit status 1.

Something has become corrupted it seems.  What is my best course of action to correct this?

Thanks

Also, if you go to Reporting > Traffic and then wait a minute the active IPs on your LAN will populate as it logs traffic per address, you might need to scroll down to see them.

Oh, thanks for that!  That was the main problem with the configuration, somehow I missed the fact that the Gateway logic changed with the newer version(s).  After following your instructions from the linked thread, all looks to be functioning as it should.     

Looks like you were on 19.1 before 20.1?

Correct.

Once I confirmed that the Wireguard connection was working and internet was functional on the network through the VPN, I backed up the config and then upgraded again to 20.1.1
So far everything is still functional.  If it breaks, I'll revert Wireguard as suggested.
The only odd thing that I see (and it was this way before as well) is the Gateway shows "disabled" but "online" is green, also priority shows "defunct" as the default setting is 255, not sure if this should be different. 

Can you try to revert WireGuard with opnsense-revert? You can read in the Docs how it works

Thanks for the help.  With the 20.1.1 update, it appeared that nothing had changed with the wireguard plugin, so I tried a complete -revert of the entire opnsense 20.1.1 update.  That went fine.  Rebooted, still the same issues with wireguard connection not allowing internet connections on the LAN.  The error in the code output above (`ifconfig:`) made me think that something had gotten corrupted with either the interface or gateway.  So, I deleted both of those, as well as the wireguard configuration and started over.  It appears to be running fine, so that was likely the problem.

Now, the test will be to upgrade to 20.1.1 and see if it breaks again.

Any ideas?

OK, thanks.  Here's the output, IP addresses redacted:

Code Select Expand

$ /usr/local/etc/rc.d/wireguard restart   
[#] rm -f /var/run/wireguard/wg0.sock
[#] resolvconf -d wg0
[#] wireguard-go wg0
INFO: (wg0) 2020/02/15 15:22:28 Starting wireguard-go version 0.0.20200121
[#] wg setconf wg0 /tmp/tmp.b1mLyP2u/sh-np.KeKpO1
[#] ifconfig wg0 inet 10.xx.xx.xx/32 10.xx.xx.xx alias
[#] ifconfig wg0 inet6 fc00:xxxx:xxxx:xxxx::3:55c/128 alias
[#] ifconfig wg0 mtu 1420
[#] ifconfig wg0 up
[#] resolvconf -a wg0 -x
[#] route -q -n add -inet6 ::/1 -interface wg0
[#] route -q -n add -inet6 8000::/1 -interface wg0
[#] route -q -n add -inet 0.0.0.0/1 -interface wg0
[#] route -q -n add -inet 128.0.0.0/1 -interface wg0
[#] route -q -n add -inet xx.xx.xxx.xxx -gateway xx.xxx.xx.xx
[+] Backgrounding route monitor
ifconfig:  SIOCAIFGROUP: Operation not permitted

Please Open a new thread for this

New topic in General created.

Has anyone else had issues with Wireguard since the most recent update?  I'm running 20.1.1
It may be coincidental, however my Wireguard-Mullvad configuration, based on the routerperformance.net Azire write-up, was working well, but it suddenly prevents my network from internet access.  I'm not sure what exactly is happening, but nothing in my config has changed.  I've tried starting over, to no avail, I have no internet access as soon as I turn on the VPN, and it returns as soon as I turn it off.