Ntp did not syncronize
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ntp (Ubuntu) |
Invalid
|
Low
|
Chuck Short | ||
Bug Description
ntp.conf
server ntp.certum.pl
server ntp1.oma.be
server time.ufe.cz
server ntp0.fau.de
server ntp1.nl.net
server ntp2.tp.pl
server ntp2.sp.se
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
driftfile /etc/ntp.drift
keys /etc/ntp.keys
trustedkey 1
requestkey 1
controlkey 1
Before starting ntp server i make sync:
#ntpdate ntp1.oma.be
7 Sep 15:13:56 ntpdate[14564]: step time server 193.190.230.65 offset -7.763787 sec
ntpdate ntp1.oma.be
7 Sep 15:13:56 ntpdate[14564]: step time server 193.190.230.65 offset -0.1335612 sec
20 minutes later
#ntpq -p
[spoiler] remote refid st t when poll reach delay offset jitter
=======
smtp.certum.pl .PPS. 1 u 6 64 1 76.104 -30259. 0.001
ntp1.oma.be .PPS. 1 u 5 64 1 60.152 -30322. 0.001
time.ure.cas.cz .ATOM. 1 u 4 64 1 55.508 -30391. 0.001
ntp0.rrze.uni-e .GPS. 1 u 3 64 1 58.721 -30458. 0.001
ntp1.nl.uu.net .PPS. 1 u 2 64 1 54.235 -30521. 0.001
ntp2.tp.pl .ATOM. 1 u 1 64 1 68.009 -30587. 0.001
ntp2.sp.se .PPS. 1 u 6 64 1 34.421 -30656. 0.001
LOCAL(0) .LOCL. 10 l 5 64 1 0.000 0.000 0.001
#grep ntpd /var/log/syslog
[spoiler]Sep 7 15:12:18 desktop ntpd[14303]: precision = 1.000 usec
Sep 7 15:12:18 desktop ntpd[14303]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Sep 7 15:12:18 desktop ntpd[14303]: Listening on interface #1 wildcard, ::#123 Disabled
Sep 7 15:12:18 desktop ntpd[14303]: Listening on interface #2 lo, ::1#123 Enabled
Sep 7 15:12:18 desktop ntpd[14303]: Listening on interface #3 eth0, fe80::21d:
Sep 7 15:12:18 desktop ntpd[14303]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
Sep 7 15:12:18 desktop ntpd[14303]: Listening on interface #5 eth0, 192.168.0.198#123 Enabled
Sep 7 15:12:18 desktop ntpd[14303]: Listening on interface #6 tun0, 192.168.25.10#123 Enabled
Sep 7 15:12:18 desktop ntpd[14303]: kernel time sync status 0040
#ntptime
ntp_gettime() returns code 5 (ERROR)
time ce4f7023.477e5000 Mon, Sep 7 2009 15:42:27.279, (.279271),
maximum error 69516 us, estimated error 16 us
ntp_adjtime() returns code 5 (ERROR)
modes 0x0 (),
offset 0.000 us, frequency 0.000 ppm, interval 1 s,
maximum error 69516 us, estimated error 16 us,
status 0x40 (UNSYNC),
time constant 4, precision 1.000 us, tolerance 500 ppm,
Few hours later
# ntptime
ntp_gettime() returns code 0 (OK)
time ce4f7abb.fa160000 Mon, Sep 7 2009 16:27:39.976, (.976898),
maximum error 13899 us, estimated error 0 us
ntp_adjtime() returns code 0 (OK)
modes 0x0 (),
offset 0.000 us, frequency 0.000 ppm, interval 1 s,
maximum error 13899 us, estimated error 0 us,
status 0x1 (PLL),
time constant 10, precision 1.000 us, tolerance 500 ppm,
#ntpdate ntp1.oma.be
7 Sep 17:08:47 ntpdate[17658]: step time server 193.190.230.65 offset -193.139848 sec
| description: | updated |
| Chuck Short (zulcss) wrote | #1 |
| Changed in ntp (Ubuntu): | |
| assignee: | nobody → Chuck Short (zulcss) |
| importance: | Undecided → Low |
| status: | New → Incomplete |
| Evgeny (pterodaktil02) wrote | #2 |
| Chuck Short (zulcss) wrote | #3 |
| Changed in ntp (Ubuntu): | |
| status: | Incomplete → Invalid |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.