From: "Anthony E. Caudel" <acaudel@gt.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NTP problem
Date: Wed, 22 Feb 2006 02:41:10 -0600 [thread overview]
Message-ID: <43FC23A6.10604@gt.rr.com> (raw)
In-Reply-To: <1140595855.5340.17.camel@localhost>
Brandon Enright wrote:
> On Wed, 2006-02-22 at 01:32 -0600, Anthony E. Caudel wrote:
>
>>My system was off about 10 days and when I turned it back on, I began
>>getting these messages in my logwatch:
>>
>>"Time Reset
>> time stepped -0.133773
>> time stepped -0.662954
>> time stepped +0.271164
>> time stepped +0.461200
>> time stepped -0.787647
>><snip>
>>
>> Time Reset 25 times (total: -1.239782 s average: -0.049591 s)
>>
>> **Unmatched Entries**
>> synchronized to 80.35.31.228, stratum 3
>> synchronized to 80.35.31.228, stratum 4
>><snip>
>> synchronized to 80.35.31.228, stratum 4
>> synchronized to 80.35.31.228, stratum 3
>> Listening on interface wildcard, 0.0.0.0#123
>> Listening on interface eth0, 192.168.1.100#123
>> Listening on interface lo, 127.0.0.1#123
>> kernel time sync status 0040"
>>
>>I rebooted thinking it needed to stabilize but it still gets them. I
>>have ntp-client and ntpd both in the "default" runlevel.
>>
>>This seems like an awful high number of resets. Much more than I used
>>to get.
>>
>>Tony
>
>
>
> Those are some pretty big jumps. What does "ntpq -c peers" and "ntpq -c
> rv" output? Also, what are the first few lines (the restrict entries)
> of your ntp.conf?
>
> Brandon
>
ntpq -c peers:
remote refid st t when poll reach delay offset jitter
==============================================================================
*ntp3.usv.ro .PPS. 1 u 70 1024 377 203.080 7.338 1.485
ntpq -rv:
assID=0 status=06a4 leap_none, sync_ntp, 10 events, event_peer/strat_chg,
version="ntpd 4.2.0a@1.1190-r Thu Dec 8 09:35:31 CST 2005 (1)"?,
processor="i686", system="Linux/2.6.15-gentoo-r1", leap=00, stratum=2,
precision=-20, rootdelay=203.080, rootdispersion=34.319, peer=35268,
refid=80.96.120.249,
reftime=c7a69e5a.a3227d02 Wed, Feb 22 2006 2:24:58.637, poll=10,
clock=0xc7a6a0b6.78a5bd94, state=4, offset=7.338, frequency=35.514,
noise=2.162, jitter=0.891, stability=64.582
ntp.conf:
restrict default nomodify nopeer
restrict 127.0.0.1
Tony
--
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-22 8:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 7:32 [gentoo-user] NTP problem Anthony E. Caudel
2006-02-22 8:10 ` Brandon Enright
2006-02-22 8:41 ` Anthony E. Caudel [this message]
2006-02-22 16:29 ` Brandon Enright
2006-02-22 18:38 ` Anthony E. Caudel
2006-02-22 19:05 ` Boyd Stephen Smith Jr.
2006-02-22 19:13 ` Brandon Enright
2006-02-22 20:03 ` Boyd Stephen Smith Jr.
-- strict thread matches above, loose matches on Subject: below --
2005-08-23 12:36 [gentoo-user] ntp problem Bruno Lustosa
2005-08-23 13:14 ` krzaq
2005-08-23 13:21 ` Bruno Lustosa
2005-08-23 13:25 ` Uwe Thiem
2005-08-23 14:30 ` Bruno Lustosa
2005-08-23 15:46 ` Michael Kintzios
2005-08-23 17:50 ` Bruno Lustosa
2005-08-23 13:26 ` kashani
2005-08-23 13:29 ` Bruno Lustosa
2005-08-23 14:19 ` krzaq
2005-08-23 14:26 ` Bruno Lustosa
2005-08-23 14:28 ` Bruno Lustosa
2005-08-24 1:25 ` W.Kenworthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43FC23A6.10604@gt.rr.com \
--to=acaudel@gt.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox