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)

Similar Messages

[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)

[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

[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...

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"

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)

[SOLVED] systemd-journald & tmpfiles-setup Failures

Hello,
I have a weird situation. After I've finished installing my system, I got errors with journald...
After logging as root I get the following errors:
systemd-journald[338]: Failed to get machine id: No such file or directory
systemd-journald[340]: Failed to get machine id: No such file or directory
systemd-journald[345]: Failed to get machine id: No such file or directory
systemd-journald[347]: Failed to get machine id: No such file or directory
systemd-journald[349]: Failed to get machine id: No such file or directory
systemd[1]: Failed to start Journal Service.
systemd[1]: Dependency failed for Trigger Flushing of Journal to Presistent Storage.
systemd[1]: Failed to start Journal Service
and after I typed
systemctl
to see what's more, I got errors at the following:
systemd-journal-flush.service loaded failed failed
systemd-journald.service loaded failed failed
systemd-tmpfiles-setup-dev.service loaded failed failed
systemd-tmpfiles-setup.service loaded failed failed
systemd-journald-dev-log.socket loaded failed failed
systemd-journald.socket loaded failed failed
and other problems related to the above like
Failed to start Cleanup of Temporary Directories.
Note that it is my first time I have problems with journald and tmpfiles-setup and I'm not sure what happened...
Any help would be very appreciated and thank you very much in advance.
Last edited by heyom (2014-08-30 09:24:24)

I just had the same problem while installing a new Arch system. I managed to fix it by running `systemd-machine-id-setup` as root (not sudo).
Also, before I did that, while installing a package I got an error message about dbus not finding a machine id, and that error message suggested running `dbus-uuidgen > /var/lib/dbus/machine-id` (again as root, not sudo). So, you may need to do that, too.

Systemd-update-utmp.services wastes 16.990s while booting.

Info:
uname -a
Linux arch-linux-desk 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64 GNU/Linux
lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 4
Model name: AMD Phenom(tm) II X4 965 Processor
Stepping: 3
CPU MHz: 3816.867
BogoMIPS: 7636.80
Virtualization: AMD-V
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
L3 cache: 6144K
NUMA node0 CPU(s): 0-3
journalctl -u system-update-utmp
-- Reboot --
Mar 01 19:00:28 arch-linux-desk systemd[1]: Merged into installed job systemd-update-utmp.service/start as 51
Mar 01 19:00:48 arch-linux-desk systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
Mar 01 19:00:48 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp reboot
Mar 01 19:00:48 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 532
Mar 01 19:00:48 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> start
Mar 01 19:00:48 arch-linux-desk systemd[532]: Executing: /usr/lib/systemd/systemd-update-utmp reboot
Mar 01 19:00:48 arch-linux-desk systemd[1]: Child 532 belongs to systemd-update-utmp.service
Mar 01 19:00:48 arch-linux-desk systemd[1]: systemd-update-utmp.service: main process exited, code=exited, status=0/SUCCESS
Mar 01 19:00:48 arch-linux-desk systemd[1]: systemd-update-utmp.service changed start -> exited
Mar 01 19:00:48 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/start finished, result=done
Mar 01 19:00:48 arch-linux-desk systemd[1]: Started Update UTMP about System Reboot/Shutdown.
Mar 01 19:29:41 arch-linux-desk systemd[1]: Installed new job systemd-update-utmp.service/stop as 2431
Mar 01 19:29:44 arch-linux-desk systemd[1]: Stopping Update UTMP about System Reboot/Shutdown...
Mar 01 19:29:44 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp shutdown
Mar 01 19:29:44 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 20268
Mar 01 19:29:44 arch-linux-desk systemd[1]: systemd-update-utmp.service changed exited -> stop
Mar 01 19:29:44 arch-linux-desk systemd[20268]: Executing: /usr/lib/systemd/systemd-update-utmp shutdown
Mar 01 19:29:45 arch-linux-desk systemd[1]: Child 20268 belongs to systemd-update-utmp.service
Mar 01 19:29:45 arch-linux-desk systemd[1]: systemd-update-utmp.service: control process exited, code=exited status=0
Mar 01 19:29:45 arch-linux-desk systemd[1]: systemd-update-utmp.service got final SIGCHLD for state stop
Mar 01 19:29:45 arch-linux-desk systemd[1]: systemd-update-utmp.service changed stop -> dead
Mar 01 19:29:45 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/stop finished, result=done
Mar 01 19:29:45 arch-linux-desk systemd[1]: Stopped Update UTMP about System Reboot/Shutdown.
-- Reboot --
Mar 01 19:31:00 arch-linux-desk systemd[1]: Merged into installed job systemd-update-utmp.service/start as 52
Mar 01 19:31:03 arch-linux-desk systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
Mar 01 19:31:03 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp reboot
Mar 01 19:31:03 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 550
Mar 01 19:31:03 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> start
Mar 01 19:31:03 arch-linux-desk systemd[550]: Executing: /usr/lib/systemd/systemd-update-utmp reboot
Mar 01 19:31:03 arch-linux-desk systemd[1]: Child 550 belongs to systemd-update-utmp.service
Mar 01 19:31:06 arch-linux-desk systemd[1]: systemd-update-utmp.service: main process exited, code=exited, status=0/SUCCESS
Mar 01 19:31:20 arch-linux-desk systemd[1]: systemd-update-utmp.service changed start -> exited
Mar 01 19:31:20 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/start finished, result=done
Mar 01 19:31:20 arch-linux-desk systemd[1]: Started Update UTMP about System Reboot/Shutdown.
Mar 01 19:36:32 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 01 21:54:04 arch-linux-desk systemd[1]: Installed new job systemd-update-utmp.service/stop as 1797
Mar 01 21:54:07 arch-linux-desk systemd[1]: Stopping Update UTMP about System Reboot/Shutdown...
Mar 01 21:54:07 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp shutdown
Mar 01 21:54:07 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 11234
Mar 01 21:54:07 arch-linux-desk systemd[1]: systemd-update-utmp.service changed exited -> stop
Mar 01 21:54:07 arch-linux-desk systemd[11234]: Executing: /usr/lib/systemd/systemd-update-utmp shutdown
Mar 01 21:54:07 arch-linux-desk systemd[1]: Child 11234 belongs to systemd-update-utmp.service
Mar 01 21:54:07 arch-linux-desk systemd[1]: systemd-update-utmp.service: control process exited, code=exited status=0
Mar 01 21:54:07 arch-linux-desk systemd[1]: systemd-update-utmp.service got final SIGCHLD for state stop
Mar 01 21:54:07 arch-linux-desk systemd[1]: systemd-update-utmp.service changed stop -> dead
Mar 01 21:54:07 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/stop finished, result=done
Mar 01 21:54:07 arch-linux-desk systemd[1]: Stopped Update UTMP about System Reboot/Shutdown.
-- Reboot --
Mar 02 16:06:04 arch-linux-desk systemd[1]: Merged into installed job systemd-update-utmp.service/start as 52
Mar 02 16:06:09 arch-linux-desk systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
Mar 02 16:06:09 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp reboot
Mar 02 16:06:09 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 526
Mar 02 16:06:09 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> start
Mar 02 16:06:09 arch-linux-desk systemd[526]: Executing: /usr/lib/systemd/systemd-update-utmp reboot
Mar 02 16:06:09 arch-linux-desk systemd[1]: Child 526 belongs to systemd-update-utmp.service
Mar 02 16:06:11 arch-linux-desk systemd[1]: systemd-update-utmp.service: main process exited, code=exited, status=0/SUCCESS
Mar 02 16:06:26 arch-linux-desk systemd[1]: systemd-update-utmp.service changed start -> exited
Mar 02 16:06:26 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/start finished, result=done
Mar 02 16:06:26 arch-linux-desk systemd[1]: Started Update UTMP about System Reboot/Shutdown.
Mar 02 16:33:59 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:11 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:24 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:37 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:46 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:58 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:35:02 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:51:11 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @43.083s
└─multi-user.target @43.082s
└─spamassassin.service @31.838s +11.243s
└─network.target @31.831s
└─NetworkManager.service @27.053s +4.774s
└─basic.target @26.943s
└─timers.target @26.934s
└─systemd-tmpfiles-clean.timer @26.934s
└─sysinit.target @26.870s
└─systemd-update-utmp.service @9.874s +16.990s
└─systemd-tmpfiles-setup.service @9.287s +577ms
└─local-fs.target @9.278s
└─tmp.mount @9.118s +155ms
└─local-fs-pre.target @1.972s
└─systemd-tmpfiles-setup-dev.service @1.567s +397ms
└─kmod-static-nodes.service @686ms +872ms
└─systemd-journald.socket @648ms
└─-.mount @647ms
└─system.slice @1.069s
└─-.slice @1.061s
Last edited by 814ckf0x (2014-03-02 18:03:00)

Okay. For reference, that step takes 0.055 seconds on my box.
ewaller$@$odin ~ 1002 %systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @24.443s
`-multi-user.target @24.443s
`-postfix.service @21.770s +2.672s
`-network.target @21.768s
`[email protected] @11.892s +9.876s
`-basic.target @11.062s
`-timers.target @11.059s
`-systemd-tmpfiles-clean.timer @11.059s
`-sysinit.target @11.059s
`-systemd-update-utmp.service @11.003s +55ms
`-systemd-tmpfiles-setup.service @10.904s +98ms
`-local-fs.target @10.903s
`-home.mount @10.750s +152ms
`-systemd-fsck@dev-disk-by\x2duuid-1e70da27\x2d41c7\x2d4
`-dev-disk-by\x2duuid-1e70da27\x2d41c7\x2d43fc\x2d963b
ewaller$@$odin ~ 1003 %
I think you should look through your journal for more information. You may want to pastebin it and post a link here.

Systemd-tmpfiles and gvfs - permission denied

systemd-tmpfiles[2346]: stat(/run/user/1000/gvfs) failed: Permission denied
Can anyone tell me why this is in my journalctl ? Sometimes many times, depending on the application I use,
other times, once or twice in a 5 hour uptime.

same here with systemd. From log file:
localhost systemd-tmpfiles[12898]: stat(/run/user/1000/gvfs) failed: Permission denied
[gabx@magnolia:1000]$ ls -al
dr-x------ 2 gabx users 0 Aug 31 21:32 gvfs
[gabx@magnolia:1000]$ chmod -R u+w gvfs
[gabx@magnolia:1000]$ ls -al
dr-x------ 2 gabx users 0 Aug 31 21:32 gvfs
As you can see, can't even change permission for user gabx to write the directory.
EDIT:
[gabx@magnolia:~]$ 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; enabled)
Active: active (exited) since Fri, 31 Aug 2012 21:32:00 +0200; 46min ago
Docs: man:tmpfiles.d(5)
Process: 353 ExecStart=/usr/bin/systemd-tmpfiles --create --remove (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/systemd-tmpfiles-setup.service
[gabx@magnolia:~]$ sudo 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; enabled)
Active: active (exited) since Fri, 31 Aug 2012 21:32:00 +0200; 47min ago
Docs: man:tmpfiles.d(5)
Process: 353 ExecStart=/usr/bin/systemd-tmpfiles --create --remove (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/systemd-tmpfiles-setup.service
Following the above status, it seems everything is OK, so I am not sure this permission denied is really an issue.
Last edited by gabx (2012-08-31 23:31:01)

[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.

[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.

Thousands of log entries for systemd-tmpfiles-clean.timer on boot

I'm running a 32 bit Arch install as a VMware ESXi 5.1 guest. Whenever the guest boots up, I get several thousand of the following entries in the system log:
Feb 18 12:49:01 squid systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
The most recent boot had almost 20,000 entries within 5 seconds:
$ sudo journalctl -b | grep systemd-tmpfiles-clean.timer | wc -l
19693
$ sudo journalctl -b | grep systemd-tmpfiles-clean.timer | sed -n '1p;$p'
Feb 18 12:49:01 squid systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
Feb 18 12:49:06 squid systemd[1]: systemd-tmpfiles-clean.timer: time change, recalculating next elapse.
I've pasted the entry into Google but have not come up with anything helpful.
I have disabled host-guest time sync:
$ vmware-toolbox-cmd timesync status
Disabled
There is a NTP daemon running that syncs time with a single windows server (which is also a guest on the same ESXi host).
As far as I'm aware there shouldn't be anything else playing with the time, but theres obviously something going on.
Can anyone please help me troubleshoot?

I've had the same problem and I don't know what's going wrong. But I have a workaround:
If you're booting into a graphical environment you can disable the vmtoolsd service
# systemctl disable vmtoolsd
and add the following line to your ~/.xinitrc:
vmware-user-suid-wrapper
The ~/.xinitrc will start the vmtoolsd service then.
This solved two problems for me:
1. No more messages like you posted in my log file.
2. The virtual machine shuts down promptly (see vmtoolsd not stopping)
Last edited by BertiBoeller (2013-03-14 13:40:21)

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)

Command on boot - systemd tmpfile

Hi.
I have a laptop with ATI/Intel hybrid graphics. I am never using the ATI graphics when in Linux, and i simply want to turn the ATI card off on boot for battery-life. I used to do this in Ubuntu, simply by putting the command:
echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
in /etc/rc.local
Now on Arch i have to go around making a tmpfile for systemd (by searching around it seems this is the "correct" way of doing this kind of stuff on boot), that will perform this action for me. However i find the syntax very difficult to understand, so if someone could help i would appreciate it. The tmpfile i have created so far (which ofcourse isnt working), is
/etc/tmpfiles.d/fix_graphics.conf
and contains the line
w /sys/kernel/debug/vgaswitcheroo/switch - - - - OFF
Could anyone give me a pointer to what could be wrong? And just for future reference: What would one do in order to run a general command or script (for doing stuff more complex than writing a line to a file etc.) as root on startup with systemd?
Thanks in Advance
Esben

Hi
According to the wiki you have to blacklist the radeon kernel module and then load it manually afterwards before executing the echo OFF >...
Also you've to enable debugfs in your fstab, all described in the wiki: https://wiki.archlinux.org/index.php/Hy … ons_So_Far
As for systemd I do this with a little script that is called by a custom service file, wiki: https://wiki.archlinux.org/index.php/Sy … vice_files
I've added some After=, Requires= and Before= "tags" to the service file to make sure it executes at a good time, (After/Requires=systemd-user-sessions.service, to not execute too early and cause a kernel panic and Before=xinit.service to start it before X is started)
Edit: Alternatively you could use acpi_call from AUR to switch off the DGP completely. However this requires some similar steps to execute on boot.
Last edited by rebootl (2012-12-19 14:20:10)

SCCM 2012 SP1 - Offline Servicing failure - Failed to find or access the update binaries to be applied on the image

Hi there
Trying to patch a new Windows 7 SP1 image within SCCM 2012 SP1, but it's failing.
I've searched for information on the failure messages I am seeing, but although there is a LOT of information online concerning Offline Servicing failures, I can't find anything on the errors I am seeing.
I've tried injecting a single update, five updates and ten updates, no difference, same messages.
We have McAfee Access Protection disabled, as we know Offline Servicing simply won't work if this is running.
In the console, in Schedule Update Status for the image I am trying to update, the following message is shown:
"Failed to find or access the update binaries to be applied on the image."
That sounds as if the process can't find the actual .cab file for any update I've tried to inject, but I don't know why it wouldn't be able to do that, we have Software Updates configured and the .cab files are on the same server.
When I looked at the OfflineServicingMgr.log file, I see the following entries:
Processing image at index 1        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:52:49        8272 (0x2050)
Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\PackageID\W7_Image.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\PackageID\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'        SMS_OFFLINE_SERVICING_MANAGER
14/06/2014 14:52:49        8272 (0x2050)
Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17514        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31
8272 (0x2050)
Failed to find properties of file 4        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31        8272 (0x2050)
UnMounting Image (Commit Changes = 0) ...        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31        8272 (0x2050)
Completed processing image package PackageID. Status = Failed        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
Updated history for image package PackageID in the database        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
Schedule processing failed        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
Processing completed for Schedule with ID 16777237        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMServer.domain SITE=Site_Code PID=8560 TID=8272 GMTDATE=Sat Jun 14 13:54:04.964 2014 ISTR0="16777237" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0        SMS_OFFLINE_SERVICING_MANAGER
14/06/2014 14:54:04        8272 (0x2050)
Schedule processing thread stopped        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:05        8272 (0x2050)
I'm not sure what file "Failed to find properties of file 4" is referring to, whether dism.exe, an update or the image itself, but immediately after this message appears the image is unmounted. After that this message shows:
"Completed processing image package PackageID. Status = Failed"
As I say, there's a lot of information available re Offline Servicing but I haven't found anything with these particular messages.
If anyone has encountered this before, I'd appreciate any information you have.
Regards,
John.

Hi,
I think file named 'NO_SMS_ON_DRIVE.SMS’ might be causing this issue. If this file is present in logical drives, then please give it a shot one more time after deleting this file from the logical drives.
Due to this file, it might be preventing 'smsexec' service to skip the drive when looking for content. So worth a try!
After deleting this file, you also need to restart 'smsexec' service to reflect the changes. You can also verify from below registry value & ensure that all of your logical drives (specially where SCCMContentLib directory resides) should be listed
over there
'HKLM\Software\Microsoft\SMS\DP\ContentLibUsableDrives'
Hope this will help!
Cheers | Navdeep Sidhu

Systemd-tmpfiles-setup.service failure

Similar Messages

Maybe you are looking for