[solved] systemd dhcpcd service

Not sure what is failing with this output, a service file start dependency?
Mar 12 10:08:53 yrch systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device.
Mar 12 10:08:53 yrch systemd[1]: Dependency failed for dhcpcd on eth0.
This is the dhcpcd service file
[root@yrch multi-user.target.wants]# cat dh*
[Unit]
Description=dhcpcd on %I
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=forking
PIDFile=/run/dhcpcd-%I.pid
ExecStart=/usr/sbin/dhcpcd -q -w %I
ExecStop=/usr/sbin/dhcpcd -x %I
[Install]
WantedBy=multi-user.target
Also running dhcpcd standalone fails first attempt, works correctly second attempt.
Last edited by ackt1c (2014-11-23 08:36:28)

Is your device eth0? The interface naming scheme has changed, it's no longet eth0, eth1 and so on, but udev gives names to devices based on the MAC address now. Unless you manually changed config files, you will have this new naming scheme in effect. Check with ip link.
Last edited by elkoraco (2013-03-13 09:18:50)

Similar Messages

[Solved] systemd-sysctl.service failed to set parameters from 99-sy...

$ cat /etc/sysctl.d/99-sysctl.conf
# Protection from the SYN flood attack.
net.ipv4.tcp_syncookies = 1
# Disable packet forwarding.
net.ipv4.ip_forward = 0
# Tweak those values to alter disk syncing and swap behavior.
vm.vfs_cache_pressure = 1000
vm.swappiness = 0
# USB Speed
vm.dirty_ratio = 5
vm.dirty_background_ratio = 3
# KDE
fs.inotify.max_user_watches = 524288
$ cat /proc/sys/vm/dirty_ratio
10
$ cat /proc/sys/vm/dirty_background_ratio
5
but
$ cat /proc/sys/vm/swappiness
0
$ cat /proc/sys/vm/vfs_cache_pressure
1000
Only restarting of systemd-systct.service helps.
$ sudo systemctl restart systemd-sysctl.service
$ cat /proc/sys/vm/dirty_ratio
5
$ cat /proc/sys/vm/dirty_background_ratio
3
what am i doing wrong?
Solved with - % sudo chmod -x /usr/lib/pm-utils/power.d/laptop-mode
Last edited by Perfect Gentleman (2013-09-20 00:34:44)

Perfect Gentleman wrote:Solved with - % sudo chmod -x /usr/lib/pm-utils/power.d/laptop-mode
A more permanent solution is to mask that file
mkdir -p /etc/pm/power.d
touch /etc/pm/power.d/laptop-mode
which will not get written on update or reinstall. (Not than an update to this package seems at all likely but just in case.)

Systemd dhcpcd service failing on boot

Hi folks,
I'm trying to convert my workstation to "pure" systemd configuration (no initscripts-systemd):
[csingley@quadrupel ~]$ pacman -Qs systemd
local/libsystemd 185-3
systemd client libraries
local/systemd 185-3
system and service manager
local/systemd-arch-units 20120612-5
Arch specific Systemd unit files
local/systemd-sysvcompat 185-3
sysvinit compat for systemd
local/systemd-tools 185-3
standalone tools from systemd
Per the instructions on the wiki, I enabled [email protected], but the service fails to start upon boot.
[root@quadrupel csingley]# systemctl status [email protected]
[email protected] - dhcpcd on eth0
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Thu, 28 Jun 2012 12:36:16 -0500; 39s ago
Process: 299 ExecStart=/sbin/dhcpcd -A -q -w %I (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/[email protected]/eth0
However, I can start the service manually after the boot process is complete:
[root@quadrupel csingley]# systemctl start [email protected]
[root@quadrupel csingley]#
Presumably not all dependencies have been satisfied when systemd tries to run dhcpcd during boot.
I'm very new to systemd; any tips for troubleshooting this issue?
TIA

dj-x-cess wrote:
I have the same problem.
It seems, at least for my machine, dhcpcd starts before eth0 gets initialized on boot time:
Sep 05 07:38:39 vostro dhcpcd[180]: version 5.6.0 starting
Sep 05 07:38:39 vostro dhcpcd[180]: eth0: interface not found or invalid
Sep 05 07:38:39 vostro kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: irq 47 for MSI/MSI-X
Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: eth0: RTL8168d/8111d at 0xf9c00000, a4:ba:db:a6:a6:33, XID 083000c0 IRQ 47
Sep 05 07:38:39 vostro kernel: r8169 0000:13:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Yes. Same thing here with the latest install. I put "tg3" in /etc/modules-load.d/tigon.conf. Guess it loads it sooner then and now it gets an IP. Couldn't you make dhcpcd wait for eth0 to come up? It looks important, I mean dhcp should work I'm a newbie with Arch, installed it for the first time.
Here are my logs before the fix (I was looking in /var/log/, but then I found out that there is a journalctl command):
Nov 14 15:33:40 neimastina dhcpcd[176]: version 5.6.2 starting
Nov 14 15:33:40 neimastina dhcpcd[176]: eth0: interface not found or invalid
Nov 14 15:33:44 neimastina systemd[1]: [email protected]: control process exited, code=exited status=1
Nov 14 15:33:45 neimastina kernel: EDAC MC: Ver: 3.0.0
Nov 14 15:33:45 neimastina kernel: wmi: Mapper loaded
Nov 14 15:33:45 neimastina kernel: iTCO_vendor_support: vendor-support=0
Nov 14 15:33:45 neimastina kernel: tg3.c:v3.124 (March 21, 2012)
Nov 14 15:33:45 neimastina kernel: EDAC MC0: Giving out device to 'x38_edac' 'x38': DEV 0000:00:00.0
Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: Tigon3 [partno(BCM95751A519FLP) rev 4201] (PCI Express) MAC address 00:10:18:53:12:b7
Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Nov 14 15:33:45 neimastina kernel: tg3 0000:34:00.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Nov 14 15:33:45 neimastina kernel: gpio_ich: GPIO from 195 to 255 on gpio_ich

[Solved] systemd-hostnamed.service broken in systemd 212?

Can someone confirm by checking
hostnamectl status
and
systemctl --failed
Thanks!
Last edited by gedgon (2014-04-03 20:30:03)

teateawhy wrote:Works for me.
Hmm, interesting. In v.212 systemd-hostnamed.service failing for me, and hostnamectl timing out. Works fine after downgrading.
Edit: Problem caused by wrong /var/tmp permission. Thanks, teateawhy.
Last edited by gedgon (2014-04-03 20:29:47)

[SOLVED] systemd adsl service does not start

After the today's upgrade of my system I get lines like this in my journal, as the adsl service does not want to start.
# router systemd[522]: Failed at step EXEC spawning /usr/sbin/pppoe-start: No such file or directory
The problem is, that pppoe-start is in /usr/bin/ and not in /usr/sbin. According to pacman (pacman-Ql rp-pppoe) /usr/bin/ is the correct location.
I really don't know, why systemd is trying to launch it, because even the service file (/usr/lib/systemd/system/adsl.service) points to the correct location.
[Unit]
Description=ADSL Deamon
[Service]
Type=forking
ExecStart=/usr/bin/pppoe-start
ExecStop=/usr/bin/pppoe-stop
[Install]
WantedBy=multi-user.target
The service is launching and stopping with pppoe-start and pppoe-stop.
When launched, it also shuts down fine when stopping it by
systemctl stop adsl
Why the hell is it trying to launch from /usr/sbin/?
Last edited by scar (2013-06-04 13:07:23)

It goes definitely against any logic.
The service file looks good, but I've copied it to /usr/lib/systemd/system/bdsl.service. Same contents - and the new one launches succesfully.
I've deleted the original ...adsl.service file, verified that it disappeared, copied it back from the new bdsl.service file, and it still does not launch.
[EDIT]
I've erased the drive, restored the system from a 1 week old backup, started it - everything worked. Then I'v updated the whole system, including the rp-pppoe package, and the adsl service is failing again.
Downgrading solves the problem. Should I file a bug report?
Last edited by scar (2013-06-01 10:14:41)

[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 user service and timer dbus error

I have installed arch recently and added a few of my own services, for example the acpi_call commands and such. Now I want to create a systemd service that runs every 5 minutes and execute a script.
I searched a lot and I found that I must use timers. I got the thing with the timers working, but because my script has to do with a specific user, I want it to run only every 5 minutes when i am logged in as that user.
I tried to put the files in /etc/systemd/users, .config/local/users and all the possibilities but everytime i want to enable it, it says dbus connection refused.
Can somebody please provide me a way to execute a systemd service every 5 minutes while I am logged in as a specific user?
I did follow the wiki and created a dbus service and all. Everything works on that side but i can't enable my user service.
thanks!
Last edited by nopemopes (2015-03-25 11:10:06)

jasonwryan wrote:
What errors are you getting? https://bbs.archlinux.org/viewtopic.php?id=57855
Not a Sysadmin issue, moving to NC...
sorry, didn't mean to be incomplete.
The error says "Failed to get D-Bus connection: Connection refused".
I did what the wiki said: Create the dbus files, enable them and such.
No i put my service files + timer in the places mentioned by the wiki but everytime i try to enable them, that error shows up.
systemctl status dbus gives me all good
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
Active: active (running) since ma 2015-03-23 19:39:24 CET; 1h 18min ago
Docs: man:dbus-daemon(1)
Main PID: 246 (dbus-daemon)
CGroup: /system.slice/dbus.service
└─246 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
that's the log for dbus and these are my files:
drive_sync.service
[Unit]
Description=Drive sync
[Service]
Type=simple
ExecStart=drive_script.sh
drive_sync.timer
[Unit]
Description=Drive sync
[Service]
Type=simple
ExecStart=drive_script.sh
these files are located in ~/.config/systemd/user
Last edited by nopemopes (2015-03-23 20:00:55)

[SOLVED] Systemd fluidsynth service tries to load / fluidsynth removed

I recently moved to a pure systemd configuration and have been trying to familiarise myself with it.
I subsequently noticed that I had fluidsynth installed, and a pacman -Qi said that it was installed as a dependency for another package, but that no other packages currently required it. So I removed it.
Now when I run systemctl --failed I get the following output:
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
fluidsynth.service loaded failed failed FluidSynth Daemon
I can stop the service without any errors, but disabling it results in this:
$ sudo systemctl disable fluidsynth.service
Failed to issue method call: No such file or directory
I'm not really sure what this means. It doesn't seem to be causing any problems, but I'd like to understand what's going on and get everything working as it should. Can anyone suggest what I should do?
Last edited by esuhl (2012-10-16 01:38:21)

Cheers. But I can't see one there:
$ sudo ls -al /etc/systemd/system
total 32
drwxr-xr-x 8 root root 4096 Oct 14 02:50 .
drwxr-xr-x 5 root root 4096 Oct 14 02:50 ..
drwxr-xr-x 2 root root 4096 Aug 30 20:13 getty.target.wants
drwxr-xr-x 2 root root 4096 Oct 12 20:13 local-fs.target.wants
drwxr-xr-x 2 root root 4096 Oct 14 02:50 multi-user.target.wants
drwxr-xr-x 2 root root 4096 Oct 9 05:01 printer.target.wants
drwxr-xr-x 2 root root 4096 Oct 9 05:01 sockets.target.wants
drwxr-xr-x 2 root root 4096 Oct 12 20:13 sysinit.target.wants
lrwxrwxrwx 1 root root 41 Oct 9 04:55 syslog.service -> /usr/lib/systemd/system/syslog-ng.service
Last edited by esuhl (2012-10-16 00:04:22)

[SOLVED] systemd: autostart service last, at login screen

hi
I don't use X, so no .xinitrc, but I'd like to run a script after boot when it reaches the terminal login.
In particular, the script is a simple beep command to play a sound.
I tried this
[Unit]
Description=welcome
After=multi-user.target
[Service]
Type=oneshot
ExecStart=/usr/bin/beep -f 1000 -l 200 -n -f 1200 -l 200 -n -f 2000 -l 120
[Install]
but can't even enable it
any suggestions? thanks
Last edited by v43 (2014-01-19 13:50:56)

because of the empty [Install] section
EDIT:
I tried adding the regular WantedBy=multi-user.target in the [Install], and it works!!
but why? how can this service be required by the multi-user.target and also be called after it?
[Unit]
Description=welcome
After=multi-user.target
[Service]
Type=oneshot
ExecStart=/usr/bin/beep -f 1000 -l 200 -n -f 1200 -l 200 -n -f 2000 -l 120
[Install]
WantedBy=multi-user.target
Last edited by v43 (2014-01-19 13:49:31)

[Solved] SystemD, how to start a service after network is up.

Hello,
I'm recently involved to set up a daemon which should be ready after boot (aria2). Then it fails, as it fails minidlna as well.
The reason is that they try to come up but there's no host to talk to. See this page.
For my purposes, it should be good when the daemons find the necessary to stay alive (even they won't have a network fully ready, that may happen in less than a minute later). For minidlna is needed a valid IP which could be 127.0.0.1 or localhost, for aria2 it may be same or just looking for a RPC binding.
This what the logs are telling me.
I was trying to set more dependencies in the service, but even to set
After=wpa_supplicant.service
it doesn't have effect.
I don't find a solution, as far as my knowledge spans. Another chance would take to set a systemD timer and when that will be gone to start the daemon. Sorry but I don't know much about that.
Looking for someone here to guide to right direction.
TIA
Last edited by TheSaint (2013-07-15 03:12:37)

WonderWoofy wrote:It depends on what network management utility you use and therefore also how you connect. If you are using an ethernet connection, you could just use dhcpcd@<interface>.service. This is a very simple service, and the network.target will not be reached until the IP address and connectivity is established.
Meanwhile some good suggestion (like yours) came up, I've tried a couple of recipes. But dhcpcd.service didn't get it right. Maybe dhcpcd@<interface>.service, would work, I'll see later.
I got this working:
[Unit]
Description=aria2 Service
Requires=network.target
After=dhcpcd.service
[Service]
Type=forking
User=aria2
Group=aria2
EnvironmentFile=/etc/conf.d/aria2.conf
WorkingDirectory=/var/aria2
ExecStart=/usr/bin/aria2c $ARIACMD
ExecReload=/usr/bin/kill -HUP $MAINPID
RestartSec=1min
Restart=on-failure
[Install]
WantedBy=multi-user.target
You may note the After=dhcpcd.service, but it doesn't work. I found RestartSec=1min ,Restart=on-failure more effective and perhaps less blocking to wait for the network to be ready. As a server this should be a small issue, very seldom compared with the running time. We (family members) can accept a little wait for the service to be on.
Exactly I don't know which of the two is the right solution, maybe the delay is the right one.
I was doing a cron scheduled job, before using systemd boot, which was kicking minidlna every 5 minutes, since it was dieing often. I didn't discover what was the reason.
I think I'll have to study another recipe which sets up a timer and keep an eye on these two services, for the long term service. But even cron would suffice, I think.
WonderWoofy wrote:if you are using wireless, the only two real solutions would be to use netctl@<profile>.service, which too won't reach the network.target until a conplete connection is made
Yes I'm on wireless network and the interface plugged on USB . My intent should go beyond any particular configuration. Maybe because I'd like to show a working setup, which may fit for all configuration (90 % )
I have to admit that the actual solution do not care much whether the network is found, so I hope to get a smarter setup that counts on the necessary tools before try something. However it's proved that they fail when no connection to the router is done. But I'm preferring that they succeed.
WonderWoofy wrote: NetworkManager gets around this by implementing an additional service called (unimaginatively) NetworkManager-wait-online.service, which is pulled in automatically when you enable NetowrkManager.service.
As I stated above I'm expecting a solution that won't pull in so much dependencies. Even NM is my connection manager, on the server.
WonderWoofy wrote:
You probably also want to use Requisite=aria2c.service on the minidlna.service as well. This too means that it will be started after aria2c, but that it will not start at all if it is not running or fails.
Additionally, you could try using the Requisite configuration on the minidnla, while setting the aria2c to restart itself on failure. So that it will keep trying, and once it does, then minidlna will start.
looks like a dog biting the tail . It's much preferable a separated failure, just in case.
WonderWoofy wrote:Edit: Also, it is not SystemD. It is systemd (like other "daemon" binaries in *nix).
I'm quite sure I saw it somewhere, none of my inventions
Last edited by TheSaint (2013-07-13 07:10:33)

[SOLVED] defect dbus service, systemd is unable to create socket

Hi,
I am experiencing serious problems with systemd & dbus.
I want to setup a gateway in a KVM VM, all was working fine till i applied my shorewall config & set to autostart (systemctl enable shorewall).
If I reboot the machine after this step one or two times, then I get a broken dbus service.
What I did than: reinstalled archlinux again (x86_x64) and setup same -> got issue again.
installed arch linux as x86 and setup same -> issue again
installed arch as x86 and configured nothing else shorewall and got this issue again after maximum of two reboots.
i found in log:
Feb 13 15:45:56 pactor systemd[1]: Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
I've checked this directory by hand and found that only /var/run is existing. /var/run/dbus is already not existing.
logs:
journalctl -b: http://nopaste.info/685f4c6192.html
-be aware of systemd-logind, this needs dbus and i experience same problem with other services which require dbus as dnsmasq
root@pactor ~]# systemctl status dbus
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago
Main PID: 169 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─169 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[root@pactor ~]# systemctl status dbus.socket
dbus.socket - D-Bus System Message Bus Socket
Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static)
Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago
Feb 13 15:45:56 pactor systemd[1]: Listening on D-Bus System Message Bus Socket.
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: activating (start) since Mi 2013-02-13 16:00:56 CET; 48s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 338 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─338 /usr/lib/systemd/systemd-logind
Feb 13 16:00:56 pactor systemd[1]: Failed to start Login Service.
Feb 13 16:00:56 pactor systemd[1]: Unit systemd-logind.service entered failed state
Feb 13 16:00:56 pactor systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Feb 13 16:00:56 pactor systemd[1]: Stopping Login Service...
Feb 13 16:00:56 pactor systemd[1]: Starting Login Service...
installed packages: http://nopaste.info/1d1be9adad.html
shorewall config: shorewall_conf.tar
Last edited by debijan (2013-02-20 20:13:47)

oh man... found the reason due to help of some guys on systemd irc... big thx to falconindy and alxchk.
shorewall's SUBSYSLOCK option in shorewall.conf is by default set to /var/lock/shorewall.
but the arch wiki point that it should be set to /var/run: https://wiki.archlinux.org/index.php/Router
definitely wrong! that deletes the /var/run symlink and created a directory intstead.
to set the SUBSYSLOCK on default is working like a charm.
look also for this: https://bbs.archlinux.org/viewtopic.php?id=151285
could somebody modify the wiki in the meantime, i will hold this thread on -not-solved in the meantime
edit:/ oh man this wrong info in wiki did cost me a lot of time :-/
Last edited by debijan (2013-02-13 22:09:35)

[SOLVED] Can't start dhcpcd service

Hi,
I installed arch freshly and for some reboots connecting to the internet worked. Somehow I managed to mess it up.
I tried connecting to a openVPN network (which btw. failed) and when I came back to my other workplace, I could not connect to the internet.
The ethernet device is up according to ip link. When typing systemctl start dhcpcd@enp8s0 it tells me:
Failed to start [email protected]: The name org.freedesktop.PolicxKit1 was not provided bz any .service files
Any hinters how I can restore the default settings I had after/during the installation? My openVPN connectivity problem is a whole other problem, but it would be nice if I could connect to the internet when a router is available...
Thank you!
Last edited by mrkernelpanic (2014-10-03 12:15:58)

Yes I did use sudo, but let me try as root too.
So after login as root:
#systemctl enable dhcpcd.service
Created symlink from /etc/systemd/system/multi-user.target.wants/dhcpcd.service to /usr/lib/sysstemd/system/dhcpcd.service.
#ip link set enpd8s00 up
enp8s0 <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
So this results in a working DHCP:
● dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled)
Active: active (running) since Fri 2014-10-03 15:21:18 CEST; 5min ago
Process: 317 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
Main PID: 318 (dhcpcd)
CGroup: /system.slice/dhcpcd.service
└─318 /usr/bin/dhcpcd -q -b
Oct 03 15:26:00 lenovo_arch dhcpcd[318]: wlp2s0: if_sendrawpacket: Network is down
Oct 03 15:26:00 lenovo_arch dhcpcd[318]: wlp2s0: dhcp if_readrawpacket: Network is down
Oct 03 15:26:04 lenovo_arch dhcpcd[318]: wlp2s0: if_sendrawpacket: Network is down
Oct 03 15:26:04 lenovo_arch dhcpcd[318]: wlp2s0: dhcp if_readrawpacket: Network is down
Oct 03 15:26:08 lenovo_arch dhcpcd[318]: wlp2s0: if_sendrawpacket: Network is down
Oct 03 15:26:08 lenovo_arch dhcpcd[318]: wlp2s0: dhcp if_readrawpacket: Network is down
Oct 03 15:26:12 lenovo_arch dhcpcd[318]: wlp2s0: if_sendrawpacket: Network is down
Oct 03 15:26:12 lenovo_arch dhcpcd[318]: wlp2s0: dhcp if_readrawpacket: Network is down
Oct 03 15:26:16 lenovo_arch dhcpcd[318]: wlp2s0: if_sendrawpacket: Network is down
Oct 03 15:26:16 lenovo_arch dhcpcd[318]: wlp2s0: dhcp if_readrawpacket: Network is down
Oh, actually, systemctl status dhcpcd.service > text did output me something for enp8s0 and not just the wireless connections (which I ignore at this point). Let me reboot.
So this is the newest log. Everything run as root right after reboot.
#systemctl status dhcdpcd.serivce
● dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled)
Active: active (running) since Fri 2014-10-03 15:40:58 CEST; 38s ago
Process: 261 ExecStart=/usr/bin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
Main PID: 266 (dhcpcd)
CGroup: /system.slice/dhcpcd.service
└─266 /usr/bin/dhcpcd -q -b
Oct 03 15:40:58 lenovo_arch dhcpcd[266]: wlp2s0: carrier lost
Oct 03 15:40:59 lenovo_arch dhcpcd[266]: wlp2s0: soliciting a DHCP lease
Oct 03 15:41:00 lenovo_arch dhcpcd[266]: enp8s0: carrier acquired
Oct 03 15:41:00 lenovo_arch dhcpcd[266]: enp8s0: IAID 0e:69:ff:09
Oct 03 15:41:01 lenovo_arch dhcpcd[266]: enp8s0: rebinding lease of 192.168.33.___
Oct 03 15:41:01 lenovo_arch dhcpcd[266]: enp8s0: soliciting an IPv6 router
Oct 03 15:41:09 lenovo_arch dhcpcd[266]: enp8s0: leased 192.168.33.___ for 3600 seconds
Oct 03 15:41:09 lenovo_arch dhcpcd[266]: enp8s0: adding route to 192.168.32._/__
Oct 03 15:41:09 lenovo_arch dhcpcd[266]: enp8s0: adding default route via 192.168.32.___
Oct 03 15:41:14 lenovo_arch dhcpcd[266]: enp8s0: no IPv6 Routers available
#ip link
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: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 3c:97:0e:69:ff:09 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 60:36:dd:e3:57:b0 brd ff:ff:ff:ff:ff:ff
#openvpn /etc/openvpn/config.ovpn
Fri Oct 3 15:43:11 2014 DEPRECATED OPTION: --tls-remote, please update your configuration
Fri Oct 3 15:43:11 2014 OpenVPN 2.3.4 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on May 3 2014
Fri Oct 3 15:43:11 2014 library versions: OpenSSL 1.0.1i 6 Aug 2014, LZO 2.08
Fri Oct 3 15:43:17 2014 WARNING: file '/etc/openvpn/ta.key' is group or others accessible
Fri Oct 3 15:43:17 2014 Control Channel Authentication: using '/etc/openvpn/ta.key' as a OpenVPN static key file
Fri Oct 3 15:43:17 2014 failed to find GID for group nogroup
Fri Oct 3 15:43:17 2014 Exiting due to fatal error
To me, it seems like dhcp is running on ethernet now, but since I have no router at this place (only way to connect to the internet would be establishing a openVPN connection) these logs seem perfectly ok to me. The only thing bugging me right now, is that the wireless card is turned up by default.
Am I correct with the assumption that connecting to a router should work now?
Last edited by mrkernelpanic (2014-10-03 12:56:43)

[Solved] Suspend to Disk: systemd-hibernate.service Fails

Howdy-ha, folks. I know this looks pretty mundane, but for the life of me I can't get hibernation to work. Each time I run systemctl hibernate the screen will go blank as though preparing to suspend, then come back on; journalctl shows the same error messages:
PM: Cannot find swap device, try swapon -a.
PM: Cannot get swap writer
Failed to start Hibernate.
Dependency failed for Hibernate.
Service sleep.target is not needed anymore. Stopping.
Unit systemd-hibernate.service entered failed state.
This happens when swap is mounted, and "swapon" says as much. I've been working on this for about four hours now, and none of what I've found seems to pertain to my situation (most of the "solutions" were "Increase partition size').
What I've tried:
- Three different kernels---linux-ck custom build and linux-ck-sandybridge from graysky's repo (both with BFQ and CFQ: see below), as well as the stock Arch kernel
- A 2 Gb swap file at /swapfile on my SSD;
- A 4 Gb swap partition on /dev/mmcblk0 (an SD card, and my preferred method/location, if possible);
- An 8 Gb swap partition on HDD /dev/sdb2
Reasons for wanting hibernate rather than suspend-to-RAM:
- Maximize battery life.
- There's some kind of issue with Linux-ck and suspending to RAM; it'll work once, then freeze in a kernel panic the second time, forcing a hard reset. The stock kernel suspends to RAM, but still won't hibernate
- I put a lot of time into building a custom Linux-ck kernel, and would rather not have to start the configuration over with the stock kernel if possible.
I'm working with limited space on my boot drive and, as mentioned, increasing the amount of swap has no bearing on this. The resulting phenomenon and error messages are the same, regardless of size and medium. I've exhausted my ideas on where to look, and what to even look for. Thanks a lot to everyone in advance (especially you,karol; don't think I don't see you lurking back there )
Last edited by ANOKNUSA (2013-11-17 05:32:14)

I rebooted, so trying to recreate the same situation:
$ free -h
total used free shared buffers cached
Mem: 7.7G 7.2G 525M 0B 32M 2.3G
-/+ buffers/cache: 4.8G 2.9G
Swap: 3.7G 0B 3.7G
top reports nearly the same thing:
top - 20:00:13 up 22 min, 1 user, load average: 0.12, 0.22, 0.14
Tasks: 155 total, 1 running, 154 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.1 us, 0.3 sy, 0.1 ni, 99.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 8061380 total, 7500096 used, 561284 free, 34432 buffers
KiB Swap: 3872236 total, 0 used, 3872236 free, 2417172 cached
htop, however, reports about 1.5 Gb more free RAM. After reboot, swappiness is still set to 100 with the same results.
EDIT:
ANOKNUSA wrote: I'll test it again with the other locations mentioned in the OP, and get back to you.
Even though I rebooted, I haven't done this yet, so ignore it for the moment.
Last edited by ANOKNUSA (2013-08-28 01:06:10)

[SOLVED] Getting my systemd user service to talk to dbus

I'm currently trying to set up a nice email workflow with mbsync, msmtp and notmuch.
My passwords are saved in the Gnome keyring "login", and I've configured mbsync to use secret-tool to retrieve them. Unfortunately when secret-tool is invoked from this systemd user service there is an error when it in turn tries to call dbus-launch.
Here is the error:
$ systemctl --user status -l mbsync.service
● mbsync.service - Synchronise IMAP folders
Loaded: loaded (/home/leo/.config/systemd/user/mbsync.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2015-05-10 20:10:56 BST; 17min ago
Process: 3691 ExecStart=/usr/bin/mbsync -a (code=exited, status=1/FAILURE)
Main PID: 3691 (code=exited, status=1/FAILURE)
May 10 20:10:55 think3 mbsync[3691]: (secret-tool:3696): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 10 20:10:55 think3 mbsync[3691]: secret-tool: Error spawning command line 'dbus-launch --autolaunch=388eb9d3cc5542d5922d60c8f9605b31 --binary-syntax --close-stderr': Child process exited with code 1
May 10 20:10:55 think3 mbsync[3691]: Skipping account ymail, password command exited with status 1
May 10 20:10:56 think3 mbsync[3691]: (secret-tool:3698): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 10 20:10:56 think3 mbsync[3691]: secret-tool: Error spawning command line 'dbus-launch --autolaunch=388eb9d3cc5542d5922d60c8f9605b31 --binary-syntax --close-stderr': Child process exited with code 1
May 10 20:10:56 think3 mbsync[3691]: Skipping account gmail, password command exited with status 1
May 10 20:10:56 think3 systemd[716]: mbsync.service: main process exited, code=exited, status=1/FAILURE
May 10 20:10:56 think3 systemd[716]: Failed to start Synchronise IMAP folders.
May 10 20:10:56 think3 systemd[716]: Unit mbsync.service entered failed state.
May 10 20:10:56 think3 systemd[716]: mbsync.service failed.
The file mbsync.service is simply
[Unit]
Description=Synchronise IMAP folders
Wants=network-online.target
After=network-online.target
[Service]
Type=oneshot
ExecStart=/usr/bin/mbsync -a
Any ideas how I can use secret-tool from within a systemd user service? The Wiki includes some information about DBus and systemd here but it looks a little outdated...
Last edited by curiousleo (2015-05-22 22:02:33)

barbae wrote:Please could you post the output of 'journalctl -b' just after user login into gnome through gdm?
Sure thing. Here it is (I've cut out some stuff that obviously had nothing to do with the problem at hand):
May 17 17:17:11 think3 systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
May 17 17:17:11 think3 systemd[1]: Created slice Root Slice.
May 17 17:17:11 think3 systemd[1]: Starting Root Slice.
May 17 17:17:11 think3 systemd[1]: Created slice System Slice.
May 17 17:17:11 think3 systemd[1]: Starting System Slice.
May 17 17:17:11 think3 systemd[1]: Started Forward Password Requests to Wall Directory Watch.
May 17 17:17:11 think3 systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
May 17 17:17:11 think3 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
May 17 17:17:11 think3 systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
May 17 17:17:11 think3 systemd[1]: Reached target Login Prompts.
May 17 17:17:11 think3 systemd[1]: Starting Login Prompts.
May 17 17:17:11 think3 systemd[1]: Created slice User and Session Slice.
May 17 17:17:11 think3 systemd[1]: Starting User and Session Slice.
May 17 17:17:11 think3 systemd[1]: Reached target Slices.
May 17 17:17:11 think3 systemd[1]: Starting Slices.
May 17 17:17:11 think3 systemd[1]: Started Create System Users.
May 17 17:17:11 think3 systemd[1]: Created slice system-systemd\x2drfkill.slice.
May 17 17:17:11 think3 systemd[1]: Starting system-systemd\x2drfkill.slice.
May 17 17:17:11 think3 systemd[1]: Started Commit a transient machine-id on disk.
May 17 17:17:11 think3 systemd[1]: Started Daily verification of password and group files.
May 17 17:17:11 think3 systemd[1]: Starting Daily verification of password and group files.
May 17 17:17:11 think3 systemd[1]: Listening on D-Bus System Message Bus Socket.
May 17 17:17:11 think3 systemd[1]: Starting D-Bus System Message Bus Socket.
May 17 17:17:11 think3 systemd[1]: Reached target Sockets.
May 17 17:17:11 think3 systemd[1]: Starting Sockets.
May 17 17:17:11 think3 systemd[1]: Reached target Basic System.
May 17 17:17:11 think3 systemd[1]: Starting Basic System.
May 17 17:17:11 think3 systemd[1]: Starting Login Service...
May 17 17:17:11 think3 systemd[1]: Starting Permit User Sessions...
May 17 17:17:11 think3 systemd[1]: Started D-Bus System Message Bus.
May 17 17:17:11 think3 systemd[1]: Starting D-Bus System Message Bus...
May 17 17:17:11 think3 systemd[1]: Reached target Timers.
May 17 17:17:11 think3 systemd[1]: Starting Timers.
May 17 17:17:11 think3 systemd[1]: Started Permit User Sessions.
May 17 17:17:11 think3 systemd[1]: Starting GNOME Display Manager...
May 17 17:17:11 think3 systemd[1]: Started Login Service.
May 17 17:17:12 think3 systemd[1]: Started GNOME Display Manager.
May 17 17:17:12 think3 systemd[1]: Reached target Multi-User System.
May 17 17:17:12 think3 systemd[1]: Starting Multi-User System.
May 17 17:17:12 think3 systemd[1]: Reached target Graphical Interface.
May 17 17:17:12 think3 systemd[1]: Starting Graphical Interface.
May 17 17:17:12 think3 systemd-logind[293]: New seat seat0.
May 17 17:17:12 think3 dbus[301]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
May 17 17:17:12 think3 systemd[1]: Reached target User and Group Name Lookups.
May 17 17:17:12 think3 systemd[1]: Starting User and Group Name Lookups.
May 17 17:17:12 think3 systemd[1]: Starting Accounts Service...
May 17 17:17:13 think3 dbus[301]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
May 17 17:17:13 think3 systemd[1]: Starting Authorization Manager...
May 17 17:17:13 think3 polkitd[443]: Started polkitd version 0.112
May 17 17:17:13 think3 polkitd[443]: Loading rules from directory /etc/polkit-1/rules.d
May 17 17:17:13 think3 polkitd[443]: Loading rules from directory /usr/share/polkit-1/rules.d
May 17 17:17:13 think3 polkitd[443]: Finished loading, compiling and executing 3 rules
May 17 17:17:13 think3 dbus[301]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
May 17 17:17:13 think3 polkitd[443]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
May 17 17:17:13 think3 systemd[1]: Started Authorization Manager.
May 17 17:17:13 think3 accounts-daemon[436]: started daemon version 0.6.40
May 17 17:17:13 think3 dbus[301]: [system] Successfully activated service 'org.freedesktop.Accounts'
May 17 17:17:13 think3 systemd[1]: Started Accounts Service.
May 17 17:17:13 think3 systemd[1]: Created slice user-120.slice.
May 17 17:17:13 think3 systemd[1]: Starting user-120.slice.
May 17 17:17:13 think3 systemd[1]: Starting User Manager for UID 120...
May 17 17:17:13 think3 systemd-logind[293]: New session c1 of user gdm.
May 17 17:17:13 think3 systemd[1]: Started Session c1 of user gdm.
May 17 17:17:13 think3 systemd[1]: Starting Session c1 of user gdm.
May 17 17:17:13 think3 systemd[454]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
May 17 17:17:13 think3 systemd[454]: Unit type .busname is not supported on this system.
May 17 17:17:13 think3 systemd[454]: Reached target Paths.
May 17 17:17:13 think3 systemd[454]: Starting Paths.
May 17 17:17:13 think3 systemd[454]: Reached target Timers.
May 17 17:17:13 think3 systemd[454]: Starting Timers.
May 17 17:17:13 think3 systemd[454]: Reached target Sockets.
May 17 17:17:13 think3 systemd[454]: Starting Sockets.
May 17 17:17:13 think3 systemd[454]: Reached target Basic System.
May 17 17:17:13 think3 systemd[454]: Starting Basic System.
May 17 17:17:13 think3 systemd[454]: Reached target Default.
May 17 17:17:13 think3 systemd[454]: Startup finished in 3ms.
May 17 17:17:13 think3 systemd[454]: Starting Default.
May 17 17:17:13 think3 systemd[1]: Started User Manager for UID 120.
May 17 17:17:13 think3 gnome-session[460]: glamor: EGL version 1.4 (DRI2):
May 17 17:17:13 think3 org.a11y.Bus[459]: Activating service name='org.a11y.atspi.Registry'
May 17 17:17:13 think3 org.a11y.Bus[459]: Successfully activated service 'org.a11y.atspi.Registry'
May 17 17:17:13 think3 org.a11y.atspi.Registry[518]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 17 17:17:14 think3 polkitd[443]: Registered Authentication Agent for unix-session:c1 (system bus name :1.9 [gnome-shell --mode=gdm --wayland --display-server], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
May 17 17:17:18 think3 gdm-password][674]: pam_unix(gdm-password:session): session opened for user leo by (uid=0)
May 17 17:17:18 think3 systemd[1]: Created slice user-1000.slice.
May 17 17:17:18 think3 systemd[1]: Starting user-1000.slice.
May 17 17:17:18 think3 systemd[1]: Starting User Manager for UID 1000...
May 17 17:17:18 think3 systemd[1]: Started Session c2 of user leo.
May 17 17:17:18 think3 systemd-logind[293]: New session c2 of user leo.
May 17 17:17:18 think3 systemd[1]: Starting Session c2 of user leo.
May 17 17:17:18 think3 systemd[717]: pam_unix(systemd-user:session): session opened for user leo by (uid=0)
May 17 17:17:18 think3 systemd[717]: Unit type .busname is not supported on this system.
May 17 17:17:18 think3 systemd[717]: Started Synchronise e-mails and create database dump once a day.
May 17 17:17:18 think3 systemd[717]: Starting Synchronise e-mails and create database dump once a day.
May 17 17:17:18 think3 systemd[717]: Reached target default.target.
May 17 17:17:18 think3 systemd[717]: Startup finished in 13ms.
May 17 17:17:18 think3 systemd[717]: Starting default.target.
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: /etc/gdm/Xsession: Beginning session setup...
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: localuser:leo being added to access control list
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.a11y.Bus'
May 17 17:17:19 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.a11y.Bus'
May 17 17:17:19 think3 org.a11y.Bus[732]: Activating service name='org.a11y.atspi.Registry'
May 17 17:17:19 think3 org.a11y.Bus[732]: Successfully activated service 'org.a11y.atspi.Registry'
May 17 17:17:19 think3 org.a11y.atspi.Registry[756]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 17 17:17:19 think3 gnome-session[734]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 17 17:17:19 think3 gnome-session[734]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 17 17:17:19 think3 gnome-session[734]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
May 17 17:17:20 think3 polkitd[443]: Registered Authentication Agent for unix-session:c2 (system bus name :1.43 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
May 17 17:17:20 think3 gnome-session[734]: Entering running state
May 17 17:17:21 think3 gnome-shell[804]: GNOME Shell started at Sun May 17 2015 17:17:20 GMT+0100 (BST)
May 17 17:17:52 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.gnome.seahorse.Application'
May 17 17:17:52 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.gnome.seahorse.Application'
May 17 17:20:48 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.gnome.seahorse.Application'
May 17 17:20:48 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.gnome.seahorse.Application'

[SOLVED] Trouble with running systemd user service on login

I'm trying to get emacs to run as a systemd/user service so that it will start up faster, as suggested in the wiki article, but I'm having some problems.
I can't get the service to run as soon as I log in. I can run the service with
systemctl --user start emacs
and it will run for the rest of my session, but if I try to run
systemctl --user enable emacs
I get the following error:
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
I ran
systemctl --user is-enabled emacs
and that returned
static
but I'm not sure what that means. Any help would be greatly appreciated.
Last edited by whitebrice (2014-06-28 17:20:13)

Are you sure there isn't a typo in your unit file? The example you linked to in the wiki does have an [Install] section.
Post your ~/.config/systemd/user/emacs.service file here so we can take a look.

[solved] systemd dhcpcd service

Similar Messages

Maybe you are looking for