[Solved] DHCPCD seems to be causing a stop job on reboot

Theaigcaman · 2018-11-30 23:45:05

https://pastebin.com/3VJUm2c9 is the output of

journalctl

on an offending boot. I believe it is being caused by dhcpcd (or systemd being odd) as on line 870 after a 1.5 minute skip in the timestamps (how long the timeout was on reboot) it kills dhcpcd with SIGKILL.

Nov 30 16:24:05 craigsarchlinux systemd[1]: session-1.scope: Stopping timed out. Killing.
Nov 30 16:24:05 craigsarchlinux systemd[1]: session-1.scope: Killing process 1177 (dhcpcd) with signal SIGKILL.
Nov 30 16:24:05 craigsarchlinux systemd[1]: session-1.scope: Failed with result 'timeout'.

I've seen it happen upon rebooting with

sudo reboot

or by using KDE Plasma's reboot button. (the journalctl posted here is from a reboot invoked by using KDE Plasma's reboot button). I've looked a bit for a solution and can't find it, but if there is an existing solution feel free to give me a link.

EDIT: the exact message on reboot is

a stop job is running for Session 1 of user craigsimpson (time/1min 30s)

EDIT 2: seems the problem was having two instances of DHCPCD.

Last edited by Theaigcaman (2018-12-02 01:04:37)

seth · 2018-12-01 08:30:48

There kinda seem to be two dhcpcd instances running?

…
Nov 30 15:23:00 craigsarchlinuxdhcpcd[1112]: main: pidfile_lock: Permission denied
Nov 30 15:23:07 craigsarchlinux sudo[1122]: craigsimpson : TTY=pts/0 ; PWD=/home/craigsimpson ; USER=root ; COMMAND=/usr/bin/dhcpcd
Nov 30 15:23:07 craigsarchlinux sudo[1122]: pam_unix(sudo:session): session opened for user root by craigsimpson(uid=0)
Nov 30 15:23:07 craigsarchlinux dhcpcd[1123]: dev: loaded udev
…

One of them started by you, using sudo. The other one presumingly a systemd service?
Also there's an independent wpa_supplicant process?

You might want to elaborate on this, ie. "how do you intend to control your network itfp?".

Theaigcaman · 2018-12-01 20:39:41

i believe on that boot i was connected to the internet with a wpa_supplicant@interface.service with a config file that i generated using wpa_passphrase. The duplicate wpa_supplicant process may be the one made by NetworkManager, but i believe i uninstalled network manager. I'll try disabling the wpa_supplicant.service and see if i can figure out the duplicate DHCPCD process. Thanks for the help. Also, as an aside, as a general rule would it be better to post long logs like that to pastebin or to put them in a code block?

seth · 2018-12-01 22:09:26

The convenient way is https://wiki.archlinux.org/index.php/Pastebin
Please ensure that only one network daemon controls any interface - it's ok (though rarely practical) to use different daemons for different interfaces.

systemctl list-unit-files --state=enabled

Theaigcaman · 2018-12-02 01:04:01

Ok, the duplicated DHCPCD process seems to be the problem, specifically the one that was started manually. I've been using WPA_supplicant for connecting to secured networks and netctl for connecting to unsecured networks. If there is a way to use only one of them that would be convenient, but i haven't found it (although haven't looked very hard). Anyways, the TL;DR of this whole thing seems to be that manually starting a DHCPCD process while another is running as a service is not the best idea. Thanks a bunch for the help.

Arch Linux

#1 2018-11-30 23:45:05

[Solved] DHCPCD seems to be causing a stop job on reboot

#2 2018-12-01 08:30:48

Re: [Solved] DHCPCD seems to be causing a stop job on reboot

#3 2018-12-01 20:39:41

Re: [Solved] DHCPCD seems to be causing a stop job on reboot

#4 2018-12-01 22:09:26

Re: [Solved] DHCPCD seems to be causing a stop job on reboot

#5 2018-12-02 01:04:01

Re: [Solved] DHCPCD seems to be causing a stop job on reboot

Board footer