On 2013-07-20 08:18 +0200, Josh Triplett wrote: > Package: systemd > Version: 204-1 > Severity: normal > File: systemd-journald > > systemd-journald expects a group systemd-journal to exist: > [ 7.667864] systemd-journald[326]: Failed to resolve 'systemd-journal' > group: No such process
This is almost surely related to this upstream change: ,---- | CHANGES WITH 198: | | * The journal files are now owned by a new group | "systemd-journal", which exists specifically to allow access | to the journal, and nothing else. Previously, we used the | "adm" group for that, which however possibly covers more | than just journal/log file access. This new group is now | already used by systemd-journal-gatewayd to ensure this | daemon gets access to the journal files and as little else | as possible. Note that "make install" will also set FS ACLs | up for /var/log/journal to give "adm" and "wheel" read | access to it, in addition to "systemd-journal" which owns | the journal files. We recommend that packaging scripts also | add read access to "adm" + "wheel" to /var/log/journal, and | all existing/future journal files. To normal users and | administrators little changes, however packagers need to | ensure to create the "systemd-journal" system group at | package installation time. `---- > However, systemd does not create this group. As a result, journalctl doesn't work: ,---- | $ journalctl | Hint: You are currently not seeing messages from other users and the system. | Users in the 'systemd-journal' group can see all messages. Pass -q to | turn off this notice. | No journal files were opened due to insufficient permissions. `---- Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org