[Bug 991190] New: journald does not create /run/systemd/journal/syslog
http://bugzilla.novell.com/show_bug.cgi?id=991190 Bug ID: 991190 Summary: journald does not create /run/systemd/journal/syslog Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jslaby@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have rsyslogd, but I see no daemon messages in /var/log/messages. rsyslog.conf contains also: $ModLoad imuxsock.so *.*;mail.none;news.none -/var/log/messages I suspect journald is the cause as journactl log shows the messages from daemons, but it does not seem to forward the messages. Despite I have "ForwardToSyslog=yes" in /etc/systemd/journald.conf, /run/systemd/journal/syslog does not exist. So there is no socket to pull the messages from... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c3 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #3 from Jiri Slaby <jslaby@suse.com> --- (In reply to Dr. Werner Fink from comment #1)
I don't care about paths journald listens on at all. man:journald.conf(5) FORWARDING TO TRADITIONAL SYSLOG DAEMONS Journal events can be transferred to a different logging daemon in two different ways. With the first method, messages are immediately forwarded to a socket (/run/systemd/journal/syslog), where the traditional syslog daemon can read them. This method is controlled by the ForwardToSyslog= option. (In reply to Dr. Werner Fink from comment #2)
Btw: After rsyslog here and enabling ForwardToConsole=yes in /etc/systemd/journald.conf and rebooting the system I see
I haven't tried to reboot, I only restarted the service which should be enough IMO. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c4 --- Comment #4 from Jiri Slaby <jslaby@suse.com> --- On my other system, I have /run/systemd/journal/syslog even though ForwardToSyslog=no. So how is this option suppose to work? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c5 --- Comment #5 from Jiri Slaby <jslaby@suse.com> --- (In reply to Jiri Slaby from comment #4)
On my other system, I have /run/systemd/journal/syslog even though ForwardToSyslog=no.
Ok, on my other system, the option correctly controls whether the messages go to rsyslog or not. Byut on my primary system, /run/systemd/journal/syslog does not exist in the first place. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c8 --- Comment #8 from Jiri Slaby <jslaby@suse.com> --- To conclude: restart of syslog.socket service was needed. That is the one responsible for creating the socket. BTW shouldn't enabling of some syslog service (like rsyslog) enable the ForwardToSyslog journald option? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c3 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #3 from Jiri Slaby <jslaby@suse.com> --- (In reply to Dr. Werner Fink from comment #1)
I don't care about paths journald listens on at all. man:journald.conf(5) FORWARDING TO TRADITIONAL SYSLOG DAEMONS Journal events can be transferred to a different logging daemon in two different ways. With the first method, messages are immediately forwarded to a socket (/run/systemd/journal/syslog), where the traditional syslog daemon can read them. This method is controlled by the ForwardToSyslog= option. (In reply to Dr. Werner Fink from comment #2)
Btw: After rsyslog here and enabling ForwardToConsole=yes in /etc/systemd/journald.conf and rebooting the system I see
I haven't tried to reboot, I only restarted the service which should be enough IMO. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c4 --- Comment #4 from Jiri Slaby <jslaby@suse.com> --- On my other system, I have /run/systemd/journal/syslog even though ForwardToSyslog=no. So how is this option suppose to work? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c5 --- Comment #5 from Jiri Slaby <jslaby@suse.com> --- (In reply to Jiri Slaby from comment #4)
On my other system, I have /run/systemd/journal/syslog even though ForwardToSyslog=no.
Ok, on my other system, the option correctly controls whether the messages go to rsyslog or not. Byut on my primary system, /run/systemd/journal/syslog does not exist in the first place. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c8 --- Comment #8 from Jiri Slaby <jslaby@suse.com> --- To conclude: restart of syslog.socket service was needed. That is the one responsible for creating the socket. BTW shouldn't enabling of some syslog service (like rsyslog) enable the ForwardToSyslog journald option? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com