I'm experience a very strange problem, where it appears python3.7 is segfaulting. This causes a cascade of failures, as SEGVGUARD detects this, then disables python3.7. As you can imagine, many services rely on python3.7, and so the router slowly begins to fail.
In backend, the only suspect things are:
Sep 9 15:40:20 configd.py: [3bb524c2-0aff-453f-9779-bce8e030351f] request pfctl byte/packet counters
Sep 9 15:40:20 configd.py: [3bb524c2-0aff-453f-9779-bce8e030351f] Script action
failed with [Errno 1] Operation not permitted at Traceback (most recent call las
t): File "/usr/local/opnsense/service/modules/processhandler.py", line 484, in e
xecute stdout=output_stream, stderr=error_stream) File "/usr/local/lib/python3.7
/subprocess.py", line 342, in check_call retcode = call(*popenargs, **kwargs) Fi
le "/usr/local/lib/python3.7/subprocess.py", line 323, in call with Popen(*popen
args, **kwargs) as p: File "/usr/local/lib/python3.7/subprocess.py", line 775, i
n __init__ restore_signals, start_new_session) File "/usr/local/lib/python3.7/su
bprocess.py", line 1453, in _execute_child restore_signals, start_new_session, p
reexec_fn) PermissionError: [Errno 1] Operation not permitted
Which then causes SEGVGAURD to activate:
kernel: [HBSD SEGVGUARD] [python3.7 (32515)] Preventing execution due to repeated segfaults.
If anybody has some recommended steps, or relevant documentation I'm very receptive. Thanks!
It seems related to the Web GUI, maybe the dashboard or live view. Though It's difficult to say for certain, given that it's a live system, that I'd rather not cause downtime for.