OPNsense Forum
Archive => 23.1 Legacy Series => Topic started by: pilotboy72 on June 29, 2023, 05:30:48 pm
-
Hello,
Starting with 23.1.10_1 and continuing with 23.1.11, I am unable to add entries into BIND. I can see the entries are written into the config.xml (multiple entries for the same A record are allowed as well), but they do not make into the .db files under either master/ or primary/. The entries also do not appear on the GUI.
It appears that the entries are being written into the .db file for the last zone in the list instead of the selected zone.
Brian
-
Any logs in Systems: Log Files : Backend?
-
Only thing I could find. Happened around the time I was working too, but not sure if it is directly related. I tried the operation a few times, but this appears only once in the log.
Script action failed with Command '/usr/local/opnsense/scripts/firmware/read.sh ' died with <Signals.SIGBUS: 10>. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 44, 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/firmware/read.sh ' died with <Signals.SIGBUS: 10>
--Brian
-
Did you already reboot?
-
The system rebooted after 23.1.11 was installed. I rebooted once more for good measure.
I retried this after the reboot and I see this line in the backend logs from configd.py:
[4690383d-0125-4ef7-926f-6a45db14121e] returned exit status 1
This isn't meaningful to me but maybe to someone else. I can see the record in the /conf/config.xml file, but it is in the wrong domain in the /conf/config.xml file. In other words, when modifying this via the GUI, the record is added to the last domain in the list instead of the selected domain in the GUI.
Brian