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#41717 - [filesystem] missing systemd-journal-remote group
Attached to Project:
Arch Linux
Opened by Soup (Soup) - Wednesday, 27 August 2014, 15:26 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 28 August 2014, 04:32 GMT
Opened by Soup (Soup) - Wednesday, 27 August 2014, 15:26 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 28 August 2014, 04:32 GMT
|
DetailsDescription: systemd-tmpfiles-setup.service fails
pacman -Q systemd filesystem systemd 216-1 filesystem 2014.07-1 Aug 27 17:13:15 host systemd-tmpfiles[445]: [/usr/lib/tmpfiles.d/systemd-remote.conf:10] Unknown group 'systemd-journal-remote'. Aug 27 17:13:15 host systemd-tmpfiles[445]: [/usr/lib/tmpfiles.d/systemd-remote.conf:11] Unknown group 'systemd-journal-remote'. Aug 27 17:13:16 host systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE Aug 27 17:13:16 host systemd[1]: Failed to start Create Volatile Files and Directories. systemctl list-unit-files|grep journal-remote systemd-journal-remote.service static systemd-journal-remote.socket disabled |
This task depends upon

This wasn't meant to be added to filesystem. systemd-sysusers takes care of creating the group on upgrade.

So then I must've screwed up when reconciling my groups pacnew. Sorry for the noise.