Bug 387831

Summary:	NTP Locks on boot if ethernet cable is disconnected
Product:	[Fedora] Fedora	Reporter:	Rafael Vila <rafivila>
Component:	ntp	Assignee:	Miroslav Lichvar <mlichvar>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	7
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-04-25 04:50:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rafael Vila 2007-11-16 22:49:53 UTC

Description of problem: Upon boot, NTPD locks up if the ethernet adapter is not 
active (cable not connected).  Eth0 and Wlan initialize however NTPD will not 
rely on the wireless connection for synchronization and the process will hang.


Version-Release number of selected component (if applicable): 2.6.22.9-91.fc7


How reproducible: 100%


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Rafael Vila 2007-11-16 23:02:07 UTC

I forgot to fill out the steps to reproduce; 1. Disconnect ethernet cable from 
the computer, 2. Start the system, 3. The system will not boot if the NTPD 
service is requested upon start-up

Actual results: System will not boot; hangs on NTPD

Expected results: Either synchronize from the wireless adapter or generate fail 
to sync message and continue boot process

Additional info: NVidia MCP55 Ethernet adapter on ASUS P5GD2 Delux

Comment 2 Miroslav Lichvar 2007-11-19 11:03:05 UTC

Is "Synchronizing with time server:" the last printed message when it's locked?

If yes, you need to remove servers from /etc/ntp/step-tickers, or disable
"Synchronize system clock before starting service" in advanced options in
system-config-date.

Comment 3 Brian Powell 2008-04-25 04:50:18 UTC

The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.

Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.