Messages

Thanks, I figured a reinstall would do the trick but I'll try it out.

That's the thing, my disk is ada0, not ses0

Here's the output from SMART for my SSD:

Code Select Expand

smartctl 7.4 2023-08-01 r5530 [FreeBSD 13.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron Client SSDs
Device Model:     Crucial_CT120M500SSD1
Serial Number:    1346095A5F4E
LU WWN Device Id: 5 00a075 1095a5f4e
Firmware Version: MU03
User Capacity:    120,034,123,776 bytes [120 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Sep 28 15:01:16 2023 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

And

Code Select Expand

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

I updated to 23.7.5 to see if the unbound fixes worked but unfortunately they did not.

Here's some more error logs:

Code Select Expand

2023-09-27T15:44:48-07:00 Error configd.py [fd485a19-ddd4-4181-8ca8-c98e57c6be8e] returned exit status 1
2023-09-27T15:44:15-07:00 Error configd.py [e6737a21-b1b5-4c12-aac9-cf637367f763] Script action stderr returned "b'diskinfo: Failed to determine serial number for: /dev/ses0'"
2023-09-27T15:44:12-07:00 Error configd.py [564b2a76-2e90-446c-b316-88e178e6d1ff] Script action stderr returned "b'diskinfo: Failed to determine serial number for: /dev/ses0'"
2023-09-27T13:51:01-07:00 Error configd.py [788894c3-6cd6-4a60-87bf-457177742baa] Script action stderr returned "b'diskinfo: Failed to determine serial number for: /dev/ses0'"
2023-09-26T16:23:47-07:00 Error configd.py [6feb4505-619a-43f8-bf81-2e9986420268] Script action stderr returned "b"pkg: sqlite error while executing SELECT count(name) FROM sqlite_master WHERE type='table' AND name='repodata'; in file pkgdb.c:2358: database is locked\npkg: Repository mimugmail contains no repodata table, need to re-create database""
2023-09-26T16:23:40-07:00 Error configd.py [68b7212a-e39f-49fe-a7d3-a0286c885660] Script action stderr returned "b"pkg: sqlite error while executing SELECT count(name) FROM sqlite_master WHERE type='table' AND name='repodata'; in file pkgdb.c:2358: database is locked\npkg: Repository OPNsense contains no repodata table, need to re-create database\npkg: sqlite error whil""
2023-09-26T16:23:23-07:00 Error configd.py [7c5d2c24-a148-45a4-9446-80822b47f54a] Script action stderr returned "b'diskinfo: Failed to determine serial number for: /dev/ses0'"
2023-09-26T16:18:47-07:00 Error configd.py [797fbae3-725c-4b21-94ac-a3df0a7dc08a] Script action stderr returned "b'diskinfo: Failed to determine serial number for: /dev/ses0'"
2023-09-26T04:12:02-07:00 Error configd.py [e3ad38d6-b47c-45a5-b8cd-4edce6c4b5b8] Script action stderr returned "b'diskinfo: Failed to determine serial number for: /dev/ses0'"
2023-09-26T04:10:45-07:00 Error configd.py [a54c0ac7-a7e4-42a5-9353-bed4e3011671] Script action stderr returned "b'diskinfo: Failed to determine serial number for: /dev/ses0'"
2023-09-26T04:09:29-07:00 Error configd.py Configd disconnected while executing : 'unbound' start

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?

I seem to have fixed it. The fix for me was I turned on DNS64 and as such when it was trying to resolve Blocklist DNS rules it defaulted to the AAAA address when some of them only have a A address.

Once I turned off DNS64 and reloaded Unbound the blocklist was updated in only a few seconds instead of 900.

Thanks for the help and pointing me to a few other troubleshooting steps!

Code Select Expand

2022-08-18T15:56:27-07:00 Notice unbound blocklist download done in 16.20 seconds (268659 records)

Well once I ran it in command line again I checked the unbound logs and noticed that it was actually updating blocklists in the background.

Code Select Expand

blocklist download done in 992.24 seconds

It seems to be that if the Download and Apply button/script is ran from the Web GUI, if it takes more than 120 seconds it is killed as it is deemed 'stuck'. If ran manually, it will continue to update until all lists are updated even if it takes 16.5 minutes.

Good point. I ran it in command line but it seems to have executed successfully, no errors thrown.

After running it again from the web GUI it seems like it timed out:

Code Select Expand

configd.py Timeout (120) executing : unbound dnsbl

And now every time I try to run it from the GUI it throws that same error I've posted before. It maybe seems to be timing out trying to download a block list?

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.