Sensei db related error in backend log

[dinguz]

After the upgrade to 24.1, I get this error each hour in the backend log:

Code Select Expand

[399652ba-ab4f-4b4f-aafe-76271a90cdf7] Script action stderr returned "b'Traceback (most recent call last):
File "/usr/local/opnsense/scripts/OPNsense/Zenarmor/sensei-db-version.py", line 11, in <module>
from packaging import version ImportError: cannot import name \'version\' from \'packaging\' (unknown location)'"


This started after this error, which happened jan 27 01:00:

Code Select Expand

[e2cf332c-cec2-4d45-a457-e312330f599c] Script action failed with Command '/usr/local/zenarmor/scripts/datastore/rename_alias_elasticsearch.py
'zenarmor_0000000000_4b3100b6-c05c-4c03-bdb5-64fbea833847_'' returned non-zero exit status 1.
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/zenarmor/scripts/datastore/rename_alias_elasticsearch.py 'zenarmor_0000000000_4b3100b6-c05c-4c03-bdb5-64fbea833847_'' returned
non-zero exit status 1.


I'm running a home deployment of Zenarmor, up-to-date, with sqlite logging backend.

[GuruLee]

I'm still on Mongo with no issues.

Sent from my SM-N986U using Tapatalk

[hedders]

I am also seeing this. Running opnsense 24.1 (although it appeared in the logs prior to the upgrade from 23.7 too), Zenarmor is up to date (engine 1.16.2, database 1.16.24012617, agent 1.16.4), using a local Elasticsearch database.

I also noted that the Audit log shows the following error in configd.py every hour: "action sensei.update-install.os-sensei-db not found for user root".

Zenarmor seems to be running fine.  I do wonder whether it has something to do with this older thread:

https://forum.opnsense.org/index.php?topic=22363.0

[almodovaris]

Yup, I also see in logs stuff as:

Code Select Expand


./audit/audit_20240203.log:<35>1 2024-02-03T01:01:04+00:00 OPNsense.home.arpa configd.py 678 - [meta sequenceId="386"] action sensei.update-install.os-sensei-db not found for user root


[dinguz]

I also noted that the Audit log shows the following error in configd.py every hour: "action sensei.update-install.os-sensei-db not found for user root".

I didn't notice until just yet, but I am seeing this as well, also starting Jan 27, which is apparently the date 1.16.2 got installed.

[fre4ki]

Same here with a new installation.

OPNsense 24.1.1
ZenArmor engine 1.16.2

ZenArmor is with local elasticsearch installed.

Error   configd.py   action sensei.update-install.os-sensei-db not found for user root

Script action stderr returned "b'Traceback (most recent call last):\n File "/usr/local/opnsense/scripts/OPNsense/Zenarmor/sensei-db-version.py", line 11, in <module>\n from packaging import version\nModuleNotFoundError: No module named \'packaging\''"

[lizznl]

Same problem here but in 2-3 days the CPU also goes to 100% and I need to restart the engine.. Any ideas what I could do? Reinstalled Zenarmor already and didn't make any difference.

[sy]

Hi,

Please run the following commands

rm -fr /usr/local/opnsense/version/sensei-db
rm -fr /usr/local/sensei-db
Click in System - Firmware - Resolve Plugin Conflicts - Reset All Local Conflicts

[dinguz]

FYI, there seems to be another issue yielding these error messages. Zenarmor support told me this is fixed in 1.16.3, which should be released near the end of this week.