Open Log Live view 100% CPU

[Mks]

Dear all,

On the most recent version I can't open the Live view or if it works CPU increase to 100%

Code Select Expand

Script action failed with Command '/usr/local/opnsense/scripts/filter/read_log.py /limit '25' /digest ''' died with <Signals.SIGKILL: 9>. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 478, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.8/subprocess.py", line 364, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/filter/read_log.py /limit '25' /digest ''' died with <Signals.SIGKILL: 9>.

Screenshot from Activity Diagnostic attached.

Any idea?

br

[Fright]

hi
have you tried to reset the logs (System: Settings: Logging)?

[Mks]

Hi,
yes I did.

Surprisingly it happens only when I try to open the live view.

System Log General entries:

Code Select Expand


2021-10-09T15:22:23 configd[3538] [2021-10-09T15:22:23+02:00][error] Timeout (120) executing : filter read log '25' '95e5f1972873ad7055ee5cbbd2ff0a0c'
2021-10-09T15:22:23 configd[66184] [2021-10-09T15:22:23+02:00][error] Timeout (120) executing : filter read log '25' ''
2021-10-09T15:22:23 configd[95445] [2021-10-09T15:22:23+02:00][error] Timeout (120) executing : filter read log '25' '95e5f1972873ad7055ee5cbbd2ff0a0c'
2021-10-09T15:20:56 kernel pid 98762 (python3.8), jid 0, uid 0, was killed: out of swap space
2021-10-09T15:20:26 kernel pid 44176 (python3.8), jid 0, uid 0, was killed: out of swap space


May any hint on this?

br

[Fright]

not enough info but it looks like some process consumes resources and at some point other processes do not have enough resources.
when you are not trying to watch the live log are there processes with increased memory consumption?

[Mks]

Hi,

thanks for supporting me in the issue, process with highest CPU consumption is:

Code Select Expand

/usr/local/bin/python3 /usr/local/opnsense/scripts/filter/read_log.py /limit 100 /digest b11d67e7c9f3bb1e75af692a1367b613 (python3.8)

br

[Fright]

it looks like it is.
maybe this is still the consequences of corrupted logs
you can just kill this process via shell or reboot opnsene if the situation allows

[Mks]

Hi,

maybe this is still the consequences of corrupted logs
you can just kill this process via shell or reboot opnsene if the situation allows

Tried several times, even new installation, but still the same :(

br

[Fright]

hm.
may be "circular logs" ..
if "Disable circular logs" is not enabled at System: Settings: Logging can you please enabled it, Save settings, then Reset log files and check live view again?

[Mks]

Thanks, seems to work. I'll have a further look on it but it looks good.
:)

br