Bug 875798 - NTP service crashed after stopping network service
NTP service crashed after stopping network service
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ntp (Show other bugs)
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Miroslav Lichvar
Petr Sklenar
Depends On:
Blocks: ovirt-3.2-release 895654
  Show dependency treegraph
Reported: 2012-11-12 10:30 EST by Igor Lvovsky
Modified: 2014-04-28 11:18 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 06:04:45 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
fix IPv6 only interface iteration (3.56 KB, patch)
2012-11-27 11:57 EST, Miroslav Lichvar
no flags Details | Diff

  None (edit)
Description Igor Lvovsky 2012-11-12 10:30:41 EST
Description of problem:

The NTP service crashed after stopping network service

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run ntpd and network services
2. stop network service
3. ntpd is die
Actual results:

Expected results:

Additional info:

NTP doesn't run after the network start again.
Comment 2 Miroslav Lichvar 2012-11-12 11:32:36 EST
Can you please provide some logs when the network is restarted?
Comment 3 Igor Lvovsky 2012-11-12 11:52:55 EST
there is no ntpd related logs in /var/log/messages.

When I added PEERNTP=no to /etc/sysconfig/network the ntpd stayed alive after network restart
Comment 4 Igor Lvovsky 2012-11-12 12:11:33 EST
You can reproduce it easly with:
service network stop; sleep 10; service network start
Comment 5 Miroslav Lichvar 2012-11-12 13:27:38 EST
From further discussion with the reporter it seems it happens when the network is stopped and after 10 seconds started again. "service network restart" doesn't trigger the bug. The latest ntp from f18 doesn't crash. There are 6 network interfaces configured on the machine and ntpd is not restarted by dhclient.


#0  0x00007ffff6fc78a5 in raise () from /lib64/libc.so.6
#1  0x00007ffff6fc9085 in abort () from /lib64/libc.so.6
#2  0x00007ffff7fe121e in default_callback (file=0x7ffff7ff34d3 "./../libisc/ifiter_ioctl.c", line=571, 
    type=<value optimized out>, cond=0x7ffff7ff35e0 "iter->pos < (unsigned int) iter->ifc.ifc_len")
    at ../libisc/assertions.c:91
#3  0x00007ffff7fdf36e in internal_current4 (iter=0x7ffff826b1a0) at ../libisc/ifiter_ioctl.c:571
#4  0x00007ffff7fdfbbc in internal_current (iter=0x7ffff826b1a0) at ../libisc/ifiter_ioctl.c:994
#5  isc_interfaceiter_first (iter=0x7ffff826b1a0) at ../libisc/interfaceiter.c:175
#6  0x00007ffff7f8d4a4 in update_interfaces (receiver=0, data=0x0, port=31488) at ntp_io.c:1281
#7  0x00007ffff7f8e715 in interface_update (receiver=<value optimized out>, data=<value optimized out>) at ntp_io.c:1119
#8  0x00007ffff7fac3e7 in timer () at ntp_timer.c:394
#9  0x00007ffff7f8f263 in ntpdmain (argc=<value optimized out>, argv=<value optimized out>) at ntpd.c:1098
#10 0x00007ffff6fb3cdd in __libc_start_main () from /lib64/libc.so.6
#11 0x00007ffff7f85cc9 in _start ()
Comment 6 RHEL Product and Program Management 2012-11-13 06:39:50 EST
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 7 lpeer 2012-11-20 08:18:42 EST
NTP not functioning can cause an issue with VM migration.
The guest can suffer from clock skew and then migration fails.
I think this bug is important enough to be fixed in 6.4 z stream.

Since I am not familiar with the details of the migration issue I am adding Barak to keep track of this bug and maybe provide more details.
Comment 8 Miroslav Lichvar 2012-11-27 11:54:11 EST
This crash happens when the system doesn't have any IPv4 addresses, but it has an IPv6 address. I think that is a rare situation, usually there is at least configured on the loopback interface which is the first interface brought up by the network service.
Comment 9 Miroslav Lichvar 2012-11-27 11:57:28 EST
Created attachment 652925 [details]
fix IPv6 only interface iteration
Comment 10 Barak 2012-12-14 09:33:35 EST
(In reply to comment #7)
> Since I am not familiar with the details of the migration issue I am adding
> Barak to keep track of this bug and maybe provide more details.

migration of a VM back in time will cause the vm to stack.
I don't think it's relevant to the bug.
What is important is that the ntp should not crash
Comment 20 errata-xmlrpc 2013-02-21 06:04:45 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.