[SOLVED]systemd-tmpfiles-setup.service fails

Hi,
I have installed arch on an old laptop (dell inspiron 6000). I haven't used arch linux for last 2 years. It seems system management style has changed drastically.
Anyways, systemctl status systemd-tmpfiles-setup.service returns this;
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sal 2015-06-09 11:00:18 EEST; 38min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 228 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 228 (code=exited, status=1/FAILURE)
Haz 09 11:00:18 yasar-laptop systemd[1]: Starting Create Volatile Files and Directories...
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Haz 09 11:00:18 yasar-laptop systemd[1]: Failed to start Create Volatile Files and Directories.
Haz 09 11:00:18 yasar-laptop systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service failed.
Is this something that I should be concerned? I don't really know what this service supposed to do?
If I should be concerned, how to troubleshoot it? Keep in mind that this is a fresh arch install.
Last edited by yasar11732 (2015-06-09 16:31:04)

Thanks,
I have add acl option to fstab file, it works now. If anyone else has this problem, here is how my fstab file looks now;
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
UUID=936297ec-2bc3-45ef-bdb0-0a4ce7239204 / ext4 rw,relatime,data=ordered 0 1
UUID=d1fd9d31-99b5-45ba-97f4-a4c20b96e48b /var reiserfs rw,relatime,acl 0 2
UUID=6a9b3e39-8ea2-446f-9a71-79faab7cdafe /home xfs rw,relatime,attr2,inode64,noquota 0 2
# UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4
UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4 none swap defaults 0 0

Similar Messages

[SOLVED]Systemd Tmpfile Setup Service Fails

I'm not sure what version this began but I'm using systemd 185-1 and systemd-arch-units 20120606-4. Service just fails to start. Is this fixable?
└╼ $ systemctl status systemd-tmpfiles-setup.service
systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: failed (Result: exit-code) since Fri, 22 Jun 2012 04:22:15 -0400; 36s ago
Docs: man:tmpfiles.d(5)
Process: 931 ExecStart=/usr/bin/systemd-tmpfiles --create --remove (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-tmpfiles-setup.service
Last edited by Hspasta (2012-06-23 04:31:05)

swanson wrote:Check fstab and comment out the tmp there.
Did and didn't help.
WorMzy wrote:
Do you have any aur/custom-made packages that put *.conf files in /usr/lib/tmpfiles.d or /usr/local/lib/tmpfiles.d?
Does the system journal have any more information about the failure?
Hm...I have a lot of stuff in /usr/lib/tmpfiles.d/
└╼ $ ls /usr/lib/tmpfiles.d/
total 44K
-rw-r--r-- 1 root root 30 Jun 4 16:12 console.conf
-rw-r--r-- 1 root root 29 May 27 00:29 consolekit.conf
-rw-r--r-- 1 root root 74 Jun 6 19:02 initscripts.conf
-rw-r--r-- 1 root root 719 Jun 4 16:12 legacy.conf
-rw-r--r-- 1 root root 61 Jun 16 01:28 lvm2.conf
-rw-r--r-- 1 root root 24 Jun 1 00:04 mpd.conf
-rw-r--r-- 1 root root 27 Jun 9 03:29 nscd.conf
-rw-r--r-- 1 root root 30 Jun 9 01:41 openssh.conf
-rw-r--r-- 1 root root 729 Jun 4 16:12 systemd.conf
-rw-r--r-- 1 root root 449 Jun 4 16:12 tmp.conf
-rw-r--r-- 1 root root 622 Jun 4 16:12 x11.conf
I feel like something in my system is broken...

[SOLVED]systemd-tmpfiles-setup.service failure

Hi guys,
I just reinstalled arch with the following partitions:
[root@arch_vinnom vinnom]# gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.0
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): BD3CA679-FA08-4F60-9BAD-B845DE9FF7EB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625142414
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 BIOS
2 4096 52432895 25.0 GiB 8300 ROOT
3 52432896 53481471 512.0 MiB 8300 BOOT
4 53481472 74452991 10.0 GiB 8300 TMP
5 74452992 95424511 10.0 GiB 8300 VAR
6 95424512 602935295 242.0 GiB 8300 HOME
7 602935296 625142414 10.6 GiB 8200 SWAP
The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Temporary Directory
Documentation=man:hier(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/tmp
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
[Mount]
What=tmpfs
Where=/tmp
Type=tmpfs
Options=mode=1777,strictatime
Because of this, I'm always getting:
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Dom 2015-05-03 03:29:58 BRT; 27min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 278 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 278 (code=exited, status=1/FAILURE)
Then I tried to change '/tmp' to '/run/tmpfs', folder that I created for this, using tmpfs wiki as reference.
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Temporary Directory
Documentation=man:hier(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/run/tmpfs
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
[Mount]
What=tmpfs
Where=/run/tmpfs
Type=tmpfs
Options=mode=1777,strictatime,nodev,nosuid,size=1536M
But the error persists. What I'm missing?
Last edited by vinnom (2015-05-03 16:51:38)

ooo wrote:Couldn't you just mask the tmp.mount service? (as mentioned in the wiki page you linked)
Then your /tmp partition would be mounted according to your fstab
Raynman wrote:
The tmp.mount generated from your fstab should override the tmp.mount in /usr/lib/systemd/system. You say
The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
If that is true (could you show output of mount and your fstab?) that is worth investigating.
However, your original problem seems to be that systemd-tmpfiles-setup.service fails. If something is wrong with your mounts, that could be related, but it might very well be something else. Is there any more information in the journal to indicate why the service fails (maybe even mentioning a tmpfiles.d config file that is responsible)? Did you create any config files for tmpfiles.d yourself?
Sorry guys, I tried to be concise, but ended up that I didn't make myself clear.
My '/tmp' is mounting fine as it takes priority over systemd. In fact, what I wanted to say is that '/tmp' mounts fine, systemd tried to mount tmpfs at '/tmp' and fails and I want to point tmpfs to mount at '/run/tmpfs' which I created for this, but just editing '/usr/lib/systemd/system/tmp.mount' didn't solve.
As for journalctl, it repeats several times this message:
Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Mai 02 22:43:32 arch_vinnom systemd[1]: Failed to start Create Volatile Files and Directories.
Mai 02 22:43:32 arch_vinnom systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service failed.
foutrelis wrote:
Depending on how your '/var' file system is created/mounted, you might need to enable ACL on it:
https://wiki.archlinux.org/index.php/Sy … rt_at_boot
hmm
I created my /var during arch installation, with mkfs.reiserfs.
Using
tune2fs -l /dev/sdXY | grep "Default mount options:"
To check if acl was already enabled, I got:
[root@arch_vinnom vinnom]# tune2fs -l /dev/sda5 | grep "Default mount options:"
tune2fs: Bad magic number in super-block while trying to open /dev/sda5
Couldn't find valid filesystem superblock.
Then I searched a bit and noted that reiserfs isn't compatible with acl =/
Last edited by vinnom (2015-05-03 15:12:18)

Systemd-tmpfiles-setup.service failure

Good evening friends.
I recently made a fresh install of arch linux on my pc and since the first boot up i get this error:
systemd-tmpfiles-setup.service failure
Failded to start create volatile files and directories
When i used "systemctl status" command on it, it said something about unkwnon groups in usr/lib/... somewhere, i can't remember all of it, because after i rebooted and tried the same command, it only said that the process failed, without giving much on details.
What might be the problem here?
Last edited by NotaName (2014-09-14 17:42:37)

falconindy wrote:
Just a guess, but I think you might have some unknown groups in usr/lib/... somewhere.
You'll really need to try harder to get the logs. They're still in the journal.
Thanks for the answer.
Well, i'm still working on the log finding part, as i'm not sure where they are supposed to be. I checked the /var/log folder files, but it seems that they are not readable/binary maybe?
P.S. Is this something that i might ignore if i don't find a way to fix it?
Last edited by NotaName (2014-09-14 19:36:47)

[SOLVED]Systemd and Crashplan service failed.

Hello,
Crashplan service won't start.
systemctl status crashplan.service
crashplan.service - CrashPlan Backup Engine
Loaded: loaded (/usr/lib/systemd/system/crashplan.service; enabled)
Active: failed (Result: exit-code) since Wed, 17 Oct 2012 11:21:39 -0600; 1h 11min ago
Process: 922 ExecStop=/opt/crashplan/bin/CrashPlanEngine stop (code=exited, status=0/SUCCESS)
Process: 527 ExecStart=/opt/crashplan/bin/CrashPlanEngine start (code=exited, status=0/SUCCESS)
Main PID: 920 (code=exited, status=127)
CGroup: name=systemd:/system/crashplan.service
Oct 17 11:21:29 arch CrashPlanEngine[527]: Starting CrashPlan Engine ... Using standard startup
Oct 17 11:21:29 arch CrashPlanEngine[527]: OK
Oct 17 11:21:29 arch systemd[1]: Started CrashPlan Backup Engine.
Oct 17 11:21:29 arch CrashPlanEngine[922]: Stopping CrashPlan Engine ... /opt/crashplan/bin/CrashPlanEngine: line 144: kill: (920) - No such process
Oct 17 11:21:39 arch CrashPlanEngine[922]: OK
Please let me know what information can I provide to sort out this issue.
Thanks.
Last edited by donniezazen (2012-10-18 07:04:11)

/usr/lib/systemd/system/crashplan.service
[Unit]
Description=CrashPlan Backup Engine
After=network.target
[Service]
Type=forking
PIDFile=/opt/crashplan/CrashPlanEngine.pid
EnvironmentFile=/opt/crashplan/bin/run.conf
WorkingDirectory=/opt/crashplan
ExecStart=/opt/crashplan/bin/CrashPlanEngine start
ExecStop=/opt/crashplan/bin/CrashPlanEngine stop
[Install]
WantedBy=multi-user.target

Systemd and systemd-vconsole-setup.service (long time)

Hi,
today I switched to systemd. It's amazing.
I have problem. one of 'service' start very long. Can someone help my figurout how to reduce boot time for: systemd-vconsole-setup.service?
# systemd-analyze blame
4646ms systemd-vconsole-setup.service
927ms dev-hugepages.mount
924ms dev-mqueue.mount
907ms sys-kernel-debug.mount
889ms wicd.service
759ms systemd-udevd.service
705ms systemd-udev-trigger.service
459ms systemd-sysctl.service
306ms systemd-remount-fs.service
296ms ip6tables.service
233ms systemd-logind.service
226ms iptables.service
209ms console-kit-log-system-start.service
181ms var.mount
167ms console-kit-daemon.service
116ms systemd-tmpfiles-setup.service
115ms systemd-readahead-collect.service
99ms home.mount
93ms systemd-user-sessions.service
85ms systemd-readahead-replay.service
18ms boot.mount
4ms tmp.mount
4ms proc-sys-fs-binfmt_misc.mount
# systemd-analyze
Startup finished in 1583ms (kernel) + 2946ms (initramfs) + 12669ms (userspace) = 17200ms
My /etc/vconsole.conf doesn't exist (I don't need it). But nothing change if I create it with proper conent.
Any ideas?
Regards
Last edited by ajes (2012-08-27 20:00:30)

@teateawhy I tried your options (de and us) but both makes pretty the same results.
I tried also on my second machine (diffrent hardware, but VGA's in both case are from Intel (MSI Wind U100 and Toshiba Satellite PRO S500-150), but with the same list of packages, and the result are the same. So for me it is hardware independent.
Perhaps I am missing some packages?
Here is my list of 'pacman -Qet':
alsa-utils 1.0.25-3
aspell-pl 20111117-1
autoconf 2.69-1
automake 1.12.3-1
bash-completion 2.0-2
bootchart2-git 20120829-1
calibre 0.8.66-1
cdrdao 1.2.3-6
chromium 21.0.1180.81-2
clamav 0.97.5-2
cups-pdf 2.6.1-1
djview4 4.8-2
dnsutils 9.9.1.P2-1
dosfstools 3.0.12-1
dvd+rw-tools 7.1-4
fakeroot 1.18.4-1
firefox 15.0-1
flashplugin 11.2.202.238-1
fontconfig-infinality 1-20120615
git 1.7.12-1
gnu-netcat 0.7.1-4
google-talkplugin 3.5.1.0-2
gpicview 0.2.3-1
grub-bios 2.00-1
gstreamer0.10-bad-plugins 0.10.23-2
gstreamer0.10-ffmpeg 0.10.13-1
gstreamer0.10-ugly-plugins 0.10.19-2
hdparm 9.39-1
hunspell-pl 20111216-1
hyphen-pl 20060726-1
intel-ucode 20120606-1
iptables 1.4.15-1
iputils 20101006-4
k3b 2.0.2-6
kdegraphics-okular 4.9.0-1
keepass 2.19-1
ktorrent 4.2.1-1
less 444-3
libdvdcss 1.2.12-1
libreoffice-calc 3.5.6-1
libreoffice-extension-languagetool 1.8-2
libreoffice-impress 3.5.6-1
libreoffice-writer 3.5.6-1
libtool 2.4.2-6
lvm2 2.02.97-1
lxappearance-obconf 0.2.0-1
lxde-common 0.5.5-2
lxdm 0.4.1-14
lxinput 0.3.2-2
lxlauncher 0.2.2-1
lxpanel 0.5.10-1
lxrandr 0.1.2-2
lxsession-edit 0.2.0-2
lxshortcut 0.1.2-1
lxtask 0.1.4-3
lxterminal 0.1.11-2
make 3.82-4
man-db 2.6.2-1
man-pages 3.42-1
mc 4.8.4-1
modemmanager 0.5.2.0-4
mtr 0.82-1
mythes-pl 1.5-1
network-manager-applet 0.9.6.2-1
nmap 6.01-2
ntp 4.2.6.p5-11
obconf 2.0.3.git20100309-3
openssh 6.1p1-1
pacbuilder-svn 138-2
patch 2.6.1-3
pcmanfm 1.0-1
pkg-config 0.27.1-1
qnapi 0.1.6_rc2-1
rpmextract 1.0-5
skype 4.0.0.8-1
smartmontools 5.43-1
subtitleeditor 0.40.0-1
sudo 1.8.5.p3-1
systemd-sysvcompat 189-3
ttf-liberation 2.00.0-1
ttf-microsoft-tahoma 5.10-1
ttf-ms-fonts 2.0-9
ttf-ubuntu-font-family 0.80-3
unrar 4.2.4-1
unzip 6.0-6
usb_modeswitch 1.2.4-1
usbutils 006-1
vim 7.3.600-1
virtualbox-ext-oracle 4.1.20-1
vpnc 0.5.3.svn516-3
wget 1.14-1
which 2.20-5
wine 1.5.11-1
wireshark-gtk 1.8.2-1
wvdial 1.61-4
xdotool 2.20110530.1-1
xf86-input-synaptics 1.6.2-1
xf86-video-intel 2.20.5-1
xlockmore 5.40-1
xorg-utils 7.6-8
yaourt-git 20120829-1
zip 3.0-3
and my /etc/makeinitcpio.conf (if it will help):
# grep -v ^# /etc/mkinitcpio.conf
MODULES="ext4 i915 ahci sd_mod"
BINARIES=""
FILES=""
HOOKS="base udev lvm2 autodetect timestamp"
COMPRESSION="xz"
COMPRESSION_OPTIONS="-9"

Systemd-remount-fs.service fails [SOLVED]

After a fresh install on a brandnew laptop, my root partition is being mounted read only, and I see that systemd-remount-fs.service fails:
[root@anton ~]# systemctl status systemd-remount-fs.service
systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
Active: failed (Result: exit-code) since Sat, 2012-12-01 21:00:05 MST; 18min ago
Docs: man:systemd-remount-fs.service(8)
Process: 186 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-remount-fs.service
Dec 01 21:00:05 anton systemd-remount-fs[186]: mount: / not mounted or bad option
Dec 01 21:00:05 anton systemd-remount-fs[186]: In some cases useful info is found in syslog - try
Dec 01 21:00:05 anton systemd-remount-fs[186]: dmesg | tail or so
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I have no idea why this is happening, or what to do to try and fix it - any help/advice would be greatly appreciated. Following is the information I think is necessary for assistance:
Note that I have /usr on a separate partition, which I suspect is possibly involved in the issue somehow.
Here's my fstab:
[root@anton ~]# cat /etc/fstab
# /dev/sda5
#UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 defaults,rw,noatime,discard,data=writeback 0 1
# /dev/sda6
UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,noatime,discard,data=writeback 0 0
# /dev/sda7
UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
# /dev/sda8
UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
Here's the relevant output from mount (note that my root (sda5) partition is not being mount with the options I specified in fstab):
[root@anton ~]# mount | grep sda
/dev/sda5 on / type ext4 (ro,relatime,data=ordered)
/dev/sda6 on /usr type ext4 (rw,noatime,discard,data=writeback)
/dev/sda7 on /var type ext4 (rw,noatime,discard,data=ordered)
/dev/sda8 on /home type ext4 (rw,relatime,discard,data=ordered)
Relavant snippet from /boot/grub/grub.cfg:
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-a09ff37e-ce60-4173-b95a-4b71a53c01d3' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 a09ff37e-ce60-4173-b95a-4b71a53c01d3
else
search --no-floppy --fs-uuid --set=root a09ff37e-ce60-4173-b95a-4b71a53c01d3
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 ro init=/usr/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
Finally, here's my mkinitcpio.cfg:
[root@anton ~]# cat /etc/mkinitcpio.conf
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect sata filesystems usbinput usr fsck shutdown"
Last edited by corey_s (2012-12-02 08:57:35)

Thanks for the quick response, WonderWoofy ( by the way, great username! )!
When I removed or modified the the mount options in the bootloader kernel command line, there was no change to the status of the fs after boot-up. I had changed it at one point from 'ro', to 'rw'; but doing so had no affect on the output of the mount command.
However, I did finally identify the cause: turns out if I specify 'data=writeback', in fstab for the root partition, then systemd-remount-fs.service fails, as per my OP - leaving me with a 'ro'-mounted root filesystem. Simply removing that, or changing it to 'data=ordered', solved the issue: when I rebooted, the root partition was mounted as per my fstab config.
So, my fstab now looks like this:
# /dev/sda5
UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 rw,noatime,discard 0 1
# /dev/sda6
UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,ro,noatime,discard,data=writeback 0 0
# /dev/sda7
UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
# /dev/sda8
UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
... and all is now well.
I'll mark this as solved, but I'll also ask: why does specifying 'data=writeback' on my root partition cause the systemd-remount-fs.service to fail? Any experts out there know?
Last edited by corey_s (2012-12-02 06:46:32)

[SOLVED] systemd-tmpfiles-clean takes a very long time to run

I've been having an issue for a while with systemd-tmpfiles-clean.service taking a very long time to run. I've tried to just ignore it, but it's really bothering me now.
Measuring by running:
# time systemd-tmpfiles --clean
systemd-tmpfiles --clean 11.63s user 110.37s system 10% cpu 19:00.67 total
I don't seem to have anything funky in any tmpfiles.d:
# ls /usr/lib/tmpfiles.d/* /run/tmpfiles.d/* /etc/tmpfiles.d/* | pacman -Qo -
ls: cannot access /etc/tmpfiles.d/*: No such file or directory
error: No package owns /run/tmpfiles.d/kmod.conf
/usr/lib/tmpfiles.d/gvfsd-fuse-tmpfiles.conf is owned by gvfs 1.20.1-2
/usr/lib/tmpfiles.d/lastlog.conf is owned by shadow 4.1.5.1-9
/usr/lib/tmpfiles.d/legacy.conf is owned by systemd 212-3
/usr/lib/tmpfiles.d/libvirt.conf is owned by libvirt 1.2.4-1
/usr/lib/tmpfiles.d/lighttpd.conf is owned by lighttpd 1.4.35-1
/usr/lib/tmpfiles.d/lirc.conf is owned by lirc-utils 1:0.9.0-71
/usr/lib/tmpfiles.d/mkinitcpio.conf is owned by mkinitcpio 17-1
/usr/lib/tmpfiles.d/nscd.conf is owned by glibc 2.19-4
/usr/lib/tmpfiles.d/postgresql.conf is owned by postgresql 9.3.4-1
/usr/lib/tmpfiles.d/samba.conf is owned by samba 4.1.7-1
/usr/lib/tmpfiles.d/slapd.conf is owned by openldap 2.4.39-1
/usr/lib/tmpfiles.d/sudo.conf is owned by sudo 1.8.10.p2-1
/usr/lib/tmpfiles.d/svnserve.conf is owned by subversion 1.8.8-1
/usr/lib/tmpfiles.d/systemd.conf is owned by systemd 212-3
/usr/lib/tmpfiles.d/systemd-nologin.conf is owned by systemd 212-3
/usr/lib/tmpfiles.d/tmp.conf is owned by systemd 212-3
/usr/lib/tmpfiles.d/uuidd.conf is owned by util-linux 2.24.1-6
/usr/lib/tmpfiles.d/x11.conf is owned by systemd 212-3
How do I debug why it is taking so long? I've looked in man 8 systemd-tmpfiles and on google, hoping to find some sort of --dubug option, but there seems to be none.
Is it some how possible to get a list of the directories that it looks at when it runs?
Anyone have any suggestions on how else to fix this.
Anyone else have this issue?
Thanks,
Gary
Last edited by garyvdm (2014-05-08 18:57:43)

Thank you very much falconindy. SYSTEMD_LOG_LEVEL=debug helped my find my issue.
The cause of the problem was thousands of directories in /var/tmp/ created by a test suite with a broken clean up method. systemd-tmpfiles-clean was recursing through these, but not deleting them.

Slow systemd-vconsole-setup service at boot (apparently)

Hello,
I am trying to understand the timing of my boot sequence, particularly the systemd part. I have the feeling that systemd-vconsole-setup.service is taking quite a long time for what it is supposed to do, since I get
systemd-analyze blame | head
3.744s systemd-vconsole-setup.service
1.871s accounts-daemon.service
1.425s systemd-logind.service
1.357s alsa-restore.service
1.356s dhcpcd.service
1.256s polkit.service
983ms systemd-binfmt.service
952ms NetworkManager.service
832ms systemd-remount-fs.service
762ms gdm.service
I know that this time may not be a true indicator, so I have modify my systemd-vconsole-setup.service to prefix the command with a "strace" and redirect the output to a file (as indicated there), and here it seems that the process takes at least 1.5s (the output itself is a huge file). However, I could not follow the suggestion any further since we do not have the same output (presumably due to the fact that those are not the same distros).
Could anyone give me an advice to know a little bit more about this service and why it takes that time? Actually, it's more about knowing how the things work rather than optimizing at all cost my boot time.
Thanks!
Guillaume
Last edited by gdlr (2014-05-01 10:04:09)

Hello,
I am trying to understand the timing of my boot sequence, particularly the systemd part. I have the feeling that systemd-vconsole-setup.service is taking quite a long time for what it is supposed to do, since I get
systemd-analyze blame | head
3.744s systemd-vconsole-setup.service
1.871s accounts-daemon.service
1.425s systemd-logind.service
1.357s alsa-restore.service
1.356s dhcpcd.service
1.256s polkit.service
983ms systemd-binfmt.service
952ms NetworkManager.service
832ms systemd-remount-fs.service
762ms gdm.service
I know that this time may not be a true indicator, so I have modify my systemd-vconsole-setup.service to prefix the command with a "strace" and redirect the output to a file (as indicated there), and here it seems that the process takes at least 1.5s (the output itself is a huge file). However, I could not follow the suggestion any further since we do not have the same output (presumably due to the fact that those are not the same distros).
Could anyone give me an advice to know a little bit more about this service and why it takes that time? Actually, it's more about knowing how the things work rather than optimizing at all cost my boot time.
Thanks!
Guillaume
Last edited by gdlr (2014-05-01 10:04:09)

[Not solved]systemd-tmpfiles stat(/run/user/myuser/gvfs) failed: Perm

I get this error message since a couple of days and systemd-tmpfiles service is slow to start compared to before. I have no arch-units/initscripts anymore. I update everyday but I can see no updates that sticks out in pacman-log, on the day before this failure appeared. (systemd-tools was updated 3 days before this error)
Permissions;
/run/user
drwxr-xr-x 3 root root 60 7 jun 10.51 .
drwxr-xr-x 11 root root 340 7 jun 10.51 ..
drwx------ 3 myuser myuser 80 7 jun 10.51 myuser
/run/user/myuser
drwx------ 3 myuser myuser 80 7 jun 10.51 .
drwxr-xr-x 3 root root 60 7 jun 10.51 ..
dr-x------ 2 myuser myuser 0 7 jun 10.51 gvfs
lrwxrwxrwx 1 root root 17 7 jun 10.51 X11-display -> /tmp/.X11-unix/X0
/run/user/myuser/gvfs
dr-x------ 2 myuser myuser 0 7 jun 10.51 .
drwx------ 3 myuser myuser 80 7 jun 10.51 ..
EDIT: Now I've look at the files;
/usr/lib/tmpfiles.d
totalt 160K
drwxr-xr-x 2 root root 4,0K 2 jun 15.54 .
drwxr-xr-x 167 root root 128K 7 jun 07.34 ..
-rw-r--r-- 1 root root 30 1 jun 02.28 console.conf
-rw-r--r-- 1 root root 29 27 maj 06.29 consolekit.conf
-rw-r--r-- 1 root root 719 1 jun 02.28 legacy.conf
-rw-r--r-- 1 root root 729 1 jun 02.28 systemd.conf
-rw-r--r-- 1 root root 449 1 jun 02.28 tmp.conf
-rw-r--r-- 1 root root 622 1 jun 02.28 x11.conf
And the only thing possibly close is; d /run/user 0755 root root 10d
from systemd.conf.
Last edited by swanson (2012-06-08 07:20:28)

Nope, error still there and no clue what's happening. It occurs without me trying to mount anything, no usb's, no phones and no disks.

[SOLVED] systemd display-manager.service problem

Hi!
After the upgrade of systemd, i noticed today this error in dmesg:
systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
systemctl status display-manager.service
display-manager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
Any idea?
Thanks!
EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
Last edited by nierro (2012-07-15 17:13:42)

nierro wrote:
Hi!
After the upgrade of systemd, i noticed today this error in dmesg:
systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
systemctl status display-manager.service
display-manager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
Any idea?
Thanks!
EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
There has been a change regarding display managers. up until now they were WantedBy graphical.target, which was kind of stupid because this allowed you to enable multiple display managers.
Instead graphical.target now Wants display-manager.service and all display managers are supposed to install the appropriate Alias. Afaik all display manager service files have been updated ragarding this and a "systemctl reenable slim.service" should fix it.

[SOLVED] systemd and ntpd.service

I've just converted to pure systemd according to the wiki. Everything went remarkably well, with just a little blemish. While I'm not notified of any error at startup, when I check systemctl I find that ntpd.service's LOAD/ACTIVE/SUB is loaded/failed/failed.
systemctl status ntpd.service gives me this:
ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled)
Active: failed (Result: exit-code) since Thu, 18 Oct 2012 04:16:56 +0200; 6s ago
Process: 1397 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/SUCCESS)
Main PID: 1398 (code=exited, status=255)
CGroup: name=systemd:/system/ntpd.service
Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
and journalctl pretty much more of the same:
Oct 18 04:16:56 mike ntpd[1397]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
Oct 18 04:16:56 mike ntpd[1398]: proto: precision = 0.106 usec
Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 18 04:16:56 mike sudo[1394]: pam_unix(sudo:session): session closed for user root
Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
Oct 18 04:16:56 mike systemd[1]: ntpd.service: main process exited, code=exited, status=255
Oct 18 04:16:56 mike systemd[1]: Unit ntpd.service entered failed state.
Trying to use it manually (eg. ntpd -qg) works, so I'm not sure what's wrong with it exactly. Where else should I look?
Last edited by Mr_Mario (2012-12-06 11:29:57)

slickvguy wrote:I've just started converting to systemd and ran into the same issue. I believe the problem is that you are missing the ntp group from your group file. If you updated your system and merely renamed your group.pacnew to group, it no longer contains the ntp group that was previously added. I just added the ntp group again ( ntp:x:87: ), and ntp started properly and the status is correct. Hope this helps.
That was it. Thank you!

[SOLVED] systemd uses cronie.service in /usr/lib instead of /etc

I've been having a little problem getting systemd to use my custom service file for cronie. I've tried doing the same thing with ntpd and a few other services, and they all work fine.
[root@garrett garrett]# cp /{usr/lib,etc}/systemd/system/cronie.service
[root@garrett garrett]# systemctl reenable cronie.service
rm '/etc/systemd/system/multi-user.target.wants/cronie.service'
ln -s '/etc/systemd/system/cronie.service' '/etc/systemd/system/multi-user.target.wants/cronie.service'
[root@garrett garrett]# systemctl status cronie.service
cronie.service - Periodic Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/cronie.service; enabled)
Active: inactive (dead)
CGroup: name=systemd:/system/cronie.service
Sep 13 21:32:52 garrett /usr/sbin/crond[622]: (CRON) INFO (running with inotify support)
It appears to have something to do with the crond.service symlink to cronie.service, since when I remove it, systemd will use the service file in /etc.
[root@garrett garrett]# rm /usr/lib/systemd/system/crond.service
[root@garrett garrett]# cp /{usr/lib,etc}/systemd/system/cronie.service
[root@garrett garrett]# systemctl reenable cronie.service
rm '/etc/systemd/system/multi-user.target.wants/cronie.service'
ln -s '/etc/systemd/system/cronie.service' '/etc/systemd/system/multi-user.target.wants/cronie.service'
[root@garrett garrett]# systemctl status cronie.service
cronie.service - Periodic Command Scheduler
Loaded: loaded (/etc/systemd/system/cronie.service; enabled)
Active: inactive (dead)
CGroup: name=systemd:/system/cronie.service
Sep 13 21:32:52 garrett /usr/sbin/crond[622]: (CRON) INFO (running with inotify support)
However, these symlinks don't cause problems in other packages such as with cups.service, which has a symlink cupsd.service. I also tried the same commands above on another arch computer I have that is running systemd and encountered the same results. This just seems really strange, and I'm not exactly sure where to go from here. Any help would be greatly appreciated.
Last edited by Floft (2012-09-14 06:40:23)

I can not replicate on my system.
# find {/usr/lib,/etc}/systemd/system/ -name "*cron*" -ls
803795 4 -rw-r--r-- 1 root root 174 Aug 8 22:24 /usr/lib/systemd/system/cronie.service
803798 0 lrwxrwxrwx 1 root root 14 Aug 8 22:24 /usr/lib/systemd/system/crond.service -> cronie.service
793796 4 -rw-r--r-- 1 root root 174 Sep 14 03:01 /etc/systemd/system/cronie.service
932745 0 lrwxrwxrwx 1 root root 34 Sep 14 03:01 /etc/systemd/system/multi-user.target.wants/cronie.service -> /etc/systemd/system/cronie.service
# systemctl status cronie
cronie.service - Periodic Command Scheduler
Loaded: loaded (/etc/systemd/system/cronie.service; enabled)
Active: active (running) since Fri, 14 Sep 2012 03:06:05 -0300; 1s ago
Main PID: 13956 (crond)
CGroup: name=systemd:/system/cronie.service
└ 13956 /usr/sbin/crond -n

[SOLVED] systemd swap related service in failed state

Hi. When I ran systemctl to check my services, there was a failed one related to swap.
Output of systemctl --failed:
UNIT LOAD ACTIVE SUB DESCRIPTION
● dev-disk-by\x2duuid-7a53052d\x2df673\x2d40c9\x2d8b21\x2d1d5d87127479.swap loaded failed failed /dev/disk/by-uuid/7a53052d-f673-40c9-8b21-1d5d87127479
Output of systemctl status dev-disk-by\x2duuid-7a53052d\x2df673\x2d40c9\x2d8b21\x2d1d5d87127479.swap:
● dev-disk-byx2duuid-7a53052dx2df673x2d40c9x2d8b21x2d1d5d87127479.swap - /dev/disk/byx2duuid/7a53052dx2df673x2d40c9x2d8b21x2d1d5d87127479
Loaded: loaded
Active: inactive (dead)
What: /dev/disk/byx2duuid/7a53052dx2df673x2d40c9x2d8b21x2d1d5d87127479
However, in the systemctl output there was another service which was active:
dev-sda6.swap loaded active active Swap Partition
And this is basically the same partition. In the output of blkid:
/dev/sda6: UUID="7a53052d-f673-40c9-8b21-1d5d87127479" TYPE="swap" PARTUUID="00c618fd-9807-4fef-89dd-28e0a79192a9"
As you can see the UUID of /dev/sda6 matches the one of the failing service. Here is the /etc/fstab entry for this partition:
UUID=7a53052d-f673-40c9-8b21-1d5d87127479 none swap defaults 0 0
So there are two services related to this partition, one that is active and one that is failed. I don't understand why and I don't know how to fix this. Any explanations and help will be greatly appreciated!
Last edited by polomi (2015-02-27 20:19:32)

I commented the swap line in /etc/fstab, and now I don't have the failed service. I also still have the dev-sda6.swap service active. So it looks good?
However, when booting, I saw a line looking like this:
Expecting device 7a53052d\x2df673\x2d40c9\x2d8b21\x2d1d5d87127479
(It's maybe not exactly written like that, the boot is too fast for me to catch the text accurately.)
It seems like it's partly fixed in any case. Thanks.
Last edited by polomi (2015-02-27 20:26:56)

[SOLVED] RF Kill-related Service Fails

Hello, fellow Archers.
Not really sure what happened here... Last night I upgraded a bunch of packages, including systemd, and a couple of weird things happened this morning when I booted up. First of all, during boot my computer printed messages to the screen about what it was loading, even though I set the "quiet" kernel option. But it gets curiouser and curiouser (I was so startled I forgot my grammar), as one of the messages told me that it failed to load [email protected] I looked into it a bit, and it looks like I have three such service (rfkill0, rfkill1, and rfkill2). I have no idea what this all means. During the upgrade, I was told that changes were made in the naming scheme of network interfaces, but that I wouldn't be affected.
Here's some info, if it helps:
$ pacman -Q systemd
systemd 210-2
$ pacman -Q netctl
netctl 1.4-2
$ uname -r
3.13.5-1-ARCH
So far, this doesn't seem to have affected my ability to use my computer, but I'd like to know what's going on.
Last edited by mmmm_cake (2014-05-30 20:43:57)

OK, I think I have a solution for this annoyance, at least on my ASUS laptop. The problem seems to be that the asus_nb_wmi fails to be loaded sometimes, so the best is to force it to be loaded straight up from the initramfs.
First, make sure that asus_nb_wmi is loaded into your system:
# modprobe asus_nb_wmi
Check if the Wifi LED gets on. If it did, then all you need to do is to specify the asus_nb_wmi module to be included at the initramfs by including it into the MODULES line at /etc/mkinitcpio.conf:
MODULES="... asus_nb_wmi ..."
Finally, recreate initramfs:
# mkinitcpio -P
Reboot: the systemd warning should be gone now and the Wifi LED light should be working correctly.
Last edited by nvteighen (2014-05-30 19:40:35)

[SOLVED]systemd-tmpfiles-setup.service fails

Similar Messages

Maybe you are looking for