dhcpcd@.service causes slow poweroff

pptp · 2020-04-22 15:11:06

As per the wiki, there's a way to avoid it cause slow startup, but I also experience slow poweroff/reboot: the 90s it takes systemd to stop it.

A stop job is running for dhcpcd on wlp4s0 (45s / 1min 31s)

Is there a similar method to address this problem?

Last edited by pptp (2020-04-22 15:18:01)

dakota · 2020-04-22 19:07:43

Did you notice this behavior on dhcpcd-8.1.7-1? Or only after upgrading to 9.0.1-2?

FWIW, I experienced the same problem when upgrading to dhcpcd-9.0.1-2. The problem persisted when I tried the Testing version: dhcpcd-9.0.2-1, and disappeared when I temporarily downgraded to dhcpcd-8.1.7-1. (I am currently running dhcpcd-9.0.1-2.)

I can provide log files, but I don't want to hijack your thread.

You may want to post the journal from a previous boot, showing the shutdown error, e.g.,

$ journalctl -b -1

Cheers,

pptp · 2020-04-22 20:04:44

Thanks. I set up this configuration today, so I do not know about previous dhcpcd versions, I will try downgrading.
I think this is the relevant log:

systemd[1]: Stopping dhcpcd on wlp4s0...
dhcpcd[3091]: sending commands to dhcpcd process
dhcpcd[3091]: sending commands to dhcpcd process
dhcpcd[706]: control command: /usr/bin/dhcpcd -x wlp4s0
dhcpcd[706]: wlp4s0: removing interface
dhcpcd[707]: process 707 unexpectedly terminating on signal 15
systemd[1]: dhcpcd@wlp4s0.service: State 'stop-sigterm' timed out. Killing.
systemd[1]: dhcpcd@wlp4s0.service: Killing process 706 (dhcpcd) with signal SIGKILL.
dhcpcd@wlp4s0.service: Main process exited, code=killed, status=9/KILL
dhcpcd@wlp4s0.service: Failed with result 'timeout'.
systemd[1]: Stopped dhcpcd on wlp4s0.
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@wlp4s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
kernel: audit: type=1131 audit(1587578915.721:96): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@wlp4s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
systemd[1]: Removed slice system-dhcpcd.slice.

fluttershy · 2020-04-23 03:27:32

I have the same issue on my Thinkpad T480s and T520

If there is anything I can contribute from my configuration to fix the problem, please let me know what you need.

T480s

Apr 22 21:48:45 apocalypse10 systemd[1]: Stopped Docker Application Container Engine.
Apr 22 21:48:45 apocalypse10 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=docker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 22 21:48:45 apocalypse10 systemd[1]: Stopped target Network is Online.
Apr 22 21:48:45 apocalypse10 systemd[1]: Stopped target Network.
Apr 22 21:48:45 apocalypse10 systemd[1]: Stopping Networking for netctl profile fb...
Apr 22 21:48:45 apocalypse10 network[64435]: Stopping network profile 'fb'...
Apr 22 21:48:45 apocalypse10 dhcpcd[1195]: wlp61s0: pid 64440 deleted default route via 192.168.xx.1
Apr 22 21:48:45 apocalypse10 dhcpcd[1195]: wlp61s0: pid 64440 deleted route to 192.168.xx.0/24
Apr 22 21:48:45 apocalypse10 dhcpcd[1195]: wlp61s0: pid 64444 deleted IP address 192.168.xx.xx/24
Apr 22 21:48:45 apocalypse10 dhcpcd[1195]: wlp61s0: rebinding lease of 192.168.xx.xx
Apr 22 21:48:45 apocalypse10 dhcpcd[1195]: wlp61s0: probing address 192.168.xx.xx/24
Apr 22 21:48:45 apocalypse10 kernel: wlp61s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 22 21:48:45 apocalypse10 dhcpcd[1195]: wlp61s0: carrier lost
Apr 22 21:48:45 apocalypse10 dhcpcd[64484]: ps_bpf_recvbpf: Network is down
Apr 22 21:48:45 apocalypse10 network[64435]: Stopped network profile 'fb'
Apr 22 21:48:45 apocalypse10 dhcpcd[1195]: received SIGTERM, stopping
Apr 22 21:48:45 apocalypse10 dhcpcd[1195]: wlp61s0: removing interface
Apr 22 21:48:45 apocalypse10 dhcpcd[1196]: process 1196 unexpectedly terminating on signal 15
Apr 22 21:50:15 apocalypse10 systemd[1]: netctl@fb.service: State 'stop-sigterm' timed out. Killing.
Apr 22 21:50:15 apocalypse10 systemd[1]: netctl@fb.service: Killing process 1195 (dhcpcd) with signal SIGKILL.
Apr 22 21:50:15 apocalypse10 systemd[1]: netctl@fb.service: Failed with result 'timeout'.
Apr 22 21:50:15 apocalypse10 systemd[1]: Stopped Networking for netctl profile fb.
Apr 22 21:50:15 apocalypse10 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@fb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 22 21:50:15 apocalypse10 kernel: kauditd_printk_skb: 12 callbacks suppressed
Apr 22 21:50:15 apocalypse10 kernel: audit: type=1131 audit(1587585015.619:696): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@fb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 22 21:50:15 apocalypse10 systemd[1]: Removed slice system-netctl.slice.
Apr 22 21:50:15 apocalypse10 systemd[1]: Stopped target Basic System.

arojas · 2020-04-23 08:02:22

How are you running dhcpcd?

pptp · 2020-04-23 08:43:43

@dakota You are right, if I downgrade to dhcpcd-8.1.7-1-x86_64.pkg.tar.zst then my reboot/poweroff problem disappears too.
@arojas I use

sudo systemctl enable dhcpcd@wlp4s0.service
sudo systemctl enable wpa_supplicant@wlp4s0.service

Head_on_a_Stick · 2020-04-23 10:54:52

fluttershy wrote:

I have the same issue

Not quite, you appear to be using netctl whereas the OP is using dpcpcd & wpa_supplicant.

If downgrading dhcpcd doesn't fix things for you then perhaps try switching to dhclient instead.

Lone_Wolf · 2020-04-23 11:03:43

I noticed the same 90 seconds timeout on 2 machines (one intel, one amd) .
Didn't investigate the cause, but it doesn't happen anymore with latest dhcpcd 9.0.2-1 .

It was moved to core[1] approx 4 hours ago, I advise you all to run pacman -Syu .

[1] https://git.archlinux.org/svntogit/pack … b40277c03c

pptp · 2020-04-23 13:47:26

Ehm, it still happens to me with

pacman -Q | grep dhcp
dhcpcd 9.0.2-1

dakota · 2020-04-23 13:58:38

A full system upgrade (dhcpcd = 9.0.2-1) did not fix the problem for me.

FWIW, my system shuts down cleanly about 25% of the time, the rest of the time it times out. My situation might be different as I am running a VPN... but it looks like the VPN is shutting down cleanly and then the call to stop dhcpcd@enp0s25.service times out.

I am starting dhcpcd as: systemctl enable dhcpcd@enp0s25.service

$ journalctl -b -1 | grep dhcpcd
--------------------------------
Apr 23 06:28:23 freckle systemd[1]: Created slice system-dhcpcd.slice.
Apr 23 06:28:25 freckle systemd[1]: Starting dhcpcd on enp0s25...
Apr 23 06:28:25 freckle dhcpcd[349]: dhcpcd-9.0.2 starting
Apr 23 06:28:26 freckle dhcpcd[379]: enp0s25: waiting for carrier
Apr 23 06:28:29 freckle dhcpcd[379]: enp0s25: carrier acquired
Apr 23 06:28:29 freckle dhcpcd[379]: DUID 00:01:00:01:26:2f:3b:4c:00:21:86:28:0d:2c
Apr 23 06:28:29 freckle dhcpcd[379]: enp0s25: IAID 86:28:0d:2c
Apr 23 06:28:29 freckle dhcpcd[379]: enp0s25: adding address fe80::1e37:9e7c:1cb4:3c76
Apr 23 06:28:29 freckle dhcpcd[379]: enp0s25: soliciting an IPv6 router
Apr 23 06:28:30 freckle dhcpcd[379]: enp0s25: rebinding lease of 10.10.32.64
Apr 23 06:28:30 freckle dhcpcd[379]: enp0s25: leased 10.10.32.64 for 86400 seconds
Apr 23 06:28:30 freckle dhcpcd[379]: enp0s25: adding route to 10.10.32.0/24
Apr 23 06:28:30 freckle dhcpcd[379]: enp0s25: adding default route via 10.10.32.1
Apr 23 06:28:30 freckle systemd[1]: Started dhcpcd on enp0s25.
Apr 23 06:28:30 freckle audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@enp0s25 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 23 06:28:30 freckle kernel: audit: type=1130 audit(1587648510.838:18): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@enp0s25 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 23 06:28:42 freckle dhcpcd[379]: enp0s25: no IPv6 Routers available
Apr 23 06:30:12 freckle systemd[1]: Stopping dhcpcd on enp0s25...
Apr 23 06:30:12 freckle dhcpcd[880]: sending commands to dhcpcd process
Apr 23 06:30:12 freckle dhcpcd[880]: sending commands to dhcpcd process
Apr 23 06:30:12 freckle dhcpcd[379]: control command: /usr/bin/dhcpcd -x enp0s25
Apr 23 06:30:12 freckle dhcpcd[379]: enp0s25: removing interface
Apr 23 06:30:12 freckle dhcpcd[380]: process 380 unexpectedly terminating on signal 15
Apr 23 06:31:43 freckle systemd[1]: dhcpcd@enp0s25.service: State 'stop-sigterm' timed out. Killing.
Apr 23 06:31:43 freckle systemd[1]: dhcpcd@enp0s25.service: Killing process 379 (dhcpcd) with signal SIGKILL.
Apr 23 06:31:43 freckle systemd[1]: dhcpcd@enp0s25.service: Main process exited, code=killed, status=9/KILL
Apr 23 06:31:43 freckle systemd[1]: dhcpcd@enp0s25.service: Failed with result 'timeout'.
Apr 23 06:31:43 freckle systemd[1]: Stopped dhcpcd on enp0s25.
Apr 23 06:31:43 freckle audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@enp0s25 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 23 06:31:43 freckle systemd[1]: Removed slice system-dhcpcd.slice.
Apr 23 06:31:43 freckle kernel: audit: type=1131 audit(1587648703.099:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@enp0s25 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 23 06:31:43 freckle systemd[1]: Unmounting /var/lib/dhcpcd/dev...
Apr 23 06:31:43 freckle systemd[1]: Unmounting /var/lib/dhcpcd/proc...
Apr 23 06:31:43 freckle systemd[1]: Unmounting /var/lib/dhcpcd/run/systemd/journal...
Apr 23 06:31:43 freckle systemd[1]: Unmounting /var/lib/dhcpcd/run/udev...
Apr 23 06:31:43 freckle systemd[1]: Unmounting /var/lib/dhcpcd/sys...
Apr 23 06:31:43 freckle systemd[1]: var-lib-dhcpcd-dev.mount: Succeeded.
Apr 23 06:31:43 freckle systemd[1]: Unmounted /var/lib/dhcpcd/dev.
Apr 23 06:31:43 freckle systemd[1]: var-lib-dhcpcd-proc.mount: Succeeded.
Apr 23 06:31:43 freckle systemd[1]: Unmounted /var/lib/dhcpcd/proc.
Apr 23 06:31:43 freckle systemd[1]: var-lib-dhcpcd-run-systemd-journal.mount: Succeeded.
Apr 23 06:31:43 freckle systemd[1]: Unmounted /var/lib/dhcpcd/run/systemd/journal.
Apr 23 06:31:43 freckle systemd[1]: var-lib-dhcpcd-run-udev.mount: Succeeded.
Apr 23 06:31:43 freckle systemd[1]: Unmounted /var/lib/dhcpcd/run/udev.
Apr 23 06:31:43 freckle systemd[1]: var-lib-dhcpcd-sys.mount: Succeeded.
Apr 23 06:31:43 freckle systemd[1]: Unmounted /var/lib/dhcpcd/sys.

Full dmesg: http://ix.io/2jcE
Full journal: http://ix.io/2jcF

Cheers,

pptp · 2020-04-23 14:53:11

dakota wrote:

system shuts down cleanly about 25% of the time

Same for me.

cirrus · 2020-04-24 14:05:09

disabling dhcpcd@ service(s) & switching to dhclient rectified matters for me.

Last edited by cirrus (2020-04-24 15:35:22)

fluttershy · 2020-04-25 03:38:11

I have now set the value DHCPClient='dhclient' in the Netctl profile and now it terminates again without any delay.

I must have missed that when I set it up. I had only used the default configuration here and all these years it worked quite well.

Now my VirtualBox configuration doesn't work anymore, but then I finally have something to do. It's time for me to learn more about the network configuration. :-)

arojas · 2020-04-25 07:44:33

fluttershy wrote:

I have now set the value DHCPClient='dhclient' in the Netctl profile and now it terminates again without any delay.
I must have missed that when I set it up. I had only used the default configuration here and all these years it worked quite well.
Now my VirtualBox configuration doesn't work anymore, but then I finally have something to do. It's time for me to learn more about the network configuration. :-)

netctl is fixed upstream. Until a new version is released you can monkey-patch the installed version yourself, since it's just a script.

dakota · 2020-04-26 20:41:37

FYI - bug report: FS#66405 - [dhcpcd] Unclean stop

pptp · 2020-04-27 09:12:41

@dakota Thanks, somehow I missed updates from this thread.

zpg443 · 2020-05-02 17:19:18

I was having this same issue:

dakota wrote:

A full system upgrade (dhcpcd = 9.0.2-1) did not fix the problem for me.
FWIW, my system shuts down cleanly about 25% of the time, the rest of the time it times out. My situation might be different as I am running a VPN... but it looks like the VPN is shutting down cleanly and then the call to stop dhcpcd@enp0s25.service times out...

Same thing, except OpenVPN did not cause the problem. I compared the logs of successful and unsuccessful shutdowns and studied differences with the unsuccessful one. Have you tried that?

In my case, it was the profile-sync-daemon, which did not have time to sync since the new dhcpcd version. dhcpcd was having to restart sddm to retry the profile sync, and this is what caused my delays with shutdown.
Stopping and disabling the profile-sync-daemon service solved the problem for me with shutting down in a timely manner. For you, it might be a different service.

Last edited by zpg443 (2020-05-02 19:18:44)

boban_dj · 2020-05-03 05:02:27

@zpg443 out of curiosity, these are my findings with delay and whithout delay. Can you find anything that causes this delay?

My dhcpcd 9.0.2-1 on 5.4.36-1-lts, when shutting down and no delay (journalctl -b -1):

May 03 06:29:19 archz800 systemd[1]: Stopping dhcpcd on enp1s0...
May 03 06:29:19 archz800 systemd[1]: dbus.service: Succeeded.
May 03 06:29:19 archz800 systemd[1]: Stopped D-Bus System Message Bus.
May 03 06:29:19 archz800 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 03 06:29:19 archz800 dhcpcd[2668]: sending commands to dhcpcd process
May 03 06:29:19 archz800 dhcpcd[2668]: sending commands to dhcpcd process
May 03 06:29:19 archz800 dhcpcd[712]: control command: /usr/bin/dhcpcd -x enp1s0
May 03 06:29:19 archz800 dhcpcd[712]: enp1s0: removing interface
May 03 06:29:19 archz800 dhcpcd[713]: process 713 unexpectedly terminating on signal 15
May 03 06:29:19 archz800 dhcpcd[712]: main: control_stop: Broken pipe
May 03 06:29:19 archz800 dhcpcd[712]: ps_dostop: Connection refused
May 03 06:29:19 archz800 dhcpcd[712]: ps_dostop: Broken pipe
May 03 06:29:19 archz800 dhcpcd[712]: dhcpcd exited
May 03 06:29:19 archz800 systemd[1]: dhcpcd@enp1s0.service: Main process exited, code=exited, status=1/FAILURE
May 03 06:29:19 archz800 systemd[1]: dhcpcd@enp1s0.service: Failed with result 'exit-code'.
May 03 06:29:19 archz800 systemd[1]: Stopped dhcpcd on enp1s0.

But when shutting down with delay (journalctl -b -2):

May 02 13:34:20 archz800 dhcpcd[40172]: sending commands to dhcpcd process
May 02 13:34:20 archz800 dhcpcd[40172]: sending commands to dhcpcd process
May 02 13:34:20 archz800 dhcpcd[701]: control command: /usr/bin/dhcpcd -x enp1s0
May 02 13:34:20 archz800 dhcpcd[701]: enp1s0: removing interface
May 02 13:34:20 archz800 dhcpcd[702]: process 702 unexpectedly terminating on signal 15
May 02 13:34:20 archz800 systemd[1]: systemd-logind.service: Succeeded.
May 02 13:34:20 archz800 systemd[1]: Stopped Login Service.
May 02 13:34:20 archz800 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 02 13:35:50 archz800 systemd[1]: dhcpcd@enp1s0.service: State 'stop-sigterm' timed out. Killing.
May 02 13:35:50 archz800 systemd[1]: dhcpcd@enp1s0.service: Killing process 701 (dhcpcd) with signal SIGKILL.
May 02 13:35:50 archz800 systemd[1]: dhcpcd@enp1s0.service: Main process exited, code=killed, status=9/KILL
May 02 13:35:50 archz800 systemd[1]: dhcpcd@enp1s0.service: Failed with result 'timeout'.
May 02 13:35:50 archz800 systemd[1]: Stopped dhcpcd on enp1s0.
May 02 13:35:50 archz800 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@enp1s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
May 02 13:35:50 archz800 systemd[1]: Removed slice system-dhcpcd.slice.

zpg443 · 2020-05-05 16:53:15

boban_dj wrote:

@zpg443 out of curiosity, these are my findings with delay and whithout delay. Can you find anything that causes this delay?

My dhcpcd 9.0.2-1 on 5.4.36-1-lts, when shutting down and no delay (journalctl -b -1):

May 03 06:29:19 archz800 systemd[1]: Stopping dhcpcd on enp1s0...
May 03 06:29:19 archz800 systemd[1]: dbus.service: Succeeded.
May 03 06:29:19 archz800 systemd[1]: Stopped D-Bus System Message Bus.
May 03 06:29:19 archz800 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 03 06:29:19 archz800 dhcpcd[2668]: sending commands to dhcpcd process
May 03 06:29:19 archz800 dhcpcd[2668]: sending commands to dhcpcd process
May 03 06:29:19 archz800 dhcpcd[712]: control command: /usr/bin/dhcpcd -x enp1s0
May 03 06:29:19 archz800 dhcpcd[712]: enp1s0: removing interface
May 03 06:29:19 archz800 dhcpcd[713]: process 713 unexpectedly terminating on signal 15
May 03 06:29:19 archz800 dhcpcd[712]: main: control_stop: Broken pipe
May 03 06:29:19 archz800 dhcpcd[712]: ps_dostop: Connection refused
May 03 06:29:19 archz800 dhcpcd[712]: ps_dostop: Broken pipe
May 03 06:29:19 archz800 dhcpcd[712]: dhcpcd exited
May 03 06:29:19 archz800 systemd[1]: dhcpcd@enp1s0.service: Main process exited, code=exited, status=1/FAILURE
May 03 06:29:19 archz800 systemd[1]: dhcpcd@enp1s0.service: Failed with result 'exit-code'.
May 03 06:29:19 archz800 systemd[1]: Stopped dhcpcd on enp1s0.

But when shutting down with delay (journalctl -b -2):

May 02 13:34:20 archz800 dhcpcd[40172]: sending commands to dhcpcd process
May 02 13:34:20 archz800 dhcpcd[40172]: sending commands to dhcpcd process
May 02 13:34:20 archz800 dhcpcd[701]: control command: /usr/bin/dhcpcd -x enp1s0
May 02 13:34:20 archz800 dhcpcd[701]: enp1s0: removing interface
May 02 13:34:20 archz800 dhcpcd[702]: process 702 unexpectedly terminating on signal 15
May 02 13:34:20 archz800 systemd[1]: systemd-logind.service: Succeeded.
May 02 13:34:20 archz800 systemd[1]: Stopped Login Service.
May 02 13:34:20 archz800 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 02 13:35:50 archz800 systemd[1]: dhcpcd@enp1s0.service: State 'stop-sigterm' timed out. Killing.
May 02 13:35:50 archz800 systemd[1]: dhcpcd@enp1s0.service: Killing process 701 (dhcpcd) with signal SIGKILL.
May 02 13:35:50 archz800 systemd[1]: dhcpcd@enp1s0.service: Main process exited, code=killed, status=9/KILL
May 02 13:35:50 archz800 systemd[1]: dhcpcd@enp1s0.service: Failed with result 'timeout'.
May 02 13:35:50 archz800 systemd[1]: Stopped dhcpcd on enp1s0.
May 02 13:35:50 archz800 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@enp1s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
May 02 13:35:50 archz800 systemd[1]: Removed slice system-dhcpcd.slice.

I cannot tell with a partial printout of each.

drankinatty · 2020-05-15 06:03:20

I am seeing the same thing on all my Arch boxes that get their IP by dhcpcd. On poweroff (not reboot) the shutdown hangs on the 1:30 timer waiting for whatever dhcpcd is waiting for. The message with `quiet` removed from the kernel line is

    "a stop job is running for dhcpcd on enp0s3 (Xs of 1min 30s)".

I have observed this on Dell, SuperMicro and Gigabyte hardware as well as virtual guest on VirtualBox. This did not start until around the 5.6.8 kernel (whatever dhcpcd that corresponds to).

boban_dj · 2020-05-15 06:31:32

from the bugreport link I added n my systemd file KillMode=process
since then everything was shutting down normally

evan-hon · 2020-05-16 03:19:16

it is same for me.

but there is no tips like

A stop job is running for dhcpcd on wlp4s0 (45s / 1min 31s)

for me. Only one cursor flashes throughout the interface.

when I close manually the dhcpcd service,the system can be closed normally.

Self-Perfection · 2020-05-16 07:45:11

Same for me

мая 15 21:12:53 systemd[1]: Stopping dhcpcd on enp2s0...
мая 15 21:12:53 dhcpcd[25204]: sending commands to dhcpcd process
мая 15 21:12:53 dhcpcd[25204]: sending commands to dhcpcd process
мая 15 21:12:53 dhcpcd[1250]: control command: /usr/bin/dhcpcd -x enp2s0
мая 15 21:12:53 dhcpcd[1250]: enp2s0: removing interface
мая 15 21:12:53 dhcpcd[1251]: process 1251 unexpectedly terminating on signal 15
мая 15 21:14:23 systemd[1]: dhcpcd@enp2s0.service: State 'stop-sigterm' timed out. Killing.
мая 15 21:14:23 systemd[1]: dhcpcd@enp2s0.service: Killing process 1250 (dhcpcd) with signal SIGKILL.
мая 15 21:14:23 systemd[1]: dhcpcd@enp2s0.service: Main process exited, code=killed, status=9/KILL
мая 15 21:14:23 systemd[1]: dhcpcd@enp2s0.service: Failed with result 'timeout'.
мая 15 21:14:23 systemd[1]: Stopped dhcpcd on enp2s0

I switched to dhclient, it does not have such slowdown.

babubobu · 2020-05-22 15:38:33

Following change has solved the shutdown delay for me:

# systemctl disable dhcpcd@enp2s0.service
# systemctl enable dhcpcd

Not sure what disadvantages this brings with it.

Captain Athelas · 2020-05-23 09:14:30

babubobu wrote:

Following change has solved the shutdown delay for me:
# systemctl disable dhcpcd@enp2s0.service
# systemctl enable dhcpcd
Not sure what disadvantages this brings with it.

This fixed it for me as well.

Arch Linux

#1 2020-04-22 15:11:06

dhcpcd@.service causes slow poweroff

#2 2020-04-22 19:07:43

Re: dhcpcd@.service causes slow poweroff

#3 2020-04-22 20:04:44

Re: dhcpcd@.service causes slow poweroff

#4 2020-04-23 03:27:32

Re: dhcpcd@.service causes slow poweroff

#5 2020-04-23 08:02:22

Re: dhcpcd@.service causes slow poweroff

#6 2020-04-23 08:43:43

Re: dhcpcd@.service causes slow poweroff

#7 2020-04-23 10:54:52

Re: dhcpcd@.service causes slow poweroff

#8 2020-04-23 11:03:43

Re: dhcpcd@.service causes slow poweroff

#9 2020-04-23 13:47:26

Re: dhcpcd@.service causes slow poweroff

#10 2020-04-23 13:58:38

Re: dhcpcd@.service causes slow poweroff

#11 2020-04-23 14:53:11

Re: dhcpcd@.service causes slow poweroff

#12 2020-04-24 14:05:09

Re: dhcpcd@.service causes slow poweroff

#13 2020-04-25 03:38:11

Re: dhcpcd@.service causes slow poweroff

#14 2020-04-25 07:44:33

Re: dhcpcd@.service causes slow poweroff

#15 2020-04-26 20:41:37

Re: dhcpcd@.service causes slow poweroff

#16 2020-04-27 09:12:41

Re: dhcpcd@.service causes slow poweroff

#17 2020-05-02 17:19:18

Re: dhcpcd@.service causes slow poweroff

#18 2020-05-03 05:02:27

Re: dhcpcd@.service causes slow poweroff

#19 2020-05-05 16:53:15

Re: dhcpcd@.service causes slow poweroff

#20 2020-05-15 06:03:20

Re: dhcpcd@.service causes slow poweroff

#21 2020-05-15 06:31:32

Re: dhcpcd@.service causes slow poweroff

#22 2020-05-16 03:19:16

Re: dhcpcd@.service causes slow poweroff

#23 2020-05-16 07:45:11

Re: dhcpcd@.service causes slow poweroff

#24 2020-05-22 15:38:33

Re: dhcpcd@.service causes slow poweroff

#25 2020-05-23 09:14:30

Re: dhcpcd@.service causes slow poweroff

Board footer