Bug 1177335 - journald Storage=none does not work as expected
Summary: journald Storage=none does not work as expected
Keywords:
Status: CLOSED DUPLICATE of bug 1147651
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 21
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-26 09:17 UTC by GV
Modified: 2015-01-05 00:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-05 00:29:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description GV 2014-12-26 09:17:44 UTC 
Description of problem:
The journald.conf manual describe Storage=none as follow:

"none" turns off all storage, all log data received will be dropped. Forwarding to other targets, such as the console, the kernel log buffer or a syslog daemon will still work however.

However, if Storage=none and ForwardToSyslog=yes in /etc/systemd/journald.conf no syslog messages are actually forwarded to rsyslog. Everything works fine with Storage=volatile.

Version-Release number of selected component (if applicable):
systemd-216-12.fc21.x86_64
Comment 1 Lennart Poettering 2015-01-05 00:29:25 UTC 
Yeah, rsyslog is nowadays pulling out the data directly from the journal and does not accept data forwarded via ForwardToSyslog=yes anymore. There's little we can do about that from the systemd side. Use Storage=volatile in combination with current rsyslog.

Anyway, nothing to fix in journald here. It's a change of behaviour on rsyslog's side we can do little about.
Comment 2 Lennart Poettering 2015-01-05 00:34:00 UTC 

*** This bug has been marked as a duplicate of bug 1147651 ***
Note You need to log in before you can comment on or make changes to this bug.