[SOLVED] systemd display-manager.service problem

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

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

Similar Messages

[SOLVED] display-manager.service

How can I find out what is trying to load this service?
I see this in my dmesg and while I don't think it's a problem, I'm just trying to make my server as robust/bug/error free as possible.
[ 4.058436] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
Not an actual server, but an old quad core PC that has no onboard, and no video card. It's just a spare box used like a server.
Last edited by Naijeru (2012-09-18 14:54:33)

Naijeru, there is documentation for a purpose. In this case: https://wiki.archlinux.org/index.php/Sy … _boot_into
Please don't be a help vampire. And read our forum etiquette.

[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] K Display Manager won't start up at boot

EDIT: I'm retarded. I hadn't even checked to see xorg-server was installed. It wasn't.
Hi,
I just installed package group kde-meta for a full KDE installation including KDM, installed xf86-video-ati for video card drivers, and then ran:
systemctl enable kdm.service
systemctl disable getty@tty1
Now, when I start up, I just get the messages "Starting K Display Manager..." and "Started K Display Manager." but the X server doesn't start up at all. Those messages are left on the screen. Using 'systemctl start kdm.service' does nothing. Literally no output or anything.
What should I do? Also, I know there's not much information, but if you give me some commands I can get some logs. I just don't know where to look for them...
Thanks in advance.
Last edited by Archimaredes (2013-01-25 19:06:33)

I've just been experiencing a similar issue. The local Apple Store just replaced my logic board (was overheating without secondary cooling when processor was under a full load, and the fans weren't kicking) for a little more trivial problem. Now that I just got it back, it ran for about 5 minutes before it spontaneously shutdown. I started it back immediately after that, and it went for only another couple minutes before it gave up yet again. After that, it just plain old wouldn't boot. Tried to reset the PRAM...wouldn't even get that far. Tried to reset the PMU...saw no change.
Whenever I try to boot it, I can hear the fan on the left start up and the hard drive attempt to spin up. Shortly after, it makes a subtle chirp-like noise and promptly shuts off. Mind you, I'm getting no display or anything 'cept these noises. I'm trying to get it to the point that I can run the diagnostics program from the OS X disc, but I think I'm going to be lucky to even get that far.
I'm thinking twice before taking my MacBook Pro to get serviced for something that isn't work-impairing now!

[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

ADS Data Manager Service problem

Hello,
I am trying to create a pdf document using ADS. While deploying it I am getting an error as follows:
ERROR LOG****************************
Failed to create a Data Manager. Please ensure that the Document Services Data Manager service is running:com.adobe.FailedCreationException
ERROR LOG ****************************
However I have checked my WAS, Data Manager service is running properly.Is there any setting on WAS which I am missing out?
Please guide...
Thanks and Regards,
Yashodhan Mujumdar

I have same problem. Did you find any solution?

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

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

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

[SOLVED]systemd-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

[SOLVED] systemd and ntpd.service

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

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

[SOLVED]Systemd Tmpfile Setup Service Fails

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

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

[SOLVED]Systemd and Crashplan service failed.

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

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

[SOLVED] few right-management related problems in XFce4

I'm new to XFce (just installed it yesterday...] and while the DE itself is amazing, I have a few problems...
1. I cannot delete shortcuts from desktop as a normal user.
[SOLVED] 2. I cannot mount external storage media as a normal user [and yes I have udev set up to mount them and pmount installed]. - solution: add dbus-launch to .xinitrc, even if you have dbus in rc.conf...
Any ideas on how to fix these?
Thanks,
Last edited by MatejLach (2011-10-11 17:42:39)

Leonid.I wrote:
karol wrote:
MatejLach wrote:
Do you mean this?;
"dbus-launch should actually be called after ck-launch-session, otherwise there will be authorization problems when mounting disks as a regular user, see FS#25031. For a temporary workaround you can comment out the xinitrc.d script at the beginning of the file [...]?"
Yes.
Is the problem related to other hdd partitions or usb sticks?
dbus-launch will start automatically, if you have dbus in DAEMONS and "exec ck-launch-session startxfce4" in ~/.xinitrc. At least this works for me (no DM)...
I DO have 'dbus' in /etc/rc.conf, but it seems that I had to manually add dbus-launch to my user-specific .xinitrc file - not sure why...

[SOLVED] systemd: create a service file that loads a kernel module

Hi, I have a daemon that I want to convert to a service unit of systemd.
The daemon tests if a module is loaded, and if not, modprobes it.
I do not want to load that module at boot up, only if the service is launched.
Is there a "proper" way to add something like RequiredModule=xxx to a service unit?
Thanks!
Last edited by Wasser (2012-09-03 08:58:02)

Maybe simply run modprobe with ExecStartPre. The command succeeds even if the module was already loaded.

[SOLVED]Disable display manager during boot

i ve installed lightdm with xfce , but it is breaking . i ve made to start lightdm at the end of boot process . how to disable lightdm.service . i cannot login to the system .
Last edited by dineshswamy (2013-02-18 17:03:31)

i did systemd.unit=multi-user.target at the boot loader . https://wiki.archlinux.org/index.php/Systemd for more options

[SOLVED] systemd swap related service in failed state

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

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

[SOLVED] systemd display-manager.service problem

Similar Messages

Maybe you are looking for