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

Similar Messages

(Solved) systemd-journald extremely high CPU usage

I started noticing this problem a few days ago, but I thought it was because I was running too much with too little RAM. But when running nothing more than a KDE desktop, my CPU usage bounces between 50% and 100%, making things laggy. It looks like systemd-journald is to blame, as it is using 50% of the CPU. This is an AMD Phenom II dual core, so this definitely shouldn't be happening. I noticed journal logs were more than 2 GB, so I deleted everything within /var/log/journal/. Rebooted, no change, so I disabled journal storage, but that did not solve the problem.
Nothing in the logs looks like a problem to me:
$ sudo journalctl
-- Logs begin at Tue 2013-03-12 17:31:37 PDT, end at Tue 2013-03-12 18:15:56 PDT. --
Mar 12 17:31:37 silverstone systemd-journal[149]: Allowing runtime journal files to grow to 298.6M.
Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpuset
Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpu
Mar 12 17:31:37 silverstone kernel: Linux version 3.7.10-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (G
Mar 12 17:31:37 silverstone kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=31669ea0-76db
Mar 12 17:31:37 silverstone kernel: e820: BIOS-provided physical RAM map:
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cff8ffff] usable
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff90000-0x00000000cff9dfff] ACPI data
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff9e000-0x00000000cffdffff] ACPI NVS
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cffe0000-0x00000000cfffffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001afffffff] usable
Mar 12 17:31:37 silverstone kernel: NX (Execute Disable) protection: active
Mar 12 17:31:37 silverstone kernel: SMBIOS 2.5 present.
Mar 12 17:31:37 silverstone kernel: DMI: MSI MS-7642/890GXM-G65 (MS-7642) , BIOS V1.2 03/31/2010
Mar 12 17:31:37 silverstone kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
Mar 12 17:31:37 silverstone kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 12 17:31:37 silverstone kernel: No AGP bridge found
Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0x1b0000 max_arch_pfn = 0x400000000
Mar 12 17:31:37 silverstone kernel: MTRR default type: uncachable
Mar 12 17:31:37 silverstone kernel: MTRR fixed ranges enabled:
Mar 12 17:31:37 silverstone kernel: 00000-9FFFF write-back
Mar 12 17:31:37 silverstone kernel: A0000-EFFFF uncachable
Mar 12 17:31:37 silverstone kernel: F0000-FFFFF write-protect
Mar 12 17:31:37 silverstone kernel: MTRR variable ranges enabled:
Mar 12 17:31:37 silverstone kernel: 0 base 000000000000 mask FFFF80000000 write-back
Mar 12 17:31:37 silverstone kernel: 1 base 000080000000 mask FFFFC0000000 write-back
Mar 12 17:31:37 silverstone kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
Mar 12 17:31:37 silverstone kernel: 3 disabled
Mar 12 17:31:37 silverstone kernel: 4 disabled
Mar 12 17:31:37 silverstone kernel: 5 disabled
Mar 12 17:31:37 silverstone kernel: 6 disabled
Mar 12 17:31:37 silverstone kernel: 7 disabled
Mar 12 17:31:37 silverstone kernel: TOM2: 00000001b0000000 aka 6912M
Mar 12 17:31:37 silverstone kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Mar 12 17:31:37 silverstone kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0xcff90 max_arch_pfn = 0x400000000
Mar 12 17:31:37 silverstone kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff880
Mar 12 17:31:37 silverstone kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
Mar 12 17:31:37 silverstone kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
$ systemctl status systemd-journald
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Tue 2013-03-12 18:10:41 PDT; 8min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 142 (systemd-journal)
Status: "Processing requests..."
CGroup: name=systemd:/system/systemd-journald.service
`-142 /usr/lib/systemd/systemd-journald
However, it looks like the log files keep getting corrupted:
$ sudo journalctl --verify
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000007f543-0004d7c4445effa4.journal
Invalid object contents at 124687944ââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal:124687944 (of 134074368, 92%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal (Bad message)
Invalid object contents at 75715936âââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal:75715936 (of 76156928, 99%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal (Bad message)
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000290d6-0004d7c3a0033472.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000000001-0004d7c413227650.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000fcfc0-0004d7c3fd8ee9c5.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
Invalid object contents at 124701856ââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal:124701856 (of 134049792, 93%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal (Bad message)
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-00000000000a9da8-0004d7c45187e39e.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000d26b1-0004d7c3ea1b73f7.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000002a43f-0004d7c425785944.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000539fb-0004d7c3b2d1f935.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000054d23-0004d7c4354da4ef.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@2c1af599e637441985385fe37ded2a2c-0000000000001706-0004d7c38cd3de88.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@5e6edd359123491f9998a310206ccbf9-00000000000019b4-0004d7c4153f8628.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-000000000007e345-0004d7c3c3ed8197.journal
I am using a two or three year old SSD, so maybe it has gotten some bad sectors? But that doesn't explain why journald still bricks things when it isn't logging anything. The install is 10 months old, and I switched from init to systemd around October. Is there anything I can do, short of reinstalling?
Thanks,
Nicholas
Last edited by bicyclingrevolution (2013-03-14 05:57:13)

Thanks for the tip ilkyest, but it didn't make any difference to the systemd-journald problem.
However, I looked at journalctl again and found it cluttered with CUPS failures:
-- Logs begin at Tue 2013-03-12 19:17:00 PDT, end at Wed 2013-03-13 22:31:31 PDT. --
Mar 12 19:17:00 silverstone spideroak_inotify[796]: Program started
Mar 12 19:21:30 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 7199 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5471 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5699 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-coredump[1592]: Process 1590 (cupsd) dumped core.
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-RGB..
Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_3840
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-RGB..
Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_F4100
Mar 12 19:21:28 silverstone dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mar 12 19:21:28 silverstone dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs
Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-RGB..
Mar 12 19:21:28 silverstone colord[354]: device removed: cups-Deskjet_3840
Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-Gray..
Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-RGB..
Mar 12 19:21:31 silverstone colord[354]: device removed: cups-Deskjet_F4100
Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or director
Mar 12 19:21:31 silverstone systemd-journal[143]: Missed 6365 kernel messages
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone cupsd[1590]: Unknown directive DefaultAuthType on line 9.
Mar 12 19:21:31 silverstone cupsd[1590]: cupsd: client.c:757: avahi_client_get_host_name: Assertion `client' failed.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone cupsd[1594]: Unknown directive DefaultAuthType on line 9.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Disabling cups solved the CPU usage issue.
It looks like the root of the problem is Avahi failing to start, but I have no idea why it isn't working.
$ systemctl status dbus-org.freedesktop.Avahi.service
dbus-org.freedesktop.Avahi.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)

[Solved] systemd-journald periodically uses 50% CPU

Hello!
I run KDE 4.11 on Arch fully upgraded. Since shortly my system seems to choke periodically at the systemd-journald process. It takes 50% of the CPU power available and everything else is starting to studder and freeze. using jounalctl only shows normal log entries and not (like suggested somewhere else) a huge amount of error entries within seconds.
I have tried to remedy this:
- I disabled cups as mentioned somewhere else
- I deleted all configuration files concerning alsa and pulseaudio (cause I found errors with journalctl) and reinstalled both
- I set /var/log/journal to "copy on write" because it is on a btrfs partition (another suggestion in a thread)
- I tried to somehow to disable systemd-journald (seems this is not possible)
Nothing seems to solve the problem - still my the systemd-journald process peaks to 50% CPU every few minutes and stays at this ressource eating level for a few minutes. Then it drops down to normal again using only minimal ressources for a few minutes ...
I am lost here. My system is really quite unusable though it is a fresh install from only two weeks ago. I only noticed this behaviour three days ago - afterwards I upgraded to kernel 3.10.9 but this hasn't changed anything either.
Any ideas anyone?
thx for reading,
piedro
Last edited by piedro (2015-02-08 18:24:45)

Hi jrusell!
Well I think I could solve it ... here is what I did:
- I deleted /var/log/journal
- rebooted and looked at the fresh log via journalctl: now it generated fresh entries again and there it was: (like in similar problems) the log has been flushed with hundreds fo fail messages! ... something like a "user burst limit exceeded" for rtkit and I found a problem with nepomukindexer (should have guessed it's KDE again - after the update to 4.11)
- so I stopped all nepomuk stuff and deleted ~/.kde4/share/apps/nepomuk, then let nepomuk trun again recreating the whole indexing database in the process (to be honest it's still in the process but ressources aren't used excessively)
Since then there hasn't been any problem with the journald process yet ... :-)
thx everybody for reading,
p.
Last edited by piedro (2013-08-26 14:11:32)

[SOLVED] systemd-journald errors

I set up a MythTV box the other day based on Arch (basically Arch+Openbox+Mythtv) and I get strange errors on shut down. It goes by extremely fast, but what I'm able to catch is:
systemd-journald failed to write entry 25 items
And some other stuff.
I'm not sure if it's related but in dmesg I see:
File /var/log/journal/eaa2513b7edf4267912b45e38d85d0e1/user-1000.journal corrupted or uncleanly shut down, renaming and replacing
I've deleted the entire /var/log/journal/eaa2513b7edf4267912b45e38d85d0e1 folder so it would be regenerated, but it didn't help.
Also, I've Googled this issue and found a bunch of topics with symptoms that match mine, but none of them have any solutions.
Last edited by jlacroix (2014-02-02 05:15:28)

WonderWoofy wrote:
I don't know, that is why I posed the possibility of sending an upstream report as a question...
Have you tried XBMC? I use that and it is pretty great (of course I have no other point of comparison). It also appears to have infrared remote control support (lirc) and also has android remote control application that works quite well (and some nice unofficial ones as well).
No, I've not had a reason to try XBMC because MythTV has worked so well for me. I'm not sure what XBMC's capabilities are, but in Myth TV I was able to create custom menus using XML for my games, which is very helpful (I prefer to do this by hand, so I avoid the mythgame plugin). This HTPC is working _extremely_ well, I'm just trying to eliminate errors so I can take a clean image of it in case it needs to be restored down the road. I noticed another error regarding cgroup stating "option or name mismatch" on shut down which from what I'm reading appears to be harmless but I'm still investigating this one.

[SOLVED] Systemd and tmpfiles? Conflicting /tmp?

I've got this error in journal;
systemd-tmpfile[247]: Two or more conflicting lines for /tmp configured, ignoring.
This is from a leftover from arch initscripts, /usr/lib/tmpfiles.d/arch.conf shich is doubled by systemd's, /usr/lib/tmpfiles.d/x11.conf (almost).
arch.conf;
D /tmp 1777 root root 10d
d /run/daemons 0755 root root -
d /tmp/.X11-unix 1777 root root 10d
d /tmp/.ICE-unix 1777 root root 10d
d /tmp/.XIM-unix 1777 root root 10d
d /tmp/.font-unix 1777 root root 10d
d /tmp/.Test-unix 1777 root root 10d
F /run/utmp 0664 root utmp -
r /tmp/.X[0-9]-lock
r /etc/nologin
r /etc/shutdownpid
r /forcefsck
r /fastboot
x11.conf;
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# See tmpfiles.d(5) for details
# Make sure these are created by default so that nobody else can
d /tmp/.X11-unix 1777 root root 10d
d /tmp/.ICE-unix 1777 root root 10d
d /tmp/.XIM-unix 1777 root root 10d
d /tmp/.font-unix 1777 root root 10d
d /tmp/.Test-unix 1777 root root 10d
# Unlink the X11 lock files
r /tmp/.X[0-9]*-lock
Can I delete the arch one - where is it started from at boot? I'm running only systemd and got rid of all arch units. Or can I merge them? I really can't tell which tmpfiles are needed.
Last edited by swanson (2012-05-31 19:11:46)

Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
if [ -s /etc/locale.conf ]; then
. /etc/locale.conf
fi
export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION

[SOLVED] systemd dhcpcd on boot failure

For the past month or so, my systemd service for dhcpcd has been failing to properly start on boot. However, I've noticed that this only occurs on a fresh start after a shutdown. It does not occur after a reboot.
I do not use any sort of connection manager such as: NetworkManager, netctl, connman, etc.. I am only using dhcpcd via systemd.
The command I've always used to create the service is:
# systemctl enable [email protected]
# systemctl start [email protected]
I've found some topics related to the issue from 2-3 years back, but they don't seem to be the exact same case from what I can tell.
Here is the output of systemctl --type=service --all: http://i.imgur.com/hqBZBoP.png
Here is the output of ip link show when the service is running:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff
Does anything seem off in my service list? This issue is really nagging at me, and I don't know enough about systemd or networking to isolate it.
Last edited by BlueYoshi (2015-05-17 22:50:51)

jasonwryan wrote:
What is in the journal after it fails to start?
Not a Sysadmin issue, moving to NC...
Just checked, and it looks like it's starting services in a strange order. "PIA" is my service to start my VPN using the https://aur.archlinux.org/packages/priv … access-vpn package. I would think dhcpcd should be starting first?
journalctl: https://bpaste.net/raw/28fe88297a78
pia.service (if relevant):
[Unit]
Description=PIA
[Service]
Type=simple
ExecStart=/usr/bin/pia
Restart=always
[Install]
WantedBy=multi-user.target

[SOLVED] systemd 208 journald process CPU spike on LXC container start

Hi,
The problem is that whenever I start an LXC container, systemd-journald process goes on 100% CPU utilization and only stops when I stop the container.
Setup details:
% cat /var/lib/lxc/projects/config
lxc.network.type = veth
lxc.arch = x86_64
lxc.utsname = projects
lxc.network.link = virbr3
lxc.network.flags = up
lxc.network.ipv4 = 192.168.200.11
lxc.rootfs = /mnt/lxc/projects
lxc.pts = 1000
lxc.autodev = 1
lxc.cgroup.memory.limit_in_bytes = 256M
The rootfs indicated is on a logical volume, /dev/mapper/virtual-projects.
Details of journal when the spike happened:
-- Logs begin at Sun 2013-08-04 07:19:25 IST. --
Oct 05 09:03:30 core systemd[1]: Unit [email protected] entered failed state.
Oct 05 09:03:30 core kernel: virbr3: port 2(vethl7BeWT) entered disabled state
Oct 05 09:03:30 core kernel: device vethl7BeWT left promiscuous mode
Oct 05 09:03:30 core kernel: virbr3: port 2(vethl7BeWT) entered disabled state
Oct 05 09:03:31 core ntpd[813]: Deleting interface #13 vethl7BeWT, fe80::fcf2:f2ff:fea0:9473#123, interface stats: received=0, sent=0, dropped=0, active_time=11 secs
Oct 05 09:03:31 core ntpd[813]: peers refreshed
Oct 05 09:03:40 core dbus-daemon[533]: dbus[533]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Oct 05 09:03:40 core dbus[533]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Oct 05 09:03:40 core dbus[533]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Oct 05 09:03:40 core dbus-daemon[533]: dbus[533]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Oct 05 09:05:30 core systemd[1]: Starting Linux Container projects...
Oct 05 09:05:30 core systemd[1]: Started Linux Container projects.
Oct 05 09:05:30 core systemd-sysctl[4562]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/zz-sysctl.conf'.
Oct 05 09:05:30 core kernel: device vethmHU7wo entered promiscuous mode
Oct 05 09:05:30 core kernel: IPv6: ADDRCONF(NETDEV_UP): vethmHU7wo: link is not ready
Oct 05 09:05:30 core NetworkManager[521]: <warn> /sys/devices/virtual/net/vethSIUSbq: couldn't determine device driver; ignoring...
Oct 05 09:05:30 core systemd-sysctl[4564]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/zz-sysctl.conf'.
Oct 05 09:05:30 core kernel: virbr3: topology change detected, propagating
Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered forwarding state
Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered forwarding state
Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered disabled state
Oct 05 09:05:30 core NetworkManager[521]: <warn> /sys/devices/virtual/net/vethmHU7wo: couldn't determine device driver; ignoring...
Oct 05 09:05:30 core kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethmHU7wo: link becomes ready
Oct 05 09:05:30 core kernel: virbr3: topology change detected, propagating
Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered forwarding state
Oct 05 09:05:30 core kernel: virbr3: port 2(vethmHU7wo) entered forwarding state
Oct 05 09:05:30 core libvirtd[809]: nl_recv returned with error: No buffer space available
Oct 05 09:05:30 core upowerd[660]: (upowerd:660): UPower-Linux-WARNING **: treating add event as change event on /org/freedesktop/UPower/devices/line_power_AC0
Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event3 (Power Button)
Oct 05 09:05:30 core upowerd[660]: (upowerd:660): UPower-Linux-WARNING **: treating add event as change event on /org/freedesktop/UPower/devices/battery_BAT0
Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event5 (Video Bus)
Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event2 (Sleep Button)
Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event1 (Lid Switch)
Oct 05 09:05:30 core systemd-logind[516]: Watching system buttons on /dev/input/event4 (Video Bus)
Oct 05 09:05:30 core mtp-probe[4711]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2"
Oct 05 09:05:30 core mtp-probe[4712]: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4"
Oct 05 09:05:30 core mtp-probe[4711]: bus: 3, device: 4 was not an MTP device
Oct 05 09:05:30 core mtp-probe[4712]: bus: 3, device: 5 was not an MTP device
Oct 05 09:05:30 core systemd-udevd[4561]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/host6/scsi_host/host6/link_power_management_policy} for writing: No such file or directory
Oct 05 09:05:32 core ntpd[813]: Listen normally on 14 vethmHU7wo fe80::fcf0:74ff:fe68:aade UDP 123
Oct 05 09:05:32 core ntpd[813]: peers refreshed
Oct 05 09:05:32 core ntpd[813]: new interface(s) found: waking up resolver
Oct 05 09:05:40 core dbus-daemon[533]: dbus[533]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Oct 05 09:05:40 core dbus[533]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Oct 05 09:05:40 core dbus[533]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Oct 05 09:05:40 core dbus-daemon[533]: dbus[533]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Oct 05 09:06:15 core kernel: EXT4-fs (dm-10): re-mounted. Opts: commit=600
Oct 05 09:06:15 core kernel: EXT4-fs (dm-12): re-mounted. Opts: acl,commit=600
Oct 05 09:06:15 core kernel: EXT4-fs (dm-18): re-mounted. Opts: commit=600
Oct 05 09:06:15 core kernel: EXT4-fs (sda1): re-mounted. Opts: commit=600
Oct 05 09:06:16 core kernel: EXT4-fs (sda4): re-mounted. Opts: acl,commit=600
Oct 05 09:06:21 core kernel: EXT4-fs (dm-10): re-mounted. Opts: commit=0
Oct 05 09:06:21 core kernel: EXT4-fs (dm-12): re-mounted. Opts: acl,commit=0
Oct 05 09:06:21 core kernel: EXT4-fs (dm-18): re-mounted. Opts: commit=0
Oct 05 09:06:21 core kernel: EXT4-fs (sda1): re-mounted. Opts: commit=0
Oct 05 09:06:28 core kernel: EXT4-fs (dm-10): re-mounted. Opts: commit=600
Oct 05 09:06:28 core kernel: EXT4-fs (dm-12): re-mounted. Opts: acl,commit=600
Oct 05 09:06:28 core kernel: EXT4-fs (dm-18): re-mounted. Opts: commit=600
Oct 05 09:06:28 core kernel: EXT4-fs (sda1): re-mounted. Opts: commit=600
Oct 05 09:06:28 core kernel: EXT4-fs (sda4): re-mounted. Opts: acl,commit=600
Oct 05 09:06:31 core kernel: EXT4-fs (dm-10): re-mounted. Opts: commit=0
Oct 05 09:06:31 core kernel: EXT4-fs (dm-12): re-mounted. Opts: acl,commit=0
Oct 05 09:06:31 core kernel: EXT4-fs (dm-18): re-mounted. Opts: commit=0
Oct 05 09:06:31 core kernel: EXT4-fs (sda1): re-mounted. Opts: commit=0
Oct 05 09:06:38 core systemd[1]: Stopping Linux Container projects...
Oct 05 09:06:38 core systemd[1]: [email protected]: main process exited, code=exited, status=137/n/a
Oct 05 09:06:38 core systemd[1]: Stopped Linux Container projects.
Oct 05 09:06:38 core systemd[1]: Unit [email protected] entered failed state.
Oct 05 09:06:38 core kernel: virbr3: port 2(vethmHU7wo) entered disabled state
Oct 05 09:06:38 core kernel: device vethmHU7wo left promiscuous mode
Oct 05 09:06:38 core kernel: virbr3: port 2(vethmHU7wo) entered disabled state
Oct 05 09:06:39 core ntpd[813]: Deleting interface #14 vethmHU7wo, fe80::fcf0:74ff:fe68:aade#123, interface stats: received=0, sent=0, dropped=0, active_time=67 secs
Oct 05 09:06:39 core ntpd[813]: peers refreshed
Nothing really leaps out to me.
This only happens on Systemd-208. Rolling back to systemd-207 resolved the issue for now, but I can't help but wonder if I won't have this problem again on systemd-209 or whatever. Is there any additional configuration that I need to do in order to get LXC working properly with systemd 208+?
Also, I don't know if this is relevant, but I got some filesystem permissions warnings on upgrading (and later downgrading) systemd.
Last edited by railmaniac (2013-10-12 14:03:47)

Some journal entries from the guest
There's a bunch of these:
ct 12 18:52:24 projects systemd-udevd[30]: Failed to apply ACL on /dev/dri/card0: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[38]: Failed to apply ACL on /dev/snd/hwC0D3: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[42]: Failed to apply ACL on /dev/snd/pcmC0D0c: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[37]: Failed to apply ACL on /dev/snd/hwC0D0: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[44]: Failed to apply ACL on /dev/snd/pcmC0D3p: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[43]: Failed to apply ACL on /dev/snd/pcmC0D0p: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[31]: Failed to apply ACL on /dev/snd/controlC0: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[35]: inotify_add_watch(7, /dev/sda, 10) failed: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[36]: Failed to apply ACL on /dev/sr0: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[34]: Failed to apply ACL on /dev/sg1: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[28]: Error, opening device '/dev/input/event12': No such file or directory
Oct 12 18:52:24 projects systemd-udevd[32]: Failed to apply ACL on /dev/video0: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[25]: inotify_add_watch(7, /dev/sdb, 10) failed: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[33]: Failed to apply ACL on /dev/kvm: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[29]: inotify_add_watch(7, /dev/sda1, 10) failed: No such file or directory
Oct 12 18:52:24 projects systemd[1]: Listening on D-Bus System Message Bus Socket.
Oct 12 18:52:24 projects systemd-udevd[30]: inotify_add_watch(7, /dev/sda2, 10) failed: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[27]: Failed to apply ACL on /dev/snd/timer: No such file or directory
Oct 12 18:52:24 projects systemd[1]: Starting Sockets.
Oct 12 18:52:24 projects systemd-udevd[35]: inotify_add_watch(7, /dev/sda4, 10) failed: No such file or directory
Oct 12 18:52:24 projects systemd-udevd[31]: inotify_add_watch(7, /dev/sda3, 10) failed: No such file or directory
And there's a bunch of these, which seems relevant since the logind part was changed in 208:
Oct 12 18:52:24 projects systemd-logind[59]: New seat seat0.
Oct 12 18:52:24 projects systemd[1]: Startup finished in 487ms.
Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event3: No such file or directory
Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event5: No such file or directory
Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event4: No such file or directory
Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event1: No such file or directory
Oct 12 18:52:24 projects systemd-logind[59]: Failed to open event2: No such file or directory
Oct 12 18:52:26 projects systemd-journal[64]: Permanent journal is using 87.6M (max 30.0M, leaving 1.1G of free 4.4G, current limit 30.0M).
Oct 12 18:52:26 projects systemd-journal[64]: Journal started
Oct 12 18:52:26 projects systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
Oct 12 18:52:26 projects systemd[1]: Unit systemd-journald.service entered failed state.
Oct 12 18:52:26 projects systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Oct 12 18:52:26 projects systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Hmm, just noticed it says systemd-journald exited with FAILURE. This is probably pretty informative to someone.

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

[SOLVED] Some systemd processes (e.g. systemd-journald) can't start.

After a fresh install on a new laptop (dual boot with Windows 8.1 vie rEFInd) I notice some error messages whilst booting. systemd-journald fails to start, and I also see some errors relating to the creation of the volatile filesystem. It's hard for me to give a lot detail about this as without journaling as I'm not sure how to get the error messages.
I did see this from dmesg:
[ 128.638674] systemd[1]: Starting Stop Read-Ahead Data Collection...
[ 128.662550] systemd[1]: Started Stop Read-Ahead Data Collection.
[ 194.545294] systemd[1]: Starting Journal Socket (/dev/log).
[ 194.545391] systemd[1]: Listening on Journal Socket (/dev/log).
[ 194.545471] systemd[1]: Starting Journal Socket.
[ 194.545540] systemd[1]: Listening on Journal Socket.
[ 194.545613] systemd[1]: Starting Journal Service...
[ 194.546604] systemd[1]: Started Journal Service.
[ 194.549797] systemd-journald[711]: Failed to get machine id: No such file or directory
[ 194.553931] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 194.554205] systemd[1]: Stopping Journal Service...
[ 24.362121] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m
[ 24.364106] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /var/log/journal/%m
[ 24.404888] systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
[ 24.409499] systemd[1]: Failed to start Create Volatile Files and Directories.
[ 24.412303] systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
And if I check the status of journald through systemctl I get:
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: failed (Result: start-limit) since Wed 2014-08-27 10:37:50 UTC; 1h 2min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Process: 720 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=1/FAILURE)
Main PID: 720 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
I've tried reinstalling systemd, and adding systemd to HOOKS in mkinitcpio.conf, neither of these things seem to help. I also can't start the services manually.
If anybody can help it would be greatly appreciated, thanks!
Last edited by Tim Butters (2014-08-28 15:49:50)

Normally, as Loqs said, 'systemd-firstboot --setup-machine-id' should have been run when you first installed the systemd package.
You can verify if the '/etc/machine-id' file exists:
$ ls -l /etc/machine-id
-rw-r--r-- 1 root root 33 25 mars 2009 /etc/machine-id
If you don't find one, maybe use 'systemd-machine-id-setup' instead to create one.
But have you seen error messages during the Arch installation? Because that should not be necessary.
Edit: 'systemd-firstboot' is new in systemd 216, so should not be found in the live installation disk 2014.08.
Last edited by berbae (2014-08-28 15:44:52)

[SOLVED]systemd-analyze startup delay problem

Hello,
i have a problem that my systemd-analyze shows me "Bootup is not yet finished. Please try again later." when im up in my fully functional desktop, because it wants to wait 1min and 30 before it finishes the "boot"
systemd-analyze
Startup finished in 3.482s (kernel) + 1min 30.058s (userspace) = 1min 33.541s
the userspace always takes that amount of time. while it actually takes ~12 sec to load with all set up. working network and stuff like that.
systemd-analyze blame
1.426s dkms.service
215ms ModemManager.service
207ms NetworkManager.service
193ms systemd-fsck@dev-disk-by\x2duuid-c9582b14\x2de7f5\x2d4496\x2dbc09\x2d7be584a182f4.s
148ms systemd-fsck@dev-disk-by\x2duuid-37962c3c\x2dcb8c\x2d4bb4\x2da27a\x2d58e852dcb643.s
85ms systemd-logind.service
78ms mnt-stuff.mount
77ms upower.service
68ms systemd-tmpfiles-clean.service
54ms systemd-modules-load.service
52ms polkit.service
52ms systemd-udev-trigger.service
47ms systemd-binfmt.service
47ms kmod-static-nodes.service
44ms mnt-downloads.mount
44ms dev-hugepages.mount
44ms dev-mqueue.mount
44ms systemd-vconsole-setup.service
43ms systemd-sysctl.service
43ms sys-kernel-debug.mount
41ms udisks2.service
25ms [email protected]
24ms lm_sensors.service
15ms cpupower.service
14ms alsa-restore.service
10ms systemd-journal-flush.service
8ms systemd-remount-fs.service
6ms systemd-user-sessions.service
6ms systemd-tmpfiles-setup.service
5ms systemd-tmpfiles-setup-dev.service
5ms rtkit-daemon.service
4ms systemd-update-utmp.service
4ms sys-fs-fuse-connections.mount
3ms proc-sys-fs-binfmt_misc.mount
3ms tmp.mount
1ms sys-kernel-config.mount
1ms systemd-udevd.service
1ms systemd-random-seed.service
nothing weird here(i think)?
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 @1min 30.058s
└─multi-user.target @1min 30.058s
└─dkms.service @875ms +1.426s
└─basic.target @869ms
└─timers.target @627ms
└─systemd-tmpfiles-clean.timer @627ms
└─sysinit.target @626ms
└─sys-fs-fuse-connections.mount @8.291s +4ms
└─systemd-modules-load.service @61ms +54ms
└─systemd-journald.socket @58ms
└─-.mount @57ms
└─system.slice @101ms
└─-.slice @101ms
as you can see multi-user.target and graphical.target starting at 1.30 only... allthough i dont even understand why they start at that time..cause my graphical interface is long time up already as well as my user account.
here svg of systemd-analyze plot: https://dl.dropboxusercontent.com/u/28788188/boot.svg
if anybody has some idea what might cause this i would really appriciate the help.
its just seems a cosmetical issue though. since my actual boot is around 13 sec from grub to fully functional desktop.
Last edited by xpander (2013-09-27 14:45:30)

WonderWoofy wrote:
These kinds of delays can happen when a service is bound to a particular piece of hardware.
So as an example the [email protected] uses "BindsTo=sys-subsystem-net-devices-%i.device". So when you enable [email protected], the part between the '@' and '.service' is what it will use in place of the '%i' of the BindsTo parameter.
This was a common problem when there was the change from the old kernel namespace used for network devices to the persistent udev naming scheme. During installation (or any time one was in the live media), it would use dhcpcd@eth0, so it would make sense that enabling dhcpcd@eth0 would set you all up for a nice ethernet connection when you launch the system for the first time. But then the 80-net-slot-names.rules udev file would change the interface name, making the BindsTo parameter time out after a while, since it would not be named something like enp2s0.
See if there are any failed units in the output of systemctl. Of course you will have to do this after systemd claims to have "finished" booting.
thanks, will digg into that. i do have some renaming policy there.. cause i have eth0 shown in ifconfig for example
i remember i did something about it in the past, because i never got used with the new naming scheme.
anyway systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
fluidsynth.service loaded failed failed FluidSynth Daemon
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
and that fluidsynth is no issue. cause with this installed, it still does same. i have fluidynth uninstalled because my pulseadio doesnt work when that is enabled

Systemd and Tmpfiles : Fail to start because of opencryptoki

Hi,
I got an error message on boot saying that tmpfiles fails to start.
systemctl --failed
● 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
sudo systemctl status systemd-tmpfiles-setup
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: failed (Result: exit-code) since lun. 2014-04-07 11:06:29 CEST; 22min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 371 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 371 (code=exited, status=1/FAILURE)
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:39] Unknown modifier 'stdll'
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:40] Syntax error.
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:42] Unknown modifier 'slot'
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:43] Syntax error.
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:44] Unknown modifier 'stdll'
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:45] Unknown modifier 'confname'
avril 07 11:06:29 silence systemd-tmpfiles[371]: [/usr/lib/tmpfiles.d/opencryptoki.conf:46] Syntax error.
avril 07 11:06:29 silence systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
avril 07 11:06:29 silence systemd[1]: Failed to start Create Volatile Files and Directories.
avril 07 11:06:29 silence systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Inside /usr/lib/tmpfiles.d there is indeed a opencryptoki.conf that is a symobolic link like this :
lrwxrwxrwx 1 root root 35 4 avril 11:06 opencryptoki.conf -> /etc/opencryptoki/opencryptoki.conf
And finally here is the content of my opencryptoki.conf
version opencryptoki-3.0
# The following defaults are defined:
# hwversion = 0.0
# firmwareversion = 0.0
# description = Linux
# manufacturer = IBM
# The slot definitions below may be overriden and/or customized.
# For example:
# slot 0
# stdll = libpkcs11_cca.so
# description = "OCK CCA Token"
# manufacturer = "MyCompany Inc."
# hwversion = 2.32
# firmwareversion = 1.0
# See man(5) opencryptoki.conf for further information.
slot 0
stdll = libpkcs11_tpm.so
slot 1
stdll = libpkcs11_ica.so
slot 2
stdll = libpkcs11_cca.so
slot 3
stdll = libpkcs11_sw.so
slot 4
stdll = libpkcs11_ep11.so
confname = ep11tok.conf
There is no .pacnew in this folder, so I guess something broke opencryptoki. That doesn't seem to cause me troubles right now but right now I failed to start my httpd service because of a lack of disk space. I guess that is not a good thing.
Could someone help me ?

Agree with Raynman, it doesn't make sense for that link to be there. That file is supposed to get a different sort of config (see `man tmpfiles.d`). I would just try:
sudo rm /usr/lib/tmpfiles.d/opencryptoki.conf
It's not a 100% kosher solution, but it should fix the issue for now, and hopefully if the AUR package gets an update they will fix that problem.
But mostly I'm posting because I wanted to say thanks for sharing all of your troubleshooting steps! I had an unrelated problem with my tmpfiles, searching brought me here, and your steps helped me both confirm that I had a different issue and fix my own issue.

[SOLVED] systemd switch, problems with slim/bootup

My system will boot, giving me "OK" for everything it's doing. Then my system gives me a tty login prompt, but continues booting:
gestalt login: [ OK ] Starting Wicd.
[ OK ] Reached target multi-user.
[ OK ] Reached target graphical interface.
So if i just hit enter, it gives me another login prompt, then I can login, but X/fluxbox isn't started or anything.
My ~/.xinitrc:
exec startfluxbox
xset +fp /usr/share/fonts/local
xset fp rehash
systemctl list-units --type=target
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target masked active active graphical.target
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded active active Syslog
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
14 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Graphical target isn't masked, like I thought it would be after reading this
systemctl status slim.service gives me:
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: failed (Result: exit-code) since Mon, 2012-11-26
Process: 305 ExecStart=urs/bin/slim -nodaemon(code=exited, status =1/FAILURE)
CGroup: name=systemd:/system/slim.service
systemd-analyze blame gives (just going to ignore the times)
wicd.service
systemd-vconsole-setup.service
systemd-binfmt.service
systemd-logind.service
systemd-modules-load.service
dev-hugepages.mount
systemd-udev-trigger.service
dev-mqueue.mount
systemd-udevd.service
proc-sys-fs-binfmt_service.mount
console-kit-daemon.service
polkit.service
systemd-tmpfiles-setup.service
home.mount
systemd-sysctl.service
tmp.mount
systemd-user-sesssions.service
systemd-remount-fs.service
slim isn't even on this list.
systemctl --failed
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
slim.service loaded failed failed SLiM Simple Login Manager
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
4 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Hopefully this isn't too much information (or completely irrelevant) for what might be a far simpler problem, but I'm just not sure what's going on. It might be worth noting that I only bothered to start switching to systemd today when I had to reboot and slim wouldn't start/get me into my WM(!) This is interesting to me, since I read (somewhere) that as of slim's last version, it would only work with systemd and not consolekit... but when I try:
pacman -Qi slim
It tells me that the last time I last updated/installed slim was November 5 of this year. Any ideas?
EDIT:
Latest nVidia drivers weren't working with my 7xxx integrated GPU. Downgrade to 304xx drivers or use nouveau.
Last edited by brokengestalt (2012-11-28 17:41:50)

I tried starting X manually (typing in "startx" at the prompt, and I get the following errors:
modprobe: ERROR: could not insert 'nvidia': No such device
Fatal server error:
no screens found
(EE)
Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
It looks like I'm just having problems with my video card, but I have the proprietary nVidia drivers installed and X installed. The systemd wiki page mentions no changes that I would need to make to my xorg or nvidia configuration...

[SOLVED] systemd-journald & tmpfiles-setup Failures

Similar Messages

Maybe you are looking for