Q-Feeds Events - nothing shown

[lmoore]

I'm running OPNsense 26.1.8_5 with os-q-feeds-connector 1.6 and when I go to view the events nothing is listed.

Looking in System -> Log Files -> Backend, I am seeing these log entries;

2026-05-22T17:13:33
Error
configd.py
[6381d872-a12b-4043-826d-0548754dcdac] Script action failed with Command '/usr/local/opnsense/scripts/qfeeds/qfeedsctl.py logs ' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 93, in execute subprocess.run(script_command, env=self.config_environment, shell=True, ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ check=not self.disable_errors, stdout=output_stream, stderr=error_stream) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/subprocess.py", line 577, in run raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/qfeeds/qfeedsctl.py logs ' returned non-zero exit status 1.

2026-05-22T10:42:41
Error
configd.py
[687e3cd2-e0d4-4f64-b27c-31bc9b6da13a] Script action failed with Command '/usr/local/opnsense/scripts/qfeeds/qfeedsctl.py logs ' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 93, in execute subprocess.run(script_command, env=self.config_environment, shell=True, ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ check=not self.disable_errors, stdout=output_stream, stderr=error_stream) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/subprocess.py", line 577, in run raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/qfeeds/qfeedsctl.py logs ' returned non-zero exit status 1.

I rebooted OPNsense earlier but it hasn't helped.

Is it just me or are others seeing this issue too?

[Seimus]

I see the same problem with the same error message.

Looks like its broken.

Regards,
S.