Error message every time I open the dashboard on the GUI

Started by AlegroEmptyPlanet2001, May 10, 2025, 04:04:38 PM

Previous topic - Next topic
When I log into the GUI I get the initial message "Danger, unexpected error. Check log files". Even if I am already in the GUI and go to another section, when I go back to the Dashboard the message comes up again. I checked the log files and can only find 2 errors but I have hunted around and cannot find anything on them. Nothing seems to be malfunctioning that I can tell so it is making it more difficult to troubleshoot.

Error1: 2025-05-10T09:55:26-04:00   Error   configd.py   [68d7dccc-f071-409a-9d65-f7e2d422af85] Script action failed with Command '/usr/local/sbin/pluginctl -S '' ''' died with <Signals.SIGSEGV: 11>. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 78, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.11/subprocess.py", line 413, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/sbin/pluginctl -S '' ''' died with <Signals.SIGSEGV: 11>.

Error 2: 2025-04-05T09:49:05-04:00   Error   firewall   There were error(s) loading the rules: /tmp/rules.debug:11: cannot define table bogonsv6: Invalid argument - The line in question reads [11]: table <bogonsv6> persist file "/usr/local/etc/bogonsv6"

Anyone seen either of these before or have any suggestions?
Thanks

Firewall - Diagnostics - Aliases

Click on Update Bogons, wait ~10-15 minutes then reboot

I did that but even after reboot it gave the same error.

This is odd. Check dmesg output. Tell us about your hardware or VM setup first.


Cheers,
Franco

The bogonsv6 behavior is/seems flaky still/again. I do not have "block bogon networks" checked in any interface, but the bogonsv6 alias is loaded anyway... eventually (bogons is loaded immediately after reboot; bogonsv6 is loaded after some hours/days). I don't actually care, as I have plenty of RAM and alias space reserved, and I don't reference bogonsv6 in another alias (at this time).

I don't think bogonsv6 behavior relates to the original problem, but the check I would perform:
- Look at all interfaces to see if "block bogon networks" is checked;
- Look at "Firewall: Aliases" to see if bogonsv6 is loaded (whether "Loaded#" = ~150000 or 0).

Bogon v6 is enabled, Blockbogon networks is not checked. I am not  running OPNSense on a VM, I have a dedicated mini PC    
Intel Processor N100
CPU Speed   3.4 GHz
Cache Size   16 GB
Graphics Card Description   Integrated
512G SSD

Bogons aside a SIGSEGV on a simple pluginctl -S call is cause for fundamental worry as previously mentioned. I would recommend not chasing specific issues here before having sorted that out with dmesg, health checks, etc.


Cheers,
Franco