OPNsense Forum

English Forums => 25.1, 25.4 Production Series => Topic started by: Cljackhammer on January 24, 2025, 01:23:27 AM

Title: b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'
Post by: Cljackhammer on January 24, 2025, 01:23:27 AM
Expriening a flood of these errors after updating to the RC. Also, you might want to mention that after this upgrade you might not be able access the Web-GUI because a default deny firewall rule blocks access. I had to disable the packet filter on the command line and specifically add a rule to my lan interface allowing ip's from my lan to access the lan address 192.168.1.1 on port 443.

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'"
Title: Re: b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'
Post by: Cljackhammer on January 24, 2025, 01:26:59 AM
This error is being logged every minute. Not good.
Title: Re: b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'
Post by: Cljackhammer on January 24, 2025, 01:33:49 AM
I just ran a health check and it came up clean. Not sure wha'ts going on here.
Title: Re: b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'
Post by: Cljackhammer on January 24, 2025, 01:44:03 AM
Well, found the issue. This Zenarmor CRON job is the culprit. I will post a message on the Zenarmor forum.

*   *   *   *   *   Zenarmor periodicals   Sensei periodicals    


Title: Re: b'pkg: No package(s) matching opnsense\n[: !=: unexpected operator'
Post by: Cljackhammer on January 24, 2025, 02:25:46 AM
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.