Since a couple of days ago, I started to see an error message very early during boot time. I am retrieving it here, below, using systemctl. It does not stop the machine from continue booting, but I do not know if it is something serious I should worry about or not?

I have the latest ISO with the latest updates.

$ systemctl --failed

UNIT LOAD ACTIVE SUB DESCRIPTION

● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and Directories

LOAD = Reflects whether the unit definition was properly loaded.

ACTIVE = The high-level unit activation state, i.e. generalization of SUB.

SUB = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.

To show all installed unit files use 'systemctl list-unit-files'.

Thanks,

--Mohamed

I can confirm this.

Perhaps there is a conjunction with the problem reported here:

$systemctl --failed

$systemctl --failed

UNIT LOAD ACTIVE SUB DESCRIPTION

● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and Directories

LOAD = Reflects whether the unit definition was properly loaded.

ACTIVE = The high-level unit activation state, i.e. generalization of SUB.

SUB = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.

To show all installed unit files use 'systemctl list-unit-files'.

$systemctl status systemd-tmpfiles-setup.service

$sudo systemctl status systemd-tmpfiles-setup.service

Wachtwoord:

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories

Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled)

Active: failed (Result: exit-code) since di 2015-03-24 07:33:31 CET; 51min ago

Docs: man:tmpfiles.d(5)

man:systemd-tmpfiles(8)

Process: 254 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)

Main PID: 254 (code=exited, status=1/FAILURE)

mrt 24 07:33:30 thomas-pc systemd[1]: Starting Create Volatile Files and Directories...

mrt 24 07:33:30 thomas-pc systemd-tmpfiles[254]: Setting access ACL "u::rwx,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x...adm:r-x

mrt 24 07:33:31 thomas-pc systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE

mrt 24 07:33:31 thomas-pc systemd[1]: Failed to start Create Volatile Files and Directories.

mrt 24 07:33:31 thomas-pc systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.

mrt 24 07:33:31 thomas-pc systemd[1]: systemd-tmpfiles-setup.service failed.

Hint: Some lines were ellipsized, use -l to show in full.

$ls /usr/lib/tmpfiles.d/

$ls /usr/lib/tmpfiles.d/

etc.conf man-db.conf mysql.conf samba.conf systemd.conf systemd-remote.conf uuidd.conf x11.conf

legacy.conf mkinitcpio.conf nscd.conf sudo.conf systemd-nologin.conf tmp.conf var.conf

When I do "systemctl status systemd-tmpfiles-setup.service -l", it gives more details. It says the reason of failure is "Argument list too long" on /var/log/journal/.../....journal. I am not sure how to trim the argument list though.

$ systemctl status systemd-tmpfiles-setup.service -l

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories

Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled)

Active: failed (Result: exit-code) since Tue 2015-03-24 22:26:29 EET; 1h 0min ago

Docs: man:tmpfiles.d(5)

man:systemd-tmpfiles(8)

Process: 351 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)

Main PID: 351 (code=exited, status=1/FAILURE)

Mar 24 22:26:29 mypan systemd-tmpfiles[351]: Setting access ACL "u::rw-,u:mohamed:r--,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/a1d0c43511b44c5b8508d9fa7e3a772f/user-1000@a67307213d2045549332fc92aca393d4-0000000000017c56-00051207c5c2cc55.journal failed: Argument list too long

Mar 24 22:26:29 mypan systemd-tmpfiles[351]: Setting access ACL "u::rw-,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/a1d0c43511b44c5b8508d9fa7e3a772f/system@0005120b0299d503-c98f6ed3e33334f3.journal~ failed: Argument list too long

Mar 24 22:26:29 mypan systemd-tmpfiles[351]: Setting access ACL "u::rw-,u:mohamed:r--,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/a1d0c43511b44c5b8508d9fa7e3a772f/user-1000@0005120b0466b4bd-274392a97367ea6d.journal~ failed: Argument list too long

Mar 24 22:26:29 mypan systemd-tmpfiles[351]: Setting access ACL "u::rw-,u:mohamed:r--,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/a1d0c43511b44c5b8508d9fa7e3a772f/user-1000.journal failed: Argument list too long

Mar 24 22:26:29 mypan systemd-tmpfiles[351]: Setting access ACL "u::rw-,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/a1d0c43511b44c5b8508d9fa7e3a772f/system@2aed94c1b3db486299eb55c24a77424c-0000000000000001-0005120b02963366.journal failed: Argument list too long

Mar 24 22:26:29 mypan systemd-tmpfiles[351]: Setting access ACL "u::rw-,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/a1d0c43511b44c5b8508d9fa7e3a772f/system.journal failed: Argument list too long

Mar 24 22:26:29 mypan systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE

Mar 24 22:26:29 mypan systemd[1]: Failed to start Create Volatile Files and Directories.

Mar 24 22:26:29 mypan systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.

Mar 24 22:26:29 mypan systemd[1]: systemd-tmpfiles-setup.service failed.

I am testing this fix here for the last 2 weeks already, surprised no earlier complaints for it :) :

So far all works as should now, hoping for a fix from (new) systemd, otherwise systemd will be patched with this solution.

11 days later

hi,i have this error:

systemctl --failed

[root@kaos-pc kaos]# systemctl --failed

UNIT LOAD ACTIVE SUB DESCRIPTION

● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files an

LOAD = Reflects whether the unit definition was properly loaded.

ACTIVE = The high-level unit activation state, i.e. generalization of SUB.

SUB = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.

To show all installed unit files use 'systemctl list-unit-files'.

...skipping...

UNIT LOAD ACTIVE SUB DESCRIPTION

● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files an

LOAD = Reflects whether the unit definition was properly loaded.

ACTIVE = The high-level unit activation state, i.e. generalization of SUB.

SUB = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.

To show all installed unit files use 'systemctl list-unit-files'.

~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

[3]+ Fermato systemctl --failed

[root@kaos-pc kaos]# systemctl status systemd-tmpfiles-setup.service

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories

Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled)

Active: failed (Result: exit-code) since sab 2015-04-04 14:02:45 CEST; 5min ago

Docs: man:tmpfiles.d(5)

man:systemd-tmpfiles(8)

Process: 232 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)

Main PID: 232 (code=exited, status=1/FAILURE)

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,u...

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,u...

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,g...

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,g...

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,g...

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,u...

apr 04 14:02:45 kaos-pc systemd[1]: systemd-tmpfiles-setup.service: main ...RE

apr 04 14:02:45 kaos-pc systemd[1]: Failed to start Create Volatile Files...s.

apr 04 14:02:45 kaos-pc systemd[1]: Unit systemd-tmpfiles-setup.service e...e.

apr 04 14:02:45 kaos-pc systemd[1]: systemd-tmpfiles-setup.service failed.

Hint: Some lines were ellipsized, use -l to show in full.

and

[kaos@kaos-pc ~]$ systemctl status systemd-tmpfiles-setup.service -l

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories

Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled)

Active: failed (Result: exit-code) since sab 2015-04-04 14:02:45 CEST; 22min ago

Docs: man:tmpfiles.d(5)

man:systemd-tmpfiles(8)

Process: 232 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)

Main PID: 232 (code=exited, status=1/FAILURE)

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,u:kaos:r--,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/33fa653d1f004dda80ad1be602950e6b/user-1000@9dffd6c39c794721b809f151128f6df4-000000000000c61a-000512d7a5ac6c9b.journal failed: Argument list too long

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,u:kaos:r--,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/33fa653d1f004dda80ad1be602950e6b/user-1000@9dffd6c39c794721b809f151128f6df4-000000000000d287-000512d7bb1d2af4.journal failed: Argument list too long

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/33fa653d1f004dda80ad1be602950e6b/system@163543184b134001a2e25be8dd2caef2-000000000000d2eb-000512d7c287e600.journal failed: Argument list too long

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/33fa653d1f004dda80ad1be602950e6b/system.journal failed: Argument list too long

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/33fa653d1f004dda80ad1be602950e6b/system@163543184b134001a2e25be8dd2caef2-000000000000c94a-000512d7b31ed639.journal failed: Argument list too long

apr 04 14:02:45 kaos-pc systemd-tmpfiles[232]: Setting access ACL "u::rw-,u:kaos:r--,g::r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:adm:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,g:wheel:r-x,m::r-x,o::---" on /var/log/journal/33fa653d1f004dda80ad1be602950e6b/user-1000.journal failed: Argument list too long

apr 04 14:02:45 kaos-pc systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE

apr 04 14:02:45 kaos-pc systemd[1]: Failed to start Create Volatile Files and Directories.

apr 04 14:02:45 kaos-pc systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.

apr 04 14:02:45 kaos-pc systemd[1]: systemd-tmpfiles-setup.service failed.

[kaos@kaos-pc ~]$

thank for help me

[MODERATOR Note}

Merged into existing topic

sorry for not having seen the topic open, thanks.

bye

i have solved whit:

sudo rm -r /var/log/journal/

sudo mkdir /var/log/journal/

kaos@kaos-pc ~]$ systemctl status systemd-tmpfiles-setup.service -l

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories

Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled)

Active: active (exited) since sab 2015-04-04 14:55:10 CEST; 1min 2s ago

Docs: man:tmpfiles.d(5)

man:systemd-tmpfiles(8)

Process: 231 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=0/SUCCESS)

Main PID: 231 (code=exited, status=0/SUCCESS)

CGroup: /system.slice/systemd-tmpfiles-setup.service

apr 04 14:55:10 kaos-pc systemd[1]: Starting Create Volatile Files and Directories...

apr 04 14:55:10 kaos-pc systemd[1]: Started Create Volatile Files and Directories.

[kaos@kaos-pc ~]

Thank you diabolik62 for your solution. It indeed works.

As far as I know, the drawback is that we lose the history stored in the journal, which is not a big deal in my case.