Went to view the Unbound logfile, page kept running. I was able to navigate away and everything is working fine, but the process is now constantly consuming 25-40% of CPU. Been running for the past 20 minutes so far.
Checking the system logs, the command consuming the CPU is:
Quote/usr/local/bin/python3 /usr/local/opnsense/scripts/systemhealth/queryLog.py --limit 20 --offset 0 --filter --module core --filename resolver --severity Emergency,Alert,Critical,Error,Warning python3.8
6/26 - Update: I've narrowed the issue down to the
"Warning" filter. When it is selected, the process never returns any results. When I select "Notice", those results are returned within 10 seconds.
I also suspect this may nothing to do with the update and may have been present before. I'm just noticing it now as I was checking things out after the upgrade.
Killing the process works and doesn't appear to have any negative impact. Given it's just a log query, I wouldn't expect it to.
HI,
i updated today and just tested it and i do not have this issue.
BR
I've updated my original post with more info:
Did you have these filters selected? "Emergency,Alert,Critical,Error,Warning "
i get results immediately with every kind of filter selected!
I wonder if it's related to the size of the log files. I have about 50+ devices on my network and I use device dns registration.
My Unbound log files range from 200MB to 900MB.
I've changed my logging level from level 3 to 1, to reduce size, and will keep an eye on it.