Problem with systemd-cat-native writting to journal

Hi !

I have a problem with configuring netdata to display logs from journal. Im doing all as in log2journal doc page and example command:

echo ‘172.18.0.1 - - [08/Oct/2024:00:23:42 +0200] “GET /stub_status HTTP/1.1” 404 223 “-” “Netdata go.d.plugin/v1.99.0-267-g634617a74”’ | /opt/netdata/bin/log2journal -f log2journal-nginx.yaml | /opt/netdata/bin/systemd-cat-native

does nothing.

journalctl -f -n 100 shows no new entries, same as journalctl -r -o verbose SYSLOG_IDENTIFIER=nginx-log,
log2journal transforms message correctly.

I’ve tried to read logs from netdata journal but there is nothing aboud systemd-cat-native.

I have done as described in systemd-cat-native and log2journal docs with no luck.

EDIT:

I also noticed, that LOGS tab in netdata cloud is not working. I have " In this room, no node has logs collection configured." message. What i understand from docs, shouldn’t this works without any configuration ? It appears that not even system logs are processed.

That is a bug, we are fixing it.

Thank you for reporting this!

It is already merged and it will be available tomorrow in the nightly builds.
A negative timeout value was timing out immediately and prevented it from processing any logs.

We also added -v or --verbose to print debugging info.

1 Like

Whet it will be fixed ? It is a must-have feature :frowning:

It seems to be working now, i can see now logs appearing in system journal now. But when I use it with verbose for debug info i have msg="PARSER: read failed: POLLHUP." in output. In log tab in cloud panel there is still no logs :frowning:

Any info ? Feature still not working

The OP issue has been fixed, @bemon. What “feature” are you referring to?

Still in “Logs” tab i have " Logs couldn’t be loaded

In this room, no node has logs collection configured. Learn about monitoring logs with Netdata." message.

There is no info on how to configure it becouse it should work “out of the box”. Issue with negative timeout is ok and working - logs in journal appears.

@ilyam8

It means that the system.plugin is not running. This is likely because you are using the static build, right? Including “systemd-journal.plugin” in the static build is technically impossible.

Oh, i didn’t know that. But after a quick peek at documentation, i installed using kickstart script on ubuntu machine. I checked install path - i have files in /opt/netdata so its static.

Thx for pointing that out.

i installed using kickstart script

I guess your Ubuntu version has reached End-of-Life (EOL). We no longer provide package updates for EOL distributions. Consider using the Netdata Docker version if you need systemd-journal.plugin.

[quote=“bemon, post:1, topic:5892”]
I have a problem with configuring netdata to display logs from journal. Im doing all as in log2journal doc page and example command:

echo ‘172.18.0.1 - - [08/Oct/2024:00:23:42 +0200] “GET /stub_status HTTP/1.1” 404 223 “-” “Netdata go.d.plugin/v1.99.0-267-g634617a74”’ | /opt/netdata/bin/log2journal -f log2journal-nginx.yaml | /opt/netdata/bin/systemd-cat-native

does nothing.

journalctl -f -n 100 shows no new entries, same as journalctl -r -o verbose SYSLOG_IDENTIFIER=nginx-log,

In order to confirm that the systemd journal plugin is activated and set correctly, double-check your Netdata configuration file (netdata.conf).