Agent again started to log journalctl

[kozakj95]

Hi, since version 3.9.0 agent again started to log journalctl which had beed fixed in 3.8.0 with variable MZ_SYSTEMD_JOURNAL_TAILER. I tested version 3.8.9 and it is working just fine.

I am using Debian package with config /etc/logdna.env with MZ_SYSTEMD_JOURNAL_TAILER=false
Does anything changed in 3.9.0 version? Can't see any changelog.

Here is link to the previous issue: #358

Can someone please check it out?
Thank you.

[jakedipity]

Thanks for the report @TonyBejl, the behavior of MZ_SYSTEMD_JOURNAL_TAILER should not have changed in the 3.9 release of the agent so this sounds like a bug. We'll investigate it further.

[klynton]

In 3.9.1 I found that setting MZ_SYSTEMD_JOURNAL_TAILER=false AND LOGDNA_JOURNALD_PATHS='' (to an empty string) turns off the journalctl logging.

[kozakj95]

In 3.9.1 I found that setting MZ_SYSTEMD_JOURNAL_TAILER=false AND LOGDNA_JOURNALD_PATHS='' (to an empty string) turns off the journalctl logging.

It seems that it works, thanks.

[showerst]

Just flagging that this is still occurring on Ubuntu in 3.10.2

The workaround identified by Kozak95 above does work.

As an aside, setting MZ_SYSTEMD_JOURNAL_TAILER to False or FALSE (rather than false) will cause the agent to error out, which should at least be documented if not fixed in the parser.