Bug 1177335

Summary:	journald Storage=none does not work as expected
Product:	[Fedora] Fedora	Reporter:	GV <rhel>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	21	CC:	johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-05 00:29:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***