3

I'm currently working on enabling and disabling ForwardToSyslog option in systemd-journald at runtime.

When I set it to "no" -> ForwardToSyslog=no in /etc/systemd/journald.conf followed by systemctl restart systemd-journald my rsyslog generated files stop receiving info.

My problem:

Reenabling forwarding to syslog by doing: ForwardToSyslog=yes in /etc/systemd/journald.conf followed by systemctl restart systemd-journald is NOT followed by getting logs inside rsyslog files.

Only newly started systemd services have logs forwarded, but those that were running need to be restarted.

My question:

Is this a bug of a systemd-journald?

Is there a better way to have logs forwarded to syslog than by restarting all of the running services?

EDIT:

I use systemd 230

Improve this question
4
  • You need to tell people what version of systemd this is. It affects answers.
    – JdeBP
    Commented Mar 8, 2017 at 18:53
  • 1
    It's 230. I've edited the post.
    – lewiatan
    Commented Mar 8, 2017 at 19:12
  • You should comment on github.com/systemd/systemd/issues/2236, it sounds like you've reproduced a bug that was thought to be fixed in a relatively current version of systemd.
    – Mark Stosberg
    Commented Mar 8, 2017 at 19:25
  • I have posted on that issue thread that I reproduced the issue with systemd 230 and 232. I hope it will get resolved..
    – lewiatan
    Commented Mar 9, 2017 at 12:17

1 Answer 1

Reset to default
2

This is bug in systemd that was believed to be fixed.

It sounds like you've reproduced it in a relatively current version of systemd, so you should comment on the bug and follow-up with the developers.

Thanks to @JdeBP for the issue reference.

Improve this answer
1
  • 1
    Thanks. I'll try to reproduce it with the even newer version and then post there if it's not fixed
    – lewiatan
    Commented Mar 8, 2017 at 19:30

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .