systemd-journal.plugin high CPU and Logs not working

Help
1

Hi,

Since upgrading to V2 agent my Logs are no longer working. If I click logs and wait a while I get

Error - 504
Timeout while waiting for a response from the plugin that serves this features

systemd-journal.plugin sits at approximately 30% of 1 CPU after the first time I click on the logs panel , but no disk activity indicating it is indexing logs etc.
After clicking on the logs panel the CPU consumption continues until I restart the Netdata container.

This was working fine until I upgraded to agent v2

Server info Ubuntu, 22.04.4 LTS 16GB of Ram, 8Cpu.

Netdata version v2.0.0-18-nightly, Business Subscription.

Running in container (as root) with docker-compose, pretty much the default docker.compose.yaml, including bind mounts to /var/log etc.

Anyone else seeing this with the latest builds?

2

I have the exact same issue since upgrading to v2.

3

@Maher @wstallwood thanks for reporting, we are looking into it.

4

Fixed in add missing spinlock unlocks on containers by ktsaou · Pull Request #19011 · netdata/netdata · GitHub. We will do v2.0.1.

1 Like
5

Thank you! pulled the v2.0.1 container tag just now and confirm logs are working again.

Impressive quick fix !

6

Indeed, I can also confirm v2.0.1 fixes this issue on my end too. Thank you, @ilyam8.

1 Like