Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[solved] systemd-219: Failed to start Create Volatile...
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
chl
n00b
n00b


Joined: 13 May 2003
Posts: 60
Location: Munich

PostPosted: Sat Feb 21, 2015 8:03 am    Post subject: [solved] systemd-219: Failed to start Create Volatile... Reply with quote

After updating to systemd-219 I noticed the following error message during boot: "Failed to start Create Volatile Files and Directories." which comes from systemd-tmpfiles-setup.service.

The full output of
Code:
systemctl status systemd-tmpfiles-setup.service
is:

Code:
systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/usr/lib64/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sa 2015-02-21 08:37:59 CET; 1min 1s ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 223 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
 Main PID: 223 (code=exited, status=1/FAILURE)

Feb 21 08:37:59 t520 systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Feb 21 08:37:59 t520 systemd[1]: Failed to start Create Volatile Files and Directories.
Feb 21 08:37:59 t520 systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Feb 21 08:37:59 t520 systemd[1]: systemd-tmpfiles-setup.service failed.


I could track down the source of the problem to two lines that were added to /usr/lib64/tmpfiles.d/systemd.conf in systemd-219:
Code:
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


(When I downgrade to systemd-218 or comment them out, the problem disappears.)

I have not found any specific bug reports so far, so I am wondering whether this is a bug of systemd or just a specific problem I have.
Since I am not familiar with the syntax of these conf-files and the respective man pages are not very helpful too, maybe somebody could explain me what these lines exactly mean.

[Edit]: My understanding is that these lines shall provide read rights for the groups adm and wheel to the journals in /var/log/journal/[machine id]/.

Moreover, I am curious whether anybody else has the same problem.

Thanks in advance
CHL
_________________
The difficulty in designing something completely foolproof, is not to underestimate the ingenuity of complete fools.


Last edited by chl on Sat Feb 21, 2015 8:34 am; edited 1 time in total
Back to top
View user's profile Send private message
mv
Advocate
Advocate


Joined: 20 Apr 2005
Posts: 4890

PostPosted: Sat Feb 21, 2015 8:19 am    Post subject: Reply with quote

/usr/share/doc/systemd-219/NEWS.xz wrote:

* journald now sets the special FS_NOCOW file flag for its
journal files. This should improve performance on btrfs

You do not use btfrs but systemd - this is forbidden. You must give systemd the absolute control over your system and organize it exactly in the way that the systemd people want, for otherwise you obviously deserve breakage in their mind.
Back to top
View user's profile Send private message
chl
n00b
n00b


Joined: 13 May 2003
Posts: 60
Location: Munich

PostPosted: Sat Feb 21, 2015 8:36 am    Post subject: Reply with quote

I just found the solution.

CONFIG_EXT4_FS_POSIX_ACL was not set in my kernel config. Accordingly it was not possible to add rights for multiple groups.

CHL
_________________
The difficulty in designing something completely foolproof, is not to underestimate the ingenuity of complete fools.
Back to top
View user's profile Send private message
mv
Advocate
Advocate


Joined: 20 Apr 2005
Posts: 4890

PostPosted: Sat Feb 21, 2015 9:03 am    Post subject: Reply with quote

chl wrote:
CONFIG_EXT4_FS_POSIX_ACL was not set in my kernel config

It's a bad idea to set this if you do not actually want to use it.
I only can repeat: Before setting up the system in the way systemd wants, you are much better off by dumping systemd and using the setup that you need, instead.
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 3905
Location: The Peanut Gallery

PostPosted: Sat Feb 21, 2015 12:57 pm    Post subject: Reply with quote

chl: mv is not trolling you; he's just getting over lost time investment. Normally he'd have been the person helping you with systemd (and I wouldn't be anywhere near this topic.;)

Glad you got it sorted.
Back to top
View user's profile Send private message
mv
Advocate
Advocate


Joined: 20 Apr 2005
Posts: 4890

PostPosted: Sat Feb 21, 2015 1:49 pm    Post subject: Reply with quote

steveL wrote:
Normally he'd have been the person helping you with systemd

Well, actually this problem is exactly of the same type which I experienced:

The real reason of both problems is that the systemd developers have only a few settings in mind when they develop systemd. If you use a setting which they did not think about, they do not realize that what is actually wrong is their imposing of broken concepts over a working infrastructure. They do not realize that their concepts are broken but claim that your infrastructure is buggy (how can it be different if their ingenious concept does not work with it, in principle?)

Forcing you to use acl on your filesystem for absolutely no other purpose but to make acl non-optional is such a symptom.
(In fact, the whole story with COW is to force you to btrfs in the long run: It would against their plans of future binary blob disitrubtion if you refuse to change to btrfs).
Quote:
Glad you got it sorted.

I really do not think that enabling acl is a solution if you do not use acl for anything else; better fix the broken rules.
Back to top
View user's profile Send private message
mv
Advocate
Advocate


Joined: 20 Apr 2005
Posts: 4890

PostPosted: Sat Feb 21, 2015 2:34 pm    Post subject: Reply with quote

Here is how you can currently fix the issue without enabling acl: Use this file as /etc/portage/env/sys-apps/systemd
Code:
post_src_install() {
   local i j k
   einfo "mv's hack from ${PORTAGE_CONFIGROOT%/}/etc/portage/env/${CATEGORY}/${PN}"
   k=false
   for i in "${ED}"/usr/lib/tmpfiles.d/*.conf
   do   j=${T}/tmfiles.d-fix
      sed -e 's/^\(.*group:[^ ]*group:.\)/#\1/' -- "${i}" >"${j}"
      diff -q -- "${i}" "${j}" >/dev/null 2>&1 && continue
      einfo "Fixing ${i##*/}"
      k=:
      cat -- "${j}" >"${i}"
   done
   ${k} || die "mv's hack has become redundant: Please remove it"
}
Reemerge systemd afterwards.
Of course, this fix consists just in commenting all offending lines...
Back to top
View user's profile Send private message
poncho
n00b
n00b


Joined: 06 Mar 2011
Posts: 71

PostPosted: Sat Feb 21, 2015 3:36 pm    Post subject: Reply with quote

those lines should be disabled if the acl useflag is not set... shouldn't they?

from http://cgit.freedesktop.org/systemd/systemd/tree/tmpfiles.d/systemd.conf.m4
Code:
m4_ifdef(`HAVE_ACL',``
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
'')m4_dnl
Back to top
View user's profile Send private message
mv
Advocate
Advocate


Joined: 20 Apr 2005
Posts: 4890

PostPosted: Sat Feb 21, 2015 5:57 pm    Post subject: Reply with quote

poncho wrote:
those lines should be disabled if the acl useflag is not set... shouldn't they?

You are right: It seems indeed not intentional; I withdraw what I said about similarity with my other issue.
But they aren't disabled: So it looks like an ordinary bug in the systemd build system...
It seems that somebody should report this bug. I won't.
Back to top
View user's profile Send private message
chl
n00b
n00b


Joined: 13 May 2003
Posts: 60
Location: Munich

PostPosted: Sat Feb 21, 2015 7:52 pm    Post subject: Reply with quote

@poncho
Code:
m4_ifdef(`HAVE_ACL',``
...
'')m4_dnl


These lines were the hint that lead me to my "solution". They are included the commit by which the offending lines were added, but they have however not made it into the source of 219.

@mv:
Thanks for the hack and your remarks about ACL. I have decided to comment out the offending lines.

Btw: Which, in your opinion, is the best alternative to systemd on a desktop?

CHL
_________________
The difficulty in designing something completely foolproof, is not to underestimate the ingenuity of complete fools.
Back to top
View user's profile Send private message
mv
Advocate
Advocate


Joined: 20 Apr 2005
Posts: 4890

PostPosted: Sat Feb 21, 2015 8:33 pm    Post subject: Reply with quote

chl wrote:
Btw: Which, in your opinion, is the best alternative to systemd on a desktop?

With Gentoo, I have only experience with openrc and systemd as init systems. Everything else requires a lot of manual work, since in Gentoo packages come usually only with openrc and/or systemd scripts.
In the moment, openrc can be used without any problem (even with a global USE=systemd and systemd as the udev provider):
I liked to have the possibility to switch between openrc and systemd during booting - this saved me from some troubles. Unfortunately, systemd has become unusable for me due to the problem in the thread steveL mentioned.
Perhpas SteveL is right: I am very angry in the moment about systemd, so maybe my assertions are currently very biased.

Since you emphasize "desktop": Some GUIs like Gnome are written to work only with systemd. However, many don't. For instance, I use fvwm which probably never will require systemd. I know that SteveL uses KDE without systemd, but I have heard that new versions of KDE might be depending on systemd, too. Of course, nobody knows what will be in the future; maybe some systemd-shim will be provided to make at least KDE work without systemd.
Back to top
View user's profile Send private message
poncho
n00b
n00b


Joined: 06 Mar 2011
Posts: 71

PostPosted: Mon Mar 09, 2015 9:25 am    Post subject: Reply with quote

mv wrote:
So it looks like an ordinary bug in the systemd build system...
It seems that somebody should report this bug. I won't.


https://bugs.gentoo.org/show_bug.cgi?id=542644
Back to top
View user's profile Send private message
nenemsis5
n00b
n00b


Joined: 23 Oct 2007
Posts: 71

PostPosted: Sun Mar 15, 2015 12:00 am    Post subject: Reply with quote

chl wrote:
I just found the solution.

CONFIG_EXT4_FS_POSIX_ACL was not set in my kernel config. Accordingly it was not possible to add rights for multiple groups.

CHL



i have turn on this, but i still have this bug :((


plz confirn on thin GBZ

https://bugs.gentoo.org/show_bug.cgi?id=543332


Code:
 # systemctl status systemd-tmpfiles-setup.service
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/usr/lib64/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since So 2015-03-15 00:26:23 CET; 34min ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 1836 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
 Main PID: 1836 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum