[systemd-devel] Systemd-219: Failed to start Create Volatile...

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Tue Mar 3 09:50:29 PST 2015

On Mon, Mar 02, 2015 at 05:07:40PM -0300, RicΛrdo Bastos™ wrote:
> Hi all,
> I'm using this tip to solve problem in systemd-TMPFILES-setup.service:
> http://forums.gentoo.org/viewtopic-t-1011254-view-previous.html?sid=4a7ba76e913f9555596abfa6e09aee95
> <http://www.google.com/url?q=http%3A%2F%2Fforums.gentoo.org%2Fviewtopic-t-1011254-view-previous.html%3Fsid%3D4a7ba76e913f9555596abfa6e09aee95&sa=D&sntz=1&usg=AFQjCNEAeFsiM_50wA7SSsdJej8T6aPpQA>
> So I commented the following lines in systemd.conf file:
> # a+ /var/log/journal/%m - - - - d:group:adm:r-x,d:group:wheel:r-x
> # A+ /var/log/journal/%m - - - - group:adm:r-x,group:wheel:r-x
> Now the service is starting correctly :)
> *# **Active: active (exited) since Seg 2015-03-02 13:37:04 BRT; 3h 1min ago*
You get the warning most likely because the filesystem that
/var/log/journal or /run/log/journal are on does not support ACL. So
users in the wheel and adm groups will not be given access to the
journal through ACLs.
This isn't really a problem — apart from the unsightly warning in the
logs, and the missing access, this should not have any other effects.

I pushed a commit to reduce the warning to debug level if the fs
does not support ACLs.


More information about the systemd-devel mailing list