Description of problem: `dhclient` crashed and core dumped on boot Version-Release number of selected component (if applicable): $ uname -r; rpm -q dhcp-client 3.18.7-200.fc21.x86_64+debug dhcp-client-4.3.2-0.1b1.fc22.x86_64 How reproducible: At-least twice Steps to Reproduce: 1. Just boot the OS with the above said Kernel, and you should notice the stack trace in `journalctl` Actual results: ------------------------------------------------------------------------------- $ journalctl --since=today | grep -i "dumped core" -A20 -B5 Feb 20 13:45:46 dell-per910-02.khw.lab.eng.bos.redhat.com dhclient[1939]: DHCPACK from 10.16.187.253 (xid=0x1ce07a6d) Feb 20 13:45:48 dell-per910-02.khw.lab.eng.bos.redhat.com NET[2006]: /usr/sbin/dhclient-script : updated /etc/resolv.conf Feb 20 13:45:48 dell-per910-02.khw.lab.eng.bos.redhat.com dhclient[1939]: bound to 10.16.187.44 -- renewal in 36156 seconds. Feb 20 13:45:54 dell-per910-02.khw.lab.eng.bos.redhat.com chronyd[1230]: Selected source 10.5.26.10 Feb 20 13:45:54 dell-per910-02.khw.lab.eng.bos.redhat.com kernel: Adjusting tsc more than 11% (4729269 vs 4667347) Feb 20 13:45:55 dell-per910-02.khw.lab.eng.bos.redhat.com systemd-coredump[2062]: Process 1939 (dhclient) of user 0 dumped core. Stack trace of thread 1941: #0 0x00007f1878c9e8c7 raise (libc.so.6) #1 0x00007f1878ca052a abort (libc.so.6) #2 0x00007f187949ec6f isc_assertion_failed (libisc.so.148) #3 0x00007f18794d7e22 watcher (libisc.so.148) #4 0x00007f187885052a start_thread (libpthread.so.0) #5 0x00007f1878d6a79d __clone (libc.so.6) Stack trace of thread 1942: #0 0x00007f1878855939 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f18794dfaf8 isc_condition_waituntil (libisc.so.148) #2 0x00007f18794c7d0b run (libisc.so.148) #3 0x00007f187885052a start_thread (libpthread.so.0) #4 0x00007f1878d6a79d __clone (libc.so.6) Stack trace of thread 1940: #0 0x00007f187a35e3c6 n/a (n/a) Feb 20 13:45:55 dell-per910-02.khw.lab.eng.bos.redhat.com chronyd[1230]: Selected source 10.16.187.254 Feb 20 13:46:03 dell-per910-02.khw.lab.eng.bos.redhat.com systemd[1]: Started Wait for chrony to synchronize system clock. ------------------------------------------------------------------------------- Expected results: dhclient should not crash.
Andrea Arcangeli mentioned that it was fixed for him in latest upstream Kernels. I just booted into this Kernel version 3.20.0-0.rc0.git9.1.fc23.x86_64 and don't see the crash in `journalctl` logs, but still `dhclient` is not running on boot.
Spoke too soon, when I manually invoked `dhclient` (with 3.20.0-0.rc0.git9.1.fc23.x86_64), I notice it again core dumping: [ 359.932029] dhclient[2180]: segfault at ffffffffffffff9c ip 00007fb6c0644c15 sp 00007fb6bb2c9480 error 5 in libc-2.20.so[7fb6c05fb000+1b4000] Segmentation fault (core dumped) Traceback --------- $ journalctl --since=today | grep "dumped core" -A20 Feb 20 14:31:43 dell-per910-02.khw.lab.eng.bos.redhat.com systemd-coredump[2426]: Process 2179 (dhclient) of user 0 dumped core. Stack trace of thread 2180: #0 0x00007fb6c0644c15 _IO_vfprintf_internal (libc.so.6) #1 0x00007fb6c070abc6 ___vsnprintf_chk (libc.so.6) #2 0x00007fb6c1acf305 log_error (libomapi.so.0) #3 0x00007fb6c1f2ac08 got_one.part.1 (dhclient) #4 0x00007fb6c1ad049e omapi_iscsock_cb (libomapi.so.0) #5 0x00007fb6c0e6761f internal_fdwatch_read (libisc.so.148) #6 0x00007fb6c0e53aaf dispatch (libisc.so.148) #7 0x00007fb6c01e152a start_thread (libpthread.so.0) #8 0x00007fb6c06fb79d __clone (libc.so.6) Stack trace of thread 2181: #0 0x00007fb6c06fbda3 epoll_wait (libc.so.6) #1 0x00007fb6c0e67fee watcher (libisc.so.148) #2 0x00007fb6c01e152a start_thread (libpthread.so.0) #3 0x00007fb6c06fb79d __clone (libc.so.6) Stack trace of thread 2179: #0 0x00007fb6c01e6590 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.