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

Similar Messages

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

Unit cpupower.service entered failed state

I've installed linux-rt (3.10.18-rt14-1-rt) with the intention of setting it up for pro-audio work. My cpu is a Core2 Quad.
I'm trying to set the cpu frequency to performance on start up, but it fails.
I installed cpupower and edited /etc/default/cpupower:
# Define CPUs governor
# valid governors: ondemand, performance, powersave, conservative, userspace.
governor='performance'
# Limit frequency range
# Valid suffixes: Hz, kHz (default), MHz, GHz, THz
min_freq="2.00GHz"
max_freq="2.50Hz"
I ran systemctl enable cpupower.service
But after reboot I get:
[tony@hydra ~]$ systemctl status cpupower.service
cpupower.service - Apply cpupower configuration
Loaded: loaded (/usr/lib/systemd/system/cpupower.service; enabled)
Active: failed (Result: exit-code) since Tue 2013-11-12 07:13:15 PST; 42min ago
Process: 218 ExecStart=/usr/lib/systemd/scripts/cpupower (code=exited, status=1/FAILURE)
Main PID: 218 (code=exited, status=1/FAILURE)
CGroup: /system.slice/cpupower.service
Here's the output from sudo journalctl | grep cpupower:
Nov 11 19:03:45 hydra sudo[11586]: tony : TTY=pts/0 ; PWD=/home/tony ; USER=root ; COMMAND=/usr/bin/pacman -S cpupower
Nov 11 19:32:46 hydra sudo[1444]: tony : TTY=pts/0 ; PWD=/home/tony ; USER=root ; COMMAND=/usr/bin/cpupower info
Nov 11 19:43:06 hydra sudo[1469]: tony : TTY=pts/0 ; PWD=/home/tony ; USER=root ; COMMAND=/usr/bin/cpupower frequency-set -g performance
Nov 12 05:48:25 hydra dbus-daemon[219]: dbus[219]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=4953 comm="systemctl enable cpupower.service ") interface="org.freedesktop.systemd1.Manager" member="EnableUnitFiles" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Nov 12 05:48:25 hydra dbus[219]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=4953 comm="systemctl enable cpupower.service ") interface="org.freedesktop.systemd1.Manager" member="EnableUnitFiles" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Nov 12 05:48:45 hydra sudo[4993]: tony : TTY=pts/0 ; PWD=/home/tony ; USER=root ; COMMAND=/usr/bin/systemctl enable cpupower.service
Nov 12 05:50:44 hydra systemd[1]: Starting Apply cpupower configuration...
Nov 12 05:50:44 hydra systemd[1]: cpupower.service: main process exited, code=exited, status=1/FAILURE
Nov 12 05:50:44 hydra systemd[1]: Failed to start Apply cpupower configuration.
Nov 12 05:50:44 hydra systemd[1]: Unit cpupower.service entered failed state.
Nov 12 06:32:32 hydra sudo[8192]: tony : TTY=pts/0 ; PWD=/home/tony ; USER=root ; COMMAND=/usr/bin/cpupower frequency-set -g
Nov 12 06:32:42 hydra sudo[8245]: tony : TTY=pts/0 ; PWD=/home/tony ; USER=root ; COMMAND=/usr/bin/cpupower frequency-set -g performance
Nov 12 06:56:14 hydra systemd[1]: Starting Apply cpupower configuration...
Nov 12 06:56:14 hydra systemd[1]: cpupower.service: main process exited, code=exited, status=1/FAILURE
Nov 12 06:56:14 hydra systemd[1]: Failed to start Apply cpupower configuration.
Nov 12 06:56:14 hydra systemd[1]: Unit cpupower.service entered failed state.
Nov 12 07:13:15 hydra systemd[1]: Starting Apply cpupower configuration...
Nov 12 07:13:15 hydra systemd[1]: cpupower.service: main process exited, code=exited, status=1/FAILURE
Nov 12 07:13:15 hydra systemd[1]: Failed to start Apply cpupower configuration.
Nov 12 07:13:15 hydra systemd[1]: Unit cpupower.service entered failed state.
Nov 12 08:16:51 hydra systemd[1]: Starting Apply cpupower configuration...
Nov 12 08:16:51 hydra systemd[1]: cpupower.service: main process exited, code=exited, status=1/FAILURE
Nov 12 08:16:51 hydra systemd[1]: Failed to start Apply cpupower configuration.
Nov 12 08:16:51 hydra systemd[1]: Unit cpupower.service entered failed state.
But, I can set it manually:
[tony@hydra ~]$ sudo cpupower frequency-set -g performance
Setting cpu: 0
Setting cpu: 1
Setting cpu: 2
Setting cpu: 3
[tony@hydra ~]$ sudo cpupower frequency-info -p
analyzing CPU 0:
1998000 2500000 performance
Any ideas on where to go from here to get this working?

No.
# systemctl start cpupower.service
Job for cpupower.service failed. See 'systemctl status cpupower.service' and 'journalctl -xn' for details.
# journalctl -xn
-- Logs begin at Sat 2013-11-09 15:26:43 PST, end at Thu 2013-11-14 06:56:23 PST. --
Nov 14 06:56:19 hydra su[1010]: (to root) tony on pts/0
Nov 14 06:56:19 hydra su[1010]: pam_unix(su:session): session opened for user root by tony(uid=1000)
Nov 14 06:56:20 hydra slim[235]: starting deadbeef 0.5.6
Nov 14 06:56:20 hydra slim[235]: server_start
Nov 14 06:56:21 hydra slim[235]: starting deadbeef 0.5.6
Nov 14 06:56:21 hydra slim[235]: server_start
Nov 14 06:56:22 hydra slim[235]: starting deadbeef 0.5.6
Nov 14 06:56:22 hydra slim[235]: server_start
Nov 14 06:56:23 hydra slim[235]: starting deadbeef 0.5.6
Nov 14 06:56:23 hydra slim[235]: server_start
Last edited by hobonix (2013-11-14 15:00:58)

[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

Systemd socket launching service and failing

I'm creating an AUR package for poppassd (POP3 Password Changing Service). The application runs in command line using stdin/stdout but is intended to be run using xinetd and pipe the socket as I/O. The code works fine when I run via command line
$ sudo /usr/bin/poppassd
200 poppassd
QUIT
500 Username required
$
When I start the socket
systemctl start poppassd.socket
the socket opens and when I try to use telnet to connect I get a disconnect right away and journalctl reports the service exited with a status of 1/FAILURE
Any ideas why the following service and socket files are not working?
poppassd.service
[Unit]
Description=POP3 Password Change Service
[Service]
ExecStart=/usr/bin/poppassd
StandardInput=socket
StandardOutput=inherit
StandardError=journal
poppassd.socket
[Socket]
ListenStream=0.0.0.0:106
[Install]
WantedBy=sockets.target

Note: i've never used poppassd and have not tested what i am about to suggest.
Since poppassd is written to be invoked by inetd with the nowait flag, it probably wants to be started with an accepted socket, not a listening socket. To do this in systemd, first add the following to the [Socket] section of poppassd.socket:
Accept=true
Then change the name of poppassd.service to [email protected]
Some socket activated template services (ie. [email protected]) also prepend '-' to the ExecStart value to prevent a single failed instance from throwing the service into a failed state.

Systemd switchover - pyload.service always fails

I have finally moved my home server over to systemd (last night) and spent today enabling all relevant daemons and services and rebooting.
I'm now faced with a number of issues, including a slowdown of the system and SSH login (gone from 1-2 seconds login to ~15 seconds to login)
I will created separate threads for each issue / service.
pyload.service always fails to start
I have re-run the setup using pyLoadCore -s and everything goes smoothly, I am even able to access the web interface. However, when I exit out of terminal the service stops, so I try to load it using systemctl and it does the same as with my httpd.service issue - it begins, works for a few seconds/minute and then fails. During this small timeframe everything works fine before it fails.
It is beginning to look like there is some issue with systemctl not letting specific services to fully load, or something (I don't know lol)

kaipee wrote:Because I spent about 10 hours doing a full system switchover and cleaning up the mess including around 20 pacnew files. I thought it would have been easy to ask someone for a bit of help looking at something with a fresh set of eyes what with it being a 'support' forum and all.
While I can empathize with the ammount of work you may have had to do, this forum is not here for questions users could easily answer on their own except they are just to tired/lazy to do so. You expect someone else to do the leg work for you when you are unwilling?
Again, I can empathize with being tired. But if you are tired, have a beer and a good night's sleep and come back to working on your system with your own fresh set of eyes. You are right that this can be a support forum - but it is not a servant forum.
If/when you have done your own work and still face challenges, we are here to help. But most here also prefer to help by guiding a user in finding their own answers rather than giving them an answer they don't understand - the whole "teach a man to fish..."
So don't ask for fish-hand-outs. Come with rod in hand asking where to cast.

[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] RF Kill-related Service Fails

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

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

[SOLVED] systemd display-manager.service problem

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

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

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

Cisco 3560 service module failed state

Hi Expert,
My office has a Cisco 2911 ISR router, we installed a 3560 service module 16P on it.
But I use command "sh ip int bri" in 2911 router when we finished installation.
The result shows that the interface Gi 1/1 doesn't work, I have try to re-install SM 16P twice, the result is the same.
The normal 2911 ISR + 3560 SM 16P show as below,
2911#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Embedded-Service-Engine0/0 unassigned YES NVRAM administrativelwy down down
GigabitEthernet0/0 xxx.xxx.xxx.xxx YES manual up up
GigabitEthernet0/1 xxx.xxx.xxx.xxx YES NVRAM up up
GigabitEthernet0/2 unassigned YES NVRAM down down
GigabitEthernet1/0 xxx.xxx.xxx.xxx YES NVRAM up up
GigabitEthernet1/1 unassigned YES unset up up
The BAD 2911 ISR + 3560 SM 16P show as below,
2911#sh ip int brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 xxx.xxx.xxx.xxx YES NVRAM up up
GigabitEthernet0/1 unassigned YES NVRAM administratively down down
GigabitEthernet0/2 unassigned YES NVRAM administratively down down
GigabitEthernet1/0 unassigned YES NVRAM administratively down down

Hi Krishnendu,
I understand what you mean, I have done this work for assign Gi 1/0 an IP address, and then using command "service-module gi 1/0 session" to enter the service-module to configure it at all.
But I just want to know what is the Gi1/1 interface used for?
I use command "sh cdp nei" on others 2911 ISR + 3560 service module, all of the has the Gi 1/1 interface, and 2911 router using Gi 1/1 interface connected service module Gi 0/17. And Gi 1/1, Gi 0/17 is configured with "trunk interface".
I'm wondering whether my 2911 router Gi 1/1 has some physics error? or maybe it has another command to to "OPEN" the Gi 1/1 on 2911?
The "normal" switch display as below,
rtr001#sh cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
D - Remote, C - CVTA, M - Two-port Mac Relay
Device ID Local Intrfce Holdtme Capability Platform Port ID
swt000.nneas.net
Gig 1/0 129 R S I SM-ES3G-1 Gig 0/18
swt000.nneas.net
Gig 1/1 129 R S I SM-ES3G-1 Gig 0/17
Thanks in advance,
BR Frank

[SOLVED] systemd-modules-load fails

.. because it cannot find gspca. My log:
journalctl -xn
-- Logs begin at Thu 2013-08-22 11:43:18 CEST, end at Mon 2014-06-23 14:26:30 CEST. --
Jun 23 14:25:21 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop7" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop2" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop1" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" has new interfaces: ("org.
Jun 23 14:26:19 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" lost interfaces: ("org.fre
Jun 23 14:26:30 jiggs systemd[1]: Starting Load Kernel Modules...
-- Subject: Unit systemd-modules-load.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has begun starting up.
Jun 23 14:26:30 jiggs systemd-modules-load[3138]: Failed to find module 'gspca'
Jun 23 14:26:30 jiggs systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Jun 23 14:26:30 jiggs systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has failed.
-- The result is failed.
Jun 23 14:26:30 jiggs systemd[1]: Unit systemd-modules-load.service entered failed state.
But I have lots of gspca's:
# ls /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca
gl860 gspca_kinect.ko gspca_ov534.ko gspca_sonixj.ko gspca_sq905c.ko gspca_topro.ko
gspca_benq.ko gspca_konica.ko gspca_pac207.ko gspca_spca1528.ko gspca_sq905.ko gspca_tv8532.ko
gspca_conex.ko gspca_main.ko gspca_pac7302.ko gspca_spca500.ko gspca_sq930x.ko gspca_vc032x.ko
gspca_cpia1.ko gspca_mars.ko gspca_pac7311.ko gspca_spca501.ko gspca_stk014.ko gspca_vicam.ko
gspca_etoms.ko gspca_mr97310a.ko gspca_se401.ko gspca_spca505.ko gspca_stk1135.ko gspca_xirlink_cit.ko
gspca_finepix.ko gspca_nw80x.ko gspca_sn9c2028.ko gspca_spca506.ko gspca_stv0680.ko gspca_zc3xx.ko
gspca_jeilinj.ko gspca_ov519.ko gspca_sn9c20x.ko gspca_spca508.ko gspca_sunplus.ko m5602
gspca_jl2005bcd.ko gspca_ov534_9.ko gspca_sonixb.ko gspca_spca561.ko gspca_t613.ko stv06xx
The only difference I have with respect to a standard installation is that I downloaded an older version of the backport drivers, and in doing so I surely re-installed gspca.
So my questions are: where is systemd-module-load searching for gspca? How can I persuade it to search in the right directory? And in any case, why is it searching for it in the wrong place to start with?. Just in case,
# uname -a
Linux jiggs 3.15.1-1-ARCH #1 SMP PREEMPT Tue Jun 17 09:32:20 CEST 2014 x86_64 GNU/Linux
Last edited by MariusMatutiae (2014-06-26 09:10:22)

Problem solved, thanks to both of you guys. For some resason, I had a webcam.conf file in /etc/modules-load.d containing the single line *gspca*, which is not a module: both modprobe and insmod fail, because the correct module name is one of those listed in /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca. They are called gspca_benq.ko gspca_konica.ko and so on. I simply deleted the file since I do not need it.
As for backport drivers: this site, http://drvbp1.linux-foundation.org/~mcg … backports/ has the most recent versions of Linux drivers, backported so that older kernels can install them (I understand this is not a concern for fellow Archers). Whenever I need to upgrade (mostly on Debian) or downgrade (a few times on Arch, because an older version of a driver is free of a newly minted bug) I download these drivers, compile them and install them from source.

[SOLVED] systemd swap related service in failed state

Similar Messages

Maybe you are looking for