Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 543332 - sys-apps/systemd-219-r2 +USE="alc" but systemd-tmpfiles-setup.service - Failed to start Create Volatile Files and Directories.
Summary: sys-apps/systemd-219-r2 +USE="alc" but systemd-tmpfiles-setup.service - Faile...
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: Highest critical (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-14 17:07 UTC by tman
Modified: 2015-09-27 06:41 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tman 2015-03-14 17:07:42 UTC
http://forums.gentoo.org/viewtopic-t-1011274-highlight-systemdtmpfiles.html?sid=368b5c397e299849905cd5951960a874


 # systemctl status systemd-tmpfiles-setup
● 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-03-14 17:55:41 CET; 2min 1s ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 1838 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
 Main PID: 1838 (code=exited, status=1/FAILURE)


Reproducible: Always




Portage 2.2.18 (python 3.4.3-final-0, default/linux/amd64/13.0/no-emul-linux-x86/desktop, gcc-4.9.2, glibc-2.20-r2, 3.19.1-gentoo x86_64)
=================================================================
System uname: Linux-3.19.1-gentoo-x86_64-Intel-R-_Core-TM-_i7-3740QM_CPU_@_2.70GHz-with-gentoo-2.2
KiB Mem:    24626200 total,  22516784 free
KiB Swap:   25461756 total,  25461756 free
Timestamp of repository gentoo: Sat, 14 Mar 2015 16:30:01 +0000
sh bash 4.3_p33-r2
ld GNU ld (Gentoo 2.25 p1.0) 2.25
app-shells/bash:          4.3_p33-r2::gentoo
dev-java/java-config:     2.2.0::gentoo
dev-lang/perl:            5.20.2::gentoo
dev-lang/python:          2.7.9-r2::gentoo, 3.4.3::gentoo
dev-util/cmake:           3.1.0::gentoo
dev-util/pkgconfig:       0.28-r2::gentoo
sys-apps/baselayout:      2.2::gentoo
sys-apps/openrc:          0.13.11::gentoo
sys-apps/sandbox:         2.6-r1::gentoo
sys-devel/autoconf:       2.13::gentoo, 2.69::gentoo
sys-devel/automake:       1.11.6-r1::gentoo, 1.13.4::gentoo, 1.14.1::gentoo, 1.15::gentoo
sys-devel/binutils:       2.25::gentoo
sys-devel/gcc:            4.9.2::gentoo
sys-devel/gcc-config:     1.8::gentoo
sys-devel/libtool:        2.4.6::gentoo
sys-devel/make:           4.1-r1::gentoo
sys-kernel/linux-headers: 3.19::gentoo (virtual/os-headers)
sys-libs/glibc:           2.20-r2::gentoo
Repositories:

gentoo
    location: /mnt/portage
    sync-type: rsync
    sync-uri: rsync://rsync.gentoo.org/gentoo-portage
    priority: -1000

lokal
    location: /mnt/portage/local/local-overlay
    masters: gentoo
    priority: 0

bitcoin
    location: /mnt/portage/local/layman/bitcoin
    masters: gentoo
    priority: 50

bumblebee
    location: /mnt/portage/local/layman/bumblebee
    masters: gentoo
    priority: 50

media-overlay
    location: /mnt/portage/local/layman/media-overlay
    masters: gentoo
    priority: 50

steam-overlay
    location: /mnt/portage/local/layman/steam-overlay
    masters: gentoo
    priority: 50

ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="*"
Comment 1 tman 2015-03-14 17:16:46 UTC
  │ Symbol: EXT4_FS_POSIX_ACL [=y]                                                                                                         │  
  │ Type  : boolean                                                                                                                        │  
  │ Prompt: Ext4 POSIX Access Control Lists                                                                                                │  
  │   Location:                                                                                                                            │  
  │     -> File systems                                                                                                                    │  
  │ (1)   -> The Extended 4 (ext4) filesystem (EXT4_FS [=y])                                                                               │  
  │   Defined at fs/ext4/Kconfig:42                                                                                                        │  
  │   Depends on: BLOCK [=y] && EXT4_FS [=y]                                                                                               │  
  │   Selects: FS_POSIX_ACL [=y]                                                                                                           │  
  │                                                                                                                                        │  
  │
Comment 2 tman 2015-03-14 18:47:44 UTC
[I] sys-apps/systemd
     Available versions:  215-r3(0/2) 216-r3(0/2) (~)216-r4(0/2) (~)218-r3(0/2) (~)219-r1(0/2) (~)219-r2(0/2) **9999(0/2) {acl apparmor audit cryptsetup curl doc elfutils +firmware-loader gcrypt gudev http idn importd introspection kdbus +kmod (+)lz4 lzma nat pam policykit python qrcode +seccomp selinux ssl sysv-utils terminal test vanilla xkb ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32" PYTHON_SINGLE_TARGET="python2_7 python3_3 python3_4" PYTHON_TARGETS="python2_7 python3_3 python3_4"}
     Installed versions:  219-r2(18:05:47 14.03.2015)(acl cryptsetup gudev introspection kmod lz4 lzma pam policykit python seccomp ssl -apparmor -audit -curl -doc -elfutils -gcrypt -http -idn -importd -kdbus -nat -qrcode -selinux -sysv-utils -terminal -test -vanilla -xkb ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32" PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4" PYTHON_TARGETS="python2_7 python3_4 -python3_3")
     Homepage:            http://www.freedesktop.org/wiki/Software/systemd
     Description:         System and service manager for Linux
Comment 3 tman 2015-03-14 20:10:24 UTC
 # systemctl status systemd-tmpfiles-setup
● 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-03-14 21:01:43 CET; 6min 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)

Mär 14 21:01:43 TuX systemd[1]: Starting Create Volatile Files and Directories...
Mär 14 21:01:43 TuX systemd-tmpfiles[1836]: Setting default 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,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:...
Mär 14 21:01:43 TuX systemd-tmpfiles[1836]: 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,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...
Mär 14 21:01:43 TuX systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Mär 14 21:01:43 TuX systemd[1]: Failed to start Create Volatile Files and Directories.
Mär 14 21:01:43 TuX systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Mär 14 21:01:43 TuX systemd[1]: systemd-tmpfiles-setup.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
Comment 4 Ulenrich 2015-03-15 01:43:11 UTC
If you want Access Control Lists set on your filesystem, das it have, eg:
---
# tune2fs -l /dev/sda4
...
Filesystem features:      has_journal ext_attr
---
extendended attributes enabled?
Comment 5 tman 2015-03-15 07:37:00 UTC
 # tune2fs -l /dev/sdb5
tune2fs 1.42.12 (29-Aug-2014)
Filesystem volume name:   <none>
Last mounted on:          /home
Filesystem UUID:          65ef9fe2-d39b-46af-8644-c1e5c4b41620
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              38404096
Block count:              153600000
Reserved block count:     7680000
Free blocks:              87833777
Free inodes:              38141361
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      987
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Sat Jul 12 20:18:35 2014
Last mount time:          Sun Mar 15 08:31:37 2015
Last write time:          Sun Mar 15 08:31:37 2015
Mount count:              618
Maximum mount count:      -1
Last checked:             Sat Oct 25 06:11:13 2014
Check interval:           0 (<none>)
Lifetime writes:          1098 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      c8e27e16-c4c3-4be9-8e9f-f61bfe85d01e
Journal backup:           inode blocks
Comment 6 tman 2015-03-16 12:55:00 UTC
why its not fixed in portage? 

following links show its fixed, but isnt
https://bugs.freedesktop.org/sho

https://bugs.freedesktop.org/show_bug.cgi?id=89202
Comment 7 Attila Tóth 2015-04-01 12:26:39 UTC
(In reply to tman from comment #6)
> why its not fixed in portage? 
> 
> following links show its fixed, but isnt
> https://bugs.freedesktop.org/sho
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=89202

I see you've set the bug OBSOLETE. However I've synced yesterday and this bug is still in portage. I'm serious although it's April's 1st...
Comment 8 tman 2015-04-01 17:41:03 UTC
well i have no clue why but after unmerging systemd and delete the old sources and remerging it works for me.
Comment 9 Randy Tupas 2015-09-26 05:28:35 UTC
Request reopen this bug. I have confirmed I have:
1. CONFIG_EXT4_FS_POSIX_ACL=y set in my kernel config
2. My root mount has "has_journal ext_attr" set

Receiving these errors 

systemd-tmpfiles-clean.service     loaded failed failed Cleanup of Temporary Directories

systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device Nodes in /dev

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

More details:
tux ~ # systemctl status systemd-tmpfiles-clean.service
● systemd-tmpfiles-clean.service - Cleanup of Temporary Directories
   Loaded: loaded (/usr/lib64/systemd/system/systemd-tmpfiles-clean.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2015-09-25 21:54:41 PDT; 32min ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 9508 ExecStart=/usr/bin/systemd-tmpfiles --clean (code=exited, status=1/FAILURE)
 Main PID: 9508 (code=exited, status=1/FAILURE)

Sep 25 21:54:41 tux systemd-tmpfiles[9508]: [/usr/lib64/tmpfiles.d/tmp.conf:11] Unknown command type 'v'.
Sep 25 21:54:41 tux systemd-tmpfiles[9508]: [/usr/lib64/tmpfiles.d/tmp.conf:12] Unknown command type 'v'.
Sep 25 21:54:41 tux systemd[1]: systemd-tmpfiles-clean.service: main process exited, code=exited, status=1/FAILURE
Sep 25 21:54:41 tux systemd[1]: Failed to start Cleanup of Temporary Directories.
Sep 25 21:54:41 tux systemd[1]: Unit systemd-tmpfiles-clean.service entered failed state.
Sep 25 21:54:41 tux systemd[1]: systemd-tmpfiles-clean.service failed.
Comment 10 Attila Tóth 2015-09-27 06:41:35 UTC
(In reply to Randy Tupas from comment #9)
> Request reopen this bug. I have confirmed I have:
> 1. CONFIG_EXT4_FS_POSIX_ACL=y set in my kernel config
> 2. My root mount has "has_journal ext_attr" set
> 
> Receiving these errors 
> 
> systemd-tmpfiles-clean.service     loaded failed failed Cleanup of Temporary
> Directories
> 
> systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device
> Nodes in /dev
> 
> systemd-tmpfiles-setup.service     loaded failed failed Create Volatile
> Files and Directories
> 
> More details:
> tux ~ # systemctl status systemd-tmpfiles-clean.service
> ● systemd-tmpfiles-clean.service - Cleanup of Temporary Directories
>    Loaded: loaded (/usr/lib64/systemd/system/systemd-tmpfiles-clean.service;
> static; vendor preset: enabled)
>    Active: failed (Result: exit-code) since Fri 2015-09-25 21:54:41 PDT;
> 32min ago
>      Docs: man:tmpfiles.d(5)
>            man:systemd-tmpfiles(8)
>   Process: 9508 ExecStart=/usr/bin/systemd-tmpfiles --clean (code=exited,
> status=1/FAILURE)
>  Main PID: 9508 (code=exited, status=1/FAILURE)
> 
> Sep 25 21:54:41 tux systemd-tmpfiles[9508]:
> [/usr/lib64/tmpfiles.d/tmp.conf:11] Unknown command type 'v'.
> Sep 25 21:54:41 tux systemd-tmpfiles[9508]:
> [/usr/lib64/tmpfiles.d/tmp.conf:12] Unknown command type 'v'.
> Sep 25 21:54:41 tux systemd[1]: systemd-tmpfiles-clean.service: main process
> exited, code=exited, status=1/FAILURE
> Sep 25 21:54:41 tux systemd[1]: Failed to start Cleanup of Temporary
> Directories.
> Sep 25 21:54:41 tux systemd[1]: Unit systemd-tmpfiles-clean.service entered
> failed state.
> Sep 25 21:54:41 tux systemd[1]: systemd-tmpfiles-clean.service failed.

This service currently works for me, I cannot confirm your symptom on my setup.