Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 149135 - ntpd startup fails on boot
Summary: ntpd startup fails on boot
Status: CLOSED DUPLICATE of bug 154759
Alias: None
Product: Fedora
Classification: Fedora
Component: ntp
Version: 3
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Jiri Ryska
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-19 01:36 UTC by JCC
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-06-12 15:16:54 UTC

Attachments (Terms of Use)

Description JCC 2005-02-19 01:36:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Description of problem:
On boot up of FC3, the ntpd startup fails.  After boot up is complete, from a terminal window, as root type: /etc/rc.d/init.d/ntpd restart, and ntp starts successfully.

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

How reproducible:

Steps to Reproduce:
1. Cold boot FC3

Actual Results:  ntpd fails to start with the following message:

ntpd: Synchronizing with time server:      [failed]

Expected Results:  ntpd: Synchronizing with time server:                      [  OK  ]

Additional info:

Comment 1 Davide Bolcioni 2005-06-03 17:56:05 UTC
I attempted a strace: ntp-4.2.0.a.20040617-4 uncerimoniously segfaults:

8042  rt_sigaction(SIGSYS, {0x8c53a0, [], SA_RESTORER, 0x2f48c8}, {SIG_DFL}, 8) = 0
8042  rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
8042  adjtimex({modes=61, offset=0, freq=0, maxerror=16, esterror=16, status=64,
constant=0, precision=1, tolerance=33554432, time={1117821155, 463315}}) = 5
8042  rt_sigaction(SIGSYS, {SIG_DFL}, NULL, 8) = 0
8042  --- SIGSEGV (Segmentation fault) @ 0 (0) ---

Comment 2 Frank Ch. Eigler 2005-06-12 15:16:54 UTC

*** This bug has been marked as a duplicate of 154759 ***

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