"b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"

[Cljackhammer]

Expriening a flood of these errors after updating Zenarmor today. The Zenarmor periodicals CRON job is the culprit.

   *   *   *   *   Zenarmor periodicals   Sensei periodicals

2025-01-23T18:59:01-05:00   Error   configd.py   [1d76c18e-5413-43eb-91d2-5f9375733079] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"

[Cljackhammer]

I identified the issue. The Zenarmor periodicals script is doign a pkg info against opnsense. I'm running the opnsense RC, so the package name is is opnsense-devel, resulting in a failure, I addressed it on my end. I assume that this issue will be resolved when I apply the release version of opnsense. I just need to remember to revise the script.

[IHK]

Thank you for your feedback.

If you have any questions or need assistance with anything, please don't hesitate to reach out to us.

We're always happy to help!

[esbiko]

Hi,

i'm new to opnsense and zenarmor and i'm facing the same issue on opnsense business edition 24.10.1

Is there anything I can do to prevent this error?

[sy]

Hi,

Do you see this error during the update, Can you share the error log?

[esbiko]

updatet this morning to 24.10.2. Error still exists.

2025-02-05T06:46:00    Error    configd.py    [3ed608d0-2266-481d-b2f9-cef160bd8ac6] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"
2025-02-05T06:45:06    Error    configd.py    [9da07f1b-2606-4e50-be3b-dcffa0288428] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"
2025-02-05T06:44:00    Error    configd.py    [f1bd3f6a-c4b5-4020-94c1-903ce3d5f694] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"
2025-02-05T06:43:00    Error    configd.py    [d1f2209c-e68a-4db8-86f4-581c15a303b9] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"
2025-02-05T06:42:00    Error    configd.py    [8bab1e94-39c5-4d96-a4c3-85f66a0c3acd] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"
2025-02-05T06:41:00    Error    configd.py    [e4fe2ab7-41d0-4080-bcde-149c75a19e42] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"
2025-02-05T06:40:00    Error    configd.py    [22d16ebe-0932-4192-bf16-1a6d7e935513] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"
2025-02-05T06:39:00    Error    configd.py    [8fbca610-6c3c-4f64-95ad-fb879a7d938b] Script action stderr returned "b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'"



***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.10.2 (amd64) at Wed Feb  5 06:51:22 CET 2025
Strict TLS 1.3 and CRL checking is enabled.
Fetching subscription information, please wait... done
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 874 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ... done
Processing entries: ....... done
SunnyValley repository update completed. 66 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (87 candidates): .......... done
Processing candidates (87 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

[sy]

Hi Thanks for reporting the issue.


This minor bug doesn't impact the process; it only manifests in the logs.

They'll address it in version 1.18.6, which is slated for release next week.


Best regards

[esbiko]

yes, thanks for the info

[sy]

Hi,

Have you had the opportunity to upgrade Zenarmor to version 1.18.6? Can you verify if the problem has been fixed?