You are not logged in.

Pages: 1

#1 2018-04-29 11:07:00

stefan
Member
Registered: 2013-03-22
Posts: 104

dhcpcd fails with coredump

Hi,

my dhcpcd usually fails during boot.  The journal will always contain lines like these:

Apr 29 10:40:15 second systemd[1]: Starting dhcpcd on all interfaces...
Apr 29 10:40:15 second dhcpcd[296]: dev: loaded udev
Apr 29 10:40:15 second dhcpcd[296]: forked to background, child pid 319
Apr 29 10:40:15 second systemd[1]: Started dhcpcd on all interfaces.
Apr 29 10:40:15 second dhcpcd[319]: enp0s3: waiting for carrier
Apr 29 10:40:15 second dhcpcd[319]: enp0s8: waiting for carrier
Apr 29 10:40:15 second dhcpcd[319]: enp0s8: carrier acquired
Apr 29 10:40:15 second dhcpcd[319]: DUID 00:01:00:01:22:78:5d:8f:08:00:27:5b:ce:13
Apr 29 10:40:15 second dhcpcd[319]: enp0s8: IAID 27:5b:ce:13
Apr 29 10:40:15 second dhcpcd[319]: enp0s8: adding address fe80::815:fc90:9b21:c43f
Apr 29 10:40:15 second dhcpcd[319]: enp0s8: carrier lost
Apr 29 10:40:15 second dhcpcd[319]: enp0s8: deleting address fe80::815:fc90:9b21:c43f
Apr 29 10:40:18 second dhcpcd[319]: enp0s8: carrier acquired
Apr 29 10:40:18 second dhcpcd[319]: enp0s8: IAID 27:5b:ce:13
Apr 29 10:40:18 second dhcpcd[319]: enp0s8: adding address fe80::815:fc90:9b21:c43f
Apr 29 10:40:18 second dhcpcd[319]: enp0s3: carrier acquired
Apr 29 10:40:18 second dhcpcd[319]: enp0s3: IAID 27:ff:10:83
Apr 29 10:40:18 second dhcpcd[319]: enp0s3: adding address fe80::c8f9:1fc:33fc:995f
Apr 29 10:40:18 second dhcpcd[319]: enp0s3: soliciting a DHCP lease
Apr 29 10:40:18 second dhcpcd[319]: enp0s8: soliciting a DHCP lease
Apr 29 10:40:18 second dhcpcd[319]: enp0s8: soliciting an IPv6 router
Apr 29 10:40:18 second dhcpcd[319]: enp0s8: offered 192.168.56.101 from 192.168.56.100
Apr 29 10:40:18 second dhcpcd[319]: enp0s8: probing address 192.168.56.101/24
Apr 29 10:40:19 second dhcpcd[319]: enp0s3: soliciting an IPv6 router
Apr 29 10:40:19 second dhcpcd[319]: enp0s3: Router Advertisement from fe80::2665:11ff:fe29:1162
Apr 29 10:40:19 second dhcpcd[319]: enp0s3: adding address 2a02:8071:8290:7100:158d:8a7a:a402:686b/64
Apr 29 10:40:19 second dhcpcd[319]: enp0s3: adding route to 2a02:8071:8290:7100::/64
Apr 29 10:40:19 second dhcpcd[319]: enp0s3: adding default route via fe80::2665:11ff:fe29:1162
Apr 29 10:40:19 second dhcpcd[319]: enp0s3: soliciting a DHCPv6 lease
Apr 29 10:40:19 second dhcpcd[319]: enp0s3: offered 192.168.0.75 from 192.168.0.1
Apr 29 10:40:19 second dhcpcd[319]: enp0s3: probing address 192.168.0.75/24
Apr 29 10:40:20 second dhcpcd[319]: enp0s3: DHCPv6 REPLY: in stateless mode
Apr 29 10:40:22 second systemd[1]: dhcpcd.service: Main process exited, code=dumped, status=6/ABRT
Apr 29 10:40:22 second systemd[1]: dhcpcd.service: Failed with result 'core-dump'.
Apr 29 10:40:22 second systemd-coredump[386]: Process 319 (dhcpcd) of user 0 dumped core.
                                              #9  0x000055f433e92071 logerrx (dhcpcd)
                                              #10 0x000055f433eb1d0c dhcp6_checkstatusok (dhcpcd)
                                              #11 0x000055f433eb2a28 dhcp6_validatelease (dhcpcd)
                                              #12 0x000055f433eb6628 dhcp6_recvif (dhcpcd)
                                              #13 0x000055f433eb6e9e dhcp6_recv (dhcpcd)
                                              #14 0x000055f433e9166b eloop_start (dhcpcd)
                                              #15 0x000055f433e8c175 main (dhcpcd)
                                              #17 0x000055f433e8c74a _start (dhcpcd)

But I can always successfully start dhcpcd manually:

# systemctl start dhcpcd

Then dhcpcd runs, networkbecomes available, although I continue to see entries like

Apr 29 10:41:19 second dhcpcd[419]: enp0s3: DHCPv6 REPLY: in stateless mode

in the journal.

Any suggestions what to look for?

I can reproduce this problem on my notebook, and on a VirtualBox freshly installed.

Offline

#2 2018-04-29 16:41:09

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,772

Re: dhcpcd fails with coredump

What are the output of ip link and of find /etc/systemd

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2018-04-29 16:51:15

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: dhcpcd fails with coredump

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:ff:10:83 brd ff:ff:ff:ff:ff:ff
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 08:00:27:5b:ce:13 brd ff:ff:ff:ff:ff:ff
# find /etc/systemd
/etc/systemd
/etc/systemd/network
/etc/systemd/user
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/dirmngr.socket
/etc/systemd/user/sockets.target.wants/gpg-agent.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-browser.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-extra.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-ssh.socket
/etc/systemd/system
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/dhcpcd.service
/etc/systemd/system/multi-user.target.wants/sshd.service
/etc/systemd/timesyncd.conf
/etc/systemd/resolved.conf
/etc/systemd/coredump.conf
/etc/systemd/journal-remote.conf
/etc/systemd/journal-upload.conf
/etc/systemd/user.conf
/etc/systemd/system.conf
/etc/systemd/logind.conf
/etc/systemd/journald.conf

Offline

#4 2018-04-30 11:12:01

tedd
Member
Registered: 2013-02-21
Posts: 26

Re: dhcpcd fails with coredump

I am also having this issue. I've tried 7.0.2-1 and 7.0.1-1. Both segfault on boot but run fine when manually started again after login.
Last working version is 6.11.5-1 for me.

Output of journal:

Apr 30 21:30:24 winslow dhcpcd[388]: enp0s3: carrier acquired
Apr 30 21:30:24 winslow kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Apr 30 21:30:24 winslow kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready
Apr 30 21:30:24 winslow dhcpcd[388]: DUID 00:01:00:01:22:21:5e:24:08:00:27:84:1a:c9
Apr 30 21:30:24 winslow dhcpcd[388]: enp0s3: IAID 27:84:1a:c9
Apr 30 21:30:24 winslow dhcpcd[388]: enp0s3: adding address fe80::f3e4:5ebd:7b6d:8059
Apr 30 21:30:25 winslow dhcpcd[388]: enp0s3: soliciting an IPv6 router
Apr 30 21:30:25 winslow dhcpcd[388]: enp0s3: rebinding lease of 10.0.1.166
Apr 30 21:30:25 winslow dhcpcd[388]: enp0s3: probing address 10.0.1.166/16
Apr 30 21:30:26 winslow dhcpcd[388]: enp0s3: Router Advertisement from fe80::fa32:e4ff:fe4f:95f0
Apr 30 21:30:26 winslow dhcpcd[388]: enp0s3: adding address 2001:44b8:2118:1100:7a9f:255b:c6e4:cde2/64
Apr 30 21:30:26 winslow dhcpcd[388]: enp0s3: adding route to 2001:44b8:2118:1100::/64
Apr 30 21:30:26 winslow dhcpcd[388]: enp0s3: adding default route via fe80::fa32:e4ff:fe4f:95f0
Apr 30 21:30:26 winslow dhcpcd[388]: enp0s3: soliciting a DHCPv6 lease
Apr 30 21:30:26 winslow dhcpcd[388]: enp0s3: DHCPv6 REPLY: no addresses available
Apr 30 21:30:26 winslow dhcpcd[388]: enp0s3: DHCPv6 REPLY: no addresses available
Apr 30 21:30:27 winslow kernel: dhcpcd[388]: segfault at aaec6beb70 ip 000055aaea9b5617 sp 00007ffdfadfac80 error 6 in dhcpcd[55aaea98d000+46000]
Apr 30 21:30:27 winslow systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Apr 30 21:30:27 winslow systemd[1]: Started Process Core Dump (PID 405/UID 0).
Apr 30 21:30:27 winslow systemd[1]: dhcpcd@enp0s3.service: Control process exited, code=dumped status=11
Apr 30 21:30:27 winslow systemd[1]: dhcpcd@enp0s3.service: Failed with result 'core-dump'.
Apr 30 21:30:27 winslow systemd[1]: Failed to start dhcpcd on enp0s3.
Apr 30 21:30:27 winslow systemd[1]: Reached target Network.
Apr 30 21:30:27 winslow systemd[1]: Started OpenSSH Daemon.
Apr 30 21:30:27 winslow systemd[1]: Starting Permit User Sessions...
Apr 30 21:30:27 winslow systemd[1]: Started Permit User Sessions.
Apr 30 21:30:27 winslow systemd[1]: Started Simple Desktop Display Manager.
Apr 30 21:30:27 winslow systemd-coredump[406]: Process 388 (dhcpcd) of user 0 dumped core.
                                               
                                               Stack trace of thread 388:
                                               #0  0x000055aaea9b5617 ipv6_handleifa (dhcpcd)
                                               #1  0x000055aaea9a6eda link_netlink (dhcpcd)
                                               #2  0x000055aaea9a6a22 get_netlink (dhcpcd)
                                               #3  0x000055aaea99704a dhcpcd_handlelink (dhcpcd)
                                               #4  0x000055aaea9988bb eloop_start (dhcpcd)
                                               #5  0x000055aaea993175 main (dhcpcd)
                                               #6  0x00007ff47078e9a7 __libc_start_main (libc.so.6)
                                               #7  0x000055aaea99374a _start (dhcpcd)

Offline

#5 2018-05-02 15:40:46

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: dhcpcd fails with coredump

This may be related to a fixed known bug [1].  The version 7.0.1 in the ArchLinux repo is outdated (and flagged).

I have installed 7.0.2 from the testing repo, which did not solve the problem, and also 7.0.3 from the upstream git repo [2].  The latter solved the problem.

__________
[1] https://roy.marples.name/archives/dhcpc … 02007.html
[2] https://roy.marples.name/git/dhcpcd.git/

Offline

#6 2018-05-03 11:22:23

stefan
Member
Registered: 2013-03-22
Posts: 104

Re: dhcpcd fails with coredump

This seems to be fixed with dhcpcd 7.0.4 available from [testing].  I still get come lines like

May 03 09:02:57 second dhcpcd[321]: enp0s3: DHCPv6 REPLY: in stateless mode

in the journal, but thats probably my bad configuation (help appreciated).

Offline

#7 2018-05-11 09:54:11

infides
Member
Registered: 2018-05-11
Posts: 1

Re: dhcpcd fails with coredump

I am still having segfaults with dhcpcd 7.0.4 at boot and also later on:

[   96.358414] dhcpcd[448]: segfault at 8 ip 000055db28419cbb sp 00007ffd9c4d0258 error 4 in dhcpcd[55db2840e000+4a000]
[  221.809755] dhcpcd[4856]: segfault at 8 ip 00005578d9932cbb sp 00007ffdf19efd28 error 4 in dhcpcd[5578d9927000+4a000]
[  325.038267] dhcpcd[6797]: segfault at 8 ip 000056216d97ccbb sp 00007ffc1a0086e8 error 4 in dhcpcd[56216d971000+4a000]

Here is the coredump:

systemd-coredump[7990]: Process 6797 (dhcpcd) of user 0 dumped core.
                                                   
                                                   Stack trace of thread 6797:
                                                   #0  0x000056216d97ccbb warn_iaid_conflict (dhcpcd)
                                                   #1  0x000056216d97e076 dhcpcd_startinterface (dhcpcd)
                                                   #2  0x000056216d98061f eloop_start (dhcpcd)
                                                   #3  0x000056216d97aebd main (dhcpcd)
                                                   #4  0x00007fc9e61cc06b __libc_start_main (libc.so.6)
                                                   #5  0x000056216d97b48a _start (dhcpcd)

Offline

Pages: 1

Board footer

Powered by FluxBB