Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47161 - systemd-journal-upload user is potentially missing systemd-journal group
Attached to Project:
Arch Linux
Opened by Daniel Speichert (dasp) - Monday, 23 November 2015, 20:56 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 27 September 2017, 16:26 GMT
Opened by Daniel Speichert (dasp) - Monday, 23 November 2015, 20:56 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 27 September 2017, 16:26 GMT
|
DetailsDescription:
systemd-journal-upload cannot upload anything unless it's given access to system journals. Intuitively, one would expect it has access to system journals. However, this service runs as a system user of the same name and according to documentation [1]: "Unless limited by one of the options specified below, all journal entries accessible to the user the program is running as will be uploaded, and then the program will wait and send new entries as they become available." The user systemd-journal-upload does not have access to any logs by default, even though it is automatically created. Additional info: * package version(s) systemd: 227-1 * config and/or log files etc. Steps to reproduce: * Configure and run systemd-journal-upload How to fix: * usermod systemd-journal-upload -G systemd-journal [1] http://www.freedesktop.org/software/systemd/man/systemd-journal-upload.html |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 27 September 2017, 16:26 GMT
Reason for closing: Fixed
Additional comments about closing: According to upstream
Wednesday, 27 September 2017, 16:26 GMT
Reason for closing: Fixed
Additional comments about closing: According to upstream

Please report this upstream -- the systemd-journal-upload user is created (and therefore somewhat managed) by a sysusers.d fragment.

Tracking: https://github.com/systemd/systemd/issues/2051

This should be fixed (quite a while ago), right?