Red Hat Bugzilla – Bug 1016160
[abrt] dhclient-4.2.5-15.fc19: isc_error_fatal: Process /usr/sbin/dhclient was killed by signal 6 (SIGABRT)
Last modified: 2015-02-18 06:34:03 EST
Description of problem:
I know this is a use-case which will bother our grandchildren but anyway... dhclient should not crash in year 2149.
How to reproduce:
Set your system date to (unsigned int) -1 (which is about Feb 7 2106), then start ntpdate, which will shift the date even further to the year 2149. At this point, dhclient just bails and crashes.
Version-Release number of selected component:
cmdline: /sbin/dhclient -d -sf /usr/libexec/nm-dhcp-client.action -pf /var/run/dhclient-em1.pid -lf /var/lib/NetworkManager/dhclient-7ac05975-799c-4cf2-9798-e69c991e3d75-em1.lease -cf /var/lib/NetworkManager/dhclient-em1.conf em1
runlevel: N 5
Thread no. 1 (5 frames)
#2 isc_error_fatal at ../../../lib/isc/error.c:76
#3 isc_error_runtimecheck at ../../../lib/isc/error.c:81
#4 evloop at ../../../../lib/isc/unix/app.c:465
#5 isc__app_ctxrun at ../../../../lib/isc/unix/app.c:696
Created attachment 808920 [details]
Created attachment 808921 [details]
Created attachment 808922 [details]
Created attachment 808923 [details]
Created attachment 808924 [details]
Created attachment 808925 [details]
Created attachment 808926 [details]
Created attachment 808928 [details]
Created attachment 808929 [details]
Created attachment 808930 [details]
Thanks, I'll take a look. It crashes somewhere in libisc, so I guess it'd be something similar to bug #789601 and bug #662254.
Other similar bug AFAIR was bug #631521.
I have problems reproducing this bug.
I run dhclient in terminal, then in other terminal set the time to 4294967295, but nothing crashes.
What do you mean by "then start ntpdate, which will shift the date even further to the year 2149"? When I run ntpdate, it just prints: "7 Feb 01:28:56 ntpdate: no servers can be used, exiting". How is ntpdate supposed to shift the time to year 2149?
Anyway, I have idea where the program may crash.
It's in isc library (which is a part of bind package), in file time.c there is function isc_time_now(). This function probably returns error status, leading to abort() being called consequently.
However I cannot be 100% sure when I don't have full application output.
Well, all the actions I described were done through the KDE system settings, so I didn't run the commands directly. But the offending ntpdate can be run like this for example:
[0|root@mbriza-laptop ~]# date
Sun Feb 7 07:28:56 CET 2106
[0|root@mbriza-laptop ~]# ntpdate clock.redhat.com
4 Jan 22:11:19 ntpdate: step time server 10.11.160.238 offset 1385649719.550704 sec
[0|root@mbriza-laptop ~]# date
Sun Jan 4 22:11:21 CET 2150
Thanks, I managed to shift the date to 2050 with ntpdate, but it still doesn't crash for me.
Maybe I'm doing it wrong.
I run the command "/sbin/dhclient -d -sf /usr/libexec..." from the report in one terminal and in second terminal I am changing the time.
As I was looking into the code, it seems that dhclient prints some error messages into stderr. I need to have the stderr output. If you can reproduce it, can you give it me?
Yes, it didn't crash for me either this time. I'll try once more on a machine where I don't mind messing settings and certificates up.
So, it still crashes, there are a few problems right now though:
1) I don't know how to retrieve the stderr output before the crash (nor I do know when exactly it crashes and how is dhclient even run at the moment, possibly by NM?)
2) I can't access the network to upload the journal at least
3) I tried rebooting just out of curiosity and the computer doesn't boot at all. :)
Anyway, tested on a fairly clean physical Fedora 20 KDE machine.
Created attachment 831599 [details]
Attaching journalctl -b | grep dhclient
Finally booted, reported via abrt again as Bug 1036717 for F20.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.