Topics

1

23.7 Legacy Series / Error updating to 23.7

« on: September 26, 2023, 12:40:08 pm »

Hello,

I ran into a few hiccups while updating to 23.7. No matter what I do, Adguardhome won't start.

No biggie, I know it runs into errors when updating. Turned off Adguard, changed Unbound to primary DNS and it worked! No matter what I tried, however, I couldn't get Adguardhome's service to run. I've updated to 1.10 which is supposed to fix an error related to this I think.

However, upon checking the logs I see this:

"Error   configd.py   [49fe10f1-4eda-4f7a-9afd-07539e4f3039] Script action stderr returned "b'diskinfo: Failed to determine serial number for: /dev/ses0'"

Now when trying to restart Unbound or other services the whole thing hangs and I need to force a restart. What's going on? How do I fix this?

2

22.7 Legacy Series / Unbound blocklist update script failing in 22.7.2

« on: August 18, 2022, 08:28:59 am »

Hey all,

I recently started using OPNsense and am loving it so far.

I just stopped using a PiHole and swapped to using the unbound blocklists to simplify my network. Unfortunately, I have been running into issues when I try to click "Download and Apply" on the Blocklist screen. I tracked down under System -> Log files -> Backend that the actual script was failing:

Severity	Process	Line
Error	configd.py	[c6b3537c-2d37-4922-bb08-7dd6c4c0ffc1] Script action failed with Command ' /usr/local/opnsense/scripts/unbound/blocklists.py && /usr/local/opnsense/scripts/unbound/wrapper.py -b ' returned non-zero exit status 99. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 482, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command ' /usr/local/opnsense/scripts/unbound/blocklists.py && /usr/local/opnsense/scripts/unbound/wrapper.py -b ' returned non-zero exit status 99.

Any ideas on how to fix this? I've tried the usual audits, restarting services, restarting the whole machine, and checking for updates.