Bug 879597

Summary:	migrating logging to journalctl regresses ABRT collectors that gathered the log files
Product:	[Fedora] Fedora	Reporter:	Ales Kozumplik <akozumpl>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	akozumpl, jfilak, johannbg, jzeleny, lnykryn, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-05 13:14:56 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:
Bug Depends On:
Bug Blocks:	878826

Description Ales Kozumplik 2012-11-23 12:13:55 UTC

Description of problem:

Currently DNF has a cron job that regularly checks mirrors for metadata updates. Its output was piped to /var/log/dnf-makecache.cron. The ABRT collector in DNF has a line akin to: 

 cp /var/log/dnf-makecache.cron .

so this files is then attached to the reported ticket. Note that the collectors can run under arbitrary user, even an unprivileged one.

Moving to systemd, I changed the line to:

  journalctl _SYSTEMD_UNIT=dnf-makecache.service &>dnf-makecache.log

For a regular user this fails with:

  Unprivileged users can't see messages unless persistent log storage is enabled. Users in the group 'adm' can always see messages.

Components using custom ABRT collectors are thus prevented from migrating to systemd.

Comment 1 Lennart Poettering 2012-11-26 18:07:59 UTC

Hmm, adding the abrt user to the "adm" group sounds like a good, secure solution, no?

Comment 2 Ales Kozumplik 2012-11-27 11:08:28 UTC

Right, but how can we systematically achieve that the user who happens to witness a DNF traceback is in the 'adm' group when he decides to report it?

Comment 3 Jiri Moskovcak 2013-03-27 14:41:50 UTC

Use EVENT=post-create, it will be run with root privs. But please make sure that your script will ALWAYS finish with zero code, otherwise abrt will delete the crash if your script fails.

Comment 4 Fedora End Of Life 2013-12-21 09:29:04 UTC

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2014-02-05 13:15:00 UTC

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.