opnsense / opnsense/plugins

[os-qfeeds-connector] - Events nothing shown

Open
#5,474 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
1.2k
Forks
863
Avg merge
2d 6h
Merged PRs (30d)
10

Description

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug
When opening the events tab within the plugin, no events are showing.

To Reproduce
Steps to reproduce the behavior:
Not able to reproduce it myself unfortunately but several users reported it on the forum including logs:
https://forum.opnsense.org/index.php?topic=51952

Expected behavior
Events showing

Screenshots
If applicable, add screenshots to help explain your problem.
N/A

Relevant log files
2026-05-22T17:13:33 Error [configd.py](https://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](https://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](https://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](https://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.

Environment
OPNsense 26.1.8_5 with os-q-feeds-connector 1.6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with /usr/local/opnsense/scripts/qfeeds/qfeedsctl.py, especially the logs action, and review the provided configd.py traceback and forum reports. Reproduce or trace why the logs command exits with status 1; done means the Events tab displays events without that configd error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.