Bug 1194809
Summary: | `dhclient` crashes on boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kashyap Chamarthy <kchamart> |
Component: | dhcp | Assignee: | Jiri Popelka <jpopelka> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 21 | CC: | aarcange, jpopelka, rkrcmar, thozza |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-02 09:17:47 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kashyap Chamarthy
2015-02-20 19:17:21 UTC
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. |