You are not logged in.

#1 2016-04-09 00:20:01

tuvistavie
Member
From: London
Registered: 2012-02-12
Posts: 15
Website

dhclient core dump after upgrade

Hi,

I recently upgraded dhclient to 4.3.4-1 and since then, I get a coredump on the
first connection attempt, when connecting to wifi using NetworkManager.
If I disconnect from the network I am trying to connect to, and reconnect
dhclient seems to work properly.

Here is the log info from journalctl.

Process 4297 (dhclient) of user 0 dumped core.
Stack trace of thread 4297:
#0  0x00007f4b722b32a8 raise (libc.so.6)
#1  0x00007f4b722b472a abort (libc.so.6)
#2  0x00007f4b722ef369 __libc_message (libc.so.6)
#3  0x00007f4b72378017 __fortify_fail (libc.so.6)
#4  0x00007f4b723761d0 __chk_fail (libc.so.6)
#5  0x00007f4b72375522 __strcpy_chk (libc.so.6)
#6  0x00000000004240ea n/a (dhclient)
#7  0x000000000040793f n/a (dhclient)
#8  0x00007f4b722a0710 __libc_start_main (libc.so.6)
#9  0x0000000000408819 n/a (dhclient)

Here are some information about my system.

$ uname -a
Linux leffe 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 x86_64 GNU/Linux
$ pacman -Qs dhclient | sed -e '/^ /d'
local/dhclient 4.3.4-1
$ pacman -Qs networkmanager  | sed -e '/^ /d'
local/libnm-glib 1.0.12-1
local/networkmanager 1.0.12-1
local/nm-connection-editor 1.0.10-1
$ lspci | grep -i net
02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24

Did I miss something while upgrading?

Please let me know if you need any other information.

Thank you,

Daniel

Last edited by tuvistavie (2016-04-09 00:21:20)

Offline

#2 2016-04-16 16:27:41

jono
Member
Registered: 2012-01-03
Posts: 13

Re: dhclient core dump after upgrade

I am having the exact same problem after my upgrade. Same version of dhclient. So I tried downgrading to an older dhclient, but it did not help.
I wonder if there is something going on with libc as is mentioned in the core dump.

I know it is not my thinkpad that is the problem. Because I can start from a boot disk and networking works fine.

Offline

#3 2016-04-16 20:54:24

anatolik
Developer
Registered: 2012-09-27
Posts: 458

Re: dhclient core dump after upgrade

Way to debug the problem:

1) Check with upstream if it is a known problem. If not then
2) Recompile dhclient with debug symbols enabled and binaries not stripped
3) Run dhclient with gdb. Once it crashes print the stacktrace and stack variable values. Either read the code and try to fix it or send the crash information upstream.


Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster

Offline

#4 2016-04-26 14:59:16

jono
Member
Registered: 2012-01-03
Posts: 13

Re: dhclient core dump after upgrade

Thanks anatolik. I spent an hour or so trying to pull the dependencies so I could build the package, but kept running into checksum errors.

Hate to be that guy, but I ended up reinstalling the whole system. Now dhcp and wifi work.

Offline

#5 2016-05-25 09:09:32

Carceri
Member
Registered: 2016-03-08
Posts: 3

Re: dhclient core dump after upgrade

I had the exact same problem.

I downloaded the sources and built dhclient with debug information to try and figure out what was wrong, but now it works fine.

If I go back to the original version in the repositories it crashes, but the exact same version I compiled with debug information runs fine.

Offline

#6 2016-08-08 15:45:10

nebulon
Member
Registered: 2016-08-08
Posts: 1

Re: dhclient core dump after upgrade

I also have the very same issue. This seems happened after updating those packages, according to pacman.log

[2016-08-07 18:29] [ALPM] upgraded binutils (2.26.1-1 -> 2.26.1-2)
[2016-08-07 18:29] [ALPM] upgraded gcc-libs (6.1.1-3 -> 6.1.1-4)
[2016-08-07 18:29] [ALPM] upgraded libcups (2.1.4-1 -> 2.1.4-2)
[2016-08-07 18:29] [ALPM] upgraded fontconfig (2.12.0-1 -> 2.12.1-3)
[2016-08-07 18:29] [ALPM-SCRIPTLET] updating font cache... done.
[2016-08-07 18:29] [ALPM] upgraded imagemagick (6.9.5.3-1 -> 6.9.5.4-1)
[2016-08-07 18:29] [ALPM] upgraded mesa (12.0.1-5 -> 12.0.1-7)
[2016-08-07 18:29] [ALPM] upgraded mesa-libgl (12.0.1-5 -> 12.0.1-7)
[2016-08-07 18:29] [ALPM] upgraded poppler (0.46.0-1 -> 0.46.0-2)
[2016-08-07 18:29] [ALPM] upgraded cups (2.1.4-1 -> 2.1.4-2)
[2016-08-07 18:29] [ALPM] upgraded curl (7.50.0-1 -> 7.50.1-1)
[2016-08-07 18:29] [ALPM] upgraded fakeroot (1.21-1 -> 1.21-2)
[2016-08-07 18:29] [ALPM] upgraded fftw (3.3.4-2 -> 3.3.5-1)
[2016-08-07 18:29] [ALPM] upgraded firefox (48.0-1 -> 48.0-2)
[2016-08-07 18:30] [ALPM] upgraded gcc (6.1.1-3 -> 6.1.1-4)
[2016-08-07 18:30] [ALPM] upgraded lib32-glibc (2.23-5 -> 2.24-1)
[2016-08-07 18:30] [ALPM] upgraded lib32-gcc-libs (6.1.1-3 -> 6.1.1-4)


Maybe it just needs a rebuild against the updated glibc?

Offline

#7 2016-08-10 09:05:53

tebeka
Member
Registered: 2016-08-02
Posts: 2

Re: dhclient core dump after upgrade

I'm experiencing the same issue (same version of dhclient). Should we file a bug at https://bugs.archlinux.org/?project=1&c … g=dhclient?

FWIW my solution was to compile dhclient from sources (./configure && make) and then copy over code/dhclient to /usr/bin.

Last edited by tebeka (2016-08-10 10:28:35)

Offline

#8 2016-08-10 18:42:59

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: dhclient core dump after upgrade

@tebeka: Use ABS to compile. Doing it your way can sometimes screw up package management. (I'm not saying WILL but MAY.)


Matt

"It is very difficult to educate the educated."

Offline

#9 2016-08-12 04:41:58

tebeka
Member
Registered: 2016-08-02
Posts: 2

Re: dhclient core dump after upgrade

Thanks @mrunion, will give abs a try (learning new things every day)

Offline

#10 2016-08-16 21:17:19

marcov
Member
Registered: 2014-06-04
Posts: 3

Re: dhclient core dump after upgrade

Hi, I'm having the same issue but with dhclient 4.3.4-2.

Strangely it seems to happen intermittently: usually when I try to reconnect, it will establish a connection after several tries.

I'm seeing the following appear in the logs:

Aug 16 10:54:10 schrodinger NetworkManager[1173]: <info>  [1471341250.4676] dhcp4 (wlp3s0): dhclient started with pid 2720
Aug 16 10:54:10 schrodinger systemd[1]: Started Process Core Dump (PID 2721/UID 0).
Aug 16 10:54:10 schrodinger NetworkManager[1173]: <info>  [1471341250.4919] dhcp4 (wlp3s0): client pid 2720 killed by signal 6
Aug 16 10:54:10 schrodinger NetworkManager[1173]: <info>  [1471341250.4919] dhcp4 (wlp3s0): state changed unknown -> fail
Aug 16 10:54:10 schrodinger NetworkManager[1173]: <info>  [1471341250.4920] dhcp4 (wlp3s0): canceled DHCP transaction
Aug 16 10:54:10 schrodinger NetworkManager[1173]: <info>  [1471341250.4920] dhcp4 (wlp3s0): state changed fail -> done
Aug 16 10:54:10 schrodinger systemd-coredump[2722]: Process 2720 (dhclient) of user 0 dumped core.
                                                    
                                                    Stack trace of thread 2720:
                                                    #0  0x00007f6208c1104f raise (libc.so.6)
                                                    #1  0x00007f6208c1247a abort (libc.so.6)
                                                    #2  0x00007f6208c4ec50 __libc_message (libc.so.6)
                                                    #3  0x00007f6208cd6f17 __fortify_fail (libc.so.6)
                                                    #4  0x00007f6208cd5050 __chk_fail (libc.so.6)
                                                    #5  0x00007f6208cd43b2 __strcpy_chk (libc.so.6)
                                                    #6  0x000000000042418a n/a (dhclient)
                                                    #7  0x000000000040793f n/a (dhclient)
                                                    #8  0x00007f6208bfe291 __libc_start_main (libc.so.6)
                                                    #9  0x0000000000408819 n/a (dhclient)

My system info:

$ archey

               +                
               #                
              ###               
             #####              
             ######             
            ; #####;            User: marco
           +##.#####            Hostname: schrodinger
          +##########           Distro: Arch Linux
         #############;         Kernel: 4.7.0-1-ARCH
        ###############+        Uptime: 11:21
       #######   #######        Window Manager: i3
     .######;     ;###;`".      Desktop Environment: 
    .#######;     ;#####.       Shell: /bin/zsh
    #########.   .########`     Terminal: xterm
   ######'           '######    Packages: 1200
  ;####                 ####;   CPU: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
  ##'                     '##   RAM: 3578 MB / 19984 MB 
 #'                         `#  Disk: 194GB / 488GB

------------------------------------------------------------

Offline

#11 2016-08-17 09:58:28

crepererum
Member
Registered: 2015-11-12
Posts: 4
Website

Re: dhclient core dump after upgrade

I see the exact same behaviour that @marcov is reporting. With some additions:

  • same stacktrace

  • also recovering after multiple tries

  • it does not seem to happen when I boot the system normally. It only seems to occur when waking up from sleep (to RAM, not to disk). Now someone might say that you more often do a sleep-wakeup compared to a full reboot. That's indeed true, but it feels that the issue is almost certain when doing a sleep-wakeup.

  • the network is a wireless connection

  • I use docker (not remembering where I've seen the post, but there were some hints that the bridge that docker creates might be an issue)

Offline

#12 2016-08-17 18:54:02

marcov
Member
Registered: 2014-06-04
Posts: 3

Re: dhclient core dump after upgrade

I can verify all the above that @crepererum mentioned on my system too. Including that I also use docker.

Offline

#13 2016-08-19 18:12:06

crepererum
Member
Registered: 2015-11-12
Posts: 4
Website

Re: dhclient core dump after upgrade

Status update: https://bugs.archlinux.org/task/48527 (see comments there).

Offline

#14 2016-09-10 20:53:36

Tidykoala
Member
Registered: 2015-07-05
Posts: 14

Re: dhclient core dump after upgrade

Hello,

Is there any news about the fix of dhclient for this issue?

I noticed that even though it still takes time to reconnect to Wifi, these days it seems to take less time and I don't have to shut off and on the Wifi. Maybe a little improvement.

Offline

#15 2016-10-11 06:31:07

rndstr
Member
Registered: 2011-03-20
Posts: 4

Re: dhclient core dump after upgrade

Here is another report of the very same behaviour

- same stacktrace (of core dump); in my logs that stacktrace goes back to Aug 20
- occurs when coming back from suspend, a reboot generally instantly fixes it
- fixed it once by shutting down the NetworkManager.service and doing it manually according to https://wiki.archlinux.org/index.php/Wi … nual_setup
- fixed it once (where it never recovered by itself) by stopping the broken openvpn connection
- I also use docker (stopping the docker.service did not help the last time I tried to fix it, though)

Offline

#16 2016-10-12 07:52:43

Tidykoala
Member
Registered: 2015-07-05
Posts: 14

Re: dhclient core dump after upgrade

It seems this issue has now been fixed in dhclient 4.3.5-1 which is now available. For the moment, I don't have the problem anymore.

Offline

Board footer

Powered by FluxBB