Liveview not updating after update to 26.7.9_1

Started by kbsense, November 15, 2026, 06:18:58 PM

Previous topic - Next topic
November 15, 2026, 06:18:58 PM Last Edit: November 15, 2026, 10:39:25 PM by kbsense
Hello,  I am a new forum member.  Started using OPNsense a couple months ago and everything has been perfectly fine.  I have performed several updates  with no problem until today.

Today I updated from OPNsense 26.7.8_2 to 26.7.9_1 and the only problem I am having is the Firewall > Log Files > Live View initially displays a table of entries then pauses indefinitely.  If I refresh the browser, another table of entries displays but then pauses as well.

Tried:
Restarting syslog-ng but didn't help. 
Different browsers (and with incognito mode) with same symptom. 
Finally resorted to rolling back to 26.7.8_2 snapshot and all is back to normal.

I have searched the forum but nothing with same symptoms popped up.

Has anyone else noticed this?

EDIT:  Forgot to mention before the update I did perform both a Health and Connectivity audit and both looked good.

Might as well ask the obvious one first.  Is the "Auto-refresh" option checked under Firewall->Log Files->Live View?
N5105 | 8/250GB | 4xi226-V | Community

Quote from: OPNenthu on November 15, 2026, 06:31:32 PMMight as well ask the obvious one first.  Is the "Auto-refresh" option checked under Firewall->Log Files->Live View?

Yes and also toggled it to make sure.

thanks for the response.   

working fine here. Firefox 159.0.1 on MS Win 10, the client I had available now.

November 16, 2026, 12:31:32 AM #4 Last Edit: November 16, 2026, 03:23:29 AM by kbsense Reason: added more information
While booted into 26.7.9_1 I am seeing hundreds of these lines in System > Log Files > Backend

Quote2026-11-15T17:02:18-06:00   Error   configd.py    [6856c23a-e340-4afd-aeb9-8e386bd24455] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, 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 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.
2026-11-15T17:02:17-06:00   Error   configd.py    [8e45790b-e141-46a5-87c2-e077fe35a9e5] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, 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 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.
2026-11-15T17:02:16-06:00   Error   configd.py    [168a3183-0bf4-497d-ad12-24b21af15142] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, 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 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.
2026-11-15T17:02:15-06:00   Error   configd.py    [3cd53413-2b7a-47cf-bf93-90188de8932b] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, 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 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.
2026-11-15T17:02:14-06:00   Error   configd.py    [8f73efab-a802-4e87-adb3-c5414e24ca68] Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/actions/script_output.py", line 94, 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 578, in run     raise CalledProcessError(retcode, process.args,                              output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'' returned non-zero exit status 1.

And even though the gui liveview isn't updating, I am still able to see logs updating via "opnsense-log -f filter"

I'm also new to OPNsense and the forum. Nevertheless, I see exactly the same error messages with 26.7.9_1 in System->Log Files->Backend and liveview stops working after 10-15 seconds. I've tested both Chrome and Edge on Windows.

Just run the command in question on the shell to reveal the error:

# /usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'

November 16, 2026, 11:08:33 AM #7 Last Edit: November 16, 2026, 11:17:27 AM by franco
File "/usr/local/opnsense/scripts/filter/read_log.py", line 237, in <module>
    elif cmd_args.digest.strip() != '' and cmd_args.digest == rule['__digest__']:
                                                              ~~~~^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

November 16, 2026, 03:50:34 PM #8 Last Edit: November 16, 2026, 04:23:00 PM by kbsense Reason: added information
$ sudo /usr/local/opnsense/scripts/filter/read_log.py --limit '1000' --digest '9f373fb3de43ed83c520b1227642de45'
Traceback (most recent call last):
  File "/usr/local/opnsense/scripts/filter/read_log.py", line 237, in <module>
    elif cmd_args.digest.strip() != '' and cmd_args.digest == rule['__digest__']:
                                                              ~~~~^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

Forgive my lack of intelligence and no disrespect intended,  but is this something we're suppose to understand and fix or is this a coding issue?

Quote from: kbsense on November 16, 2026, 03:50:34 PMForgive my lack of intelligence but is this something we're suppose to understand and fix or is this a coding issue?

This is a bug. The fix has been posted for review.

https://github.com/opnsense/core/pull/11216

November 16, 2026, 04:25:06 PM #10 Last Edit: November 16, 2026, 04:52:59 PM by kbsense
Quote from: tuto2 on November 16, 2026, 04:19:38 PM
Quote from: kbsense on November 16, 2026, 03:50:34 PMForgive my lack of intelligence but is this something we're suppose to understand and fix or is this a coding issue?

This is a bug. The fix has been posted for review.

https://github.com/opnsense/core/pull/11216

Thank you tuto2  Greatly appreciated.


Quote from: franco on November 16, 2026, 07:20:50 PMHotfix 26.7.9_3 is out now.


Cheers,
Franco

Hotfix applied and liveview is now working as intended. 

Thank you OPNsense team for the fast turn around!

out of interest, why is not visible to everyone ie. seemingly only some people affected?

November 16, 2026, 10:38:21 PM #14 Last Edit: November 16, 2026, 11:29:04 PM by franco
The live log has to trigger the new log suppress setting in 26.7.9, which means it has to log exactly the same packets within 30 seconds with no other packets being logged in between. In this case the log would suppress the write of the duplicated packets but write a non-conforming live log line such as:

> Last message '30,,,55bc433c14defd4' repeated 2 times, suppressed by syslog-ng on OPNsense.localdomain

This will then break the log reader producing a fatal Python error mentioned here.

The hotfix does two things:

1. It rolls back the live log suppress so that non-conforming log lines are no longer written, and
2. the log reader now ignores all lines it could not parse skipping over the condition that would show up as an error which makes the live log readable again when broken for this reason (or any other future reason for that matter).


Cheers,
Franco