Saw this in the Backend Log after updating to 25.7.2:
opnsense error:
[3910c104-62e6-4f14-8bd5-148de80c702e] Script action failed with Command '/usr/local/opnsense/scripts/filter/pftablecount.py ''' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 78, in execute subprocess.run(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.11/subprocess.py", line 571, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/pftablecount.py ''' returned non-zero exit status 1.
It is non-critical.
D
Can you run it from the shell and see why it would return an error?
# /usr/local/opnsense/scripts/filter/pftablecount.py
Thanks,
Franco
I got the same logged error, but running from a shell seems to work:
root@fw:/home/user # /usr/local/opnsense/scripts/filter/pftablecount.py
{"status":"ok","size":2000000, [...] "out_block_p":0,"out_block_b":0,"out_pass_p":0,"out_pass_b":0}}}
root@fw:/home/user #
Edit: non-root:
user@fw:~ $ /usr/local/opnsense/scripts/filter/pftablecount.py
Traceback (most recent call last):
File "/usr/local/opnsense/scripts/filter/pftablecount.py", line 49, in <module>
if "-" in parts[0]:
~~~~~^^^
IndexError: list index out of range
user@fw:~ $
It happens on reboots for me. Reproducible. Attached is a screenshot. It looks like it runs fine using CLI. Attached is the output I get.
Best,
D
I also tried usr login and got this as well:
File "/usr/local/opnsense/scripts/filter/pftablecount.py", line 49, in <module>
Missing name for redirect.
if "-" in parts[0]:
if: Badly formed number.
IndexError: list index out of range
IndexError:: Too many arguments.
Can you try this patch?
# opnsense-patch https://github.com/opnsense/core/commit/6ee6d9d8
Cheers,
Franco
Quote from: franco on August 22, 2025, 11:17:26 AMCan you try this patch?
# opnsense-patch https://github.com/opnsense/core/commit/6ee6d9d8
Cheers,
Franco
I applied the patch, but still same error after reboot.
[62298fa6-e6e7-4699-a704-987777bdd904] Script action failed with Command '/usr/local/opnsense/scripts/filter/pftablecount.py ''' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 78, in execute subprocess.run(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.11/subprocess.py", line 571, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/pftablecount.py ''' returned non-zero exit status 1.
Also performed a health check and it showed a checksum error:
opnsense-25.7.2: checksum mismatch for /usr/local/opnsense/scripts/filter/pftablecount.py
May I ask a really "stupid" question? I haven't updated my home APU2D4 firewall, so I'm only looking at version 25.7.1_1 of OPNsense.
Are you trying to reduce the number of processes running as root? Are you improving security by executing processes with least privilege?
If the process is not executing as root (or group wheel), the txt files in /var/db/aliastables can't be read.
I see that many of the files in /var/db/aliastables have permission "-rw-r----- 1 root wheel"
Gary
@Jackknife4782 - the checksum error results from the patch you applied. It is to be expected.
D
Quote from: Gary7 on August 22, 2025, 04:08:42 PMMay I ask a really "stupid" question? I haven't updated my home APU2D4 firewall, so I'm only looking at version 25.7.1_1 of OPNsense.
Are you trying to reduce the number of processes running as root? Are you improving security by executing processes with least privilege?
If the process is not executing as root (or group wheel), the txt files in /var/db/aliastables can't be read.
I see that many of the files in /var/db/aliastables have permission "-rw-r----- 1 root wheel"
Gary
I sign in to opnsense using a non-root user as admin. Not technical enough to answer you questions beyond that. I just noticed the error after the upgrade and was curious if it is normal or not. Thanks for the advice though.
Quote from: davidfi01 on August 22, 2025, 09:40:00 PM@Jackknife4782 - the checksum error results from the patch you applied. It is to be expected.
D
Ah, I understand. Thanks
Meanwhile I can reproduce this once at boot and https://github.com/opnsense/core/commit/61f13a516914 on top of the other commit seems to do the trick. Either case it's only cosmetic and it will be fixed in 25.7.3.
Cheers,
Franco
So, my router has been randomly disconnecting or basically not doing any of it's jobs. Happens a couple of times a day. OP Error is the only error I could find in the logs.
I applied the patches. It was ok for a bit but now it's not even rebooting at all. Something completely nuked the drive i had (The router was using a AM4 motherboard with a 5700 processor and a 256GB nvme drive). I reverted to the dec750 i had which had a muchh older (24.1) version running for now. I'm not sure what went wrong or when I can update, but now i'm scared to update.
It's unrelated to this particular issue.