On Sunday 09 January 2011 00:34:33 Dale wrote:
I read the man pages and even used google but the part about what to
log didn't register with me. Basically, I need to tell it where to
put the log file, which I did, then what I want it to log as well,
which I missed. Sort of like the way
Way back when I first got an X2 they couldn't keep time for whatever
reason. I used to have to add something like clock=pmtmr notsc to the
kernel command line to make it behave.
That issue was fixed in a later kernel, but you could start adding clock
options to your kernel command line and pray
Peter Humphrey wrote:
On Friday 07 January 2011 22:48:27 Dale wrote:
Any other ideas?
You could still try chrony.
Success !! Check this out:
r...@fireball / # ntpdate -b -u -q pool.ntp.org
server 169.229.70.183, stratum 3, offset 0.009525, delay 0.12221
server
On Saturday 08 January 2011 21:45:45 Dale wrote:
Now, with ntp, it logs to messages when it syncs, resets the clock
and such. Does chrony do this somewhere too? I have this in my
conf file:
[...]
logdir /var/log/chrony
You need to uncomment the next line too - the one that specifies what
On Saturday 08 January 2011 22:59:59 Peter Humphrey wrote:
Incidentally, chronyd logs a cannot open error the first time it
tries to write to a log or dump file; it seems to be harmless.
Correction: that only applies to dump files; it creates log files quietly.
--
Rgds
Peter. Linux
Peter Humphrey wrote:
On Saturday 08 January 2011 21:45:45 Dale wrote:
Now, with ntp, it logs to messages when it syncs, resets the clock
and such. Does chrony do this somewhere too? I have this in my
conf file:
[...]
logdir /var/log/chrony
You need to uncomment the
On Thu, 2011-01-06 at 21:31 -0600, Dale wrote:
William Kenworthy wrote:
Dale, can you post (a sanitised) version of what 'ntpq -p' gives after
ntpd has been running for some time, and the sanitised result of
'ntptrace. Also include your full (sanitised) ntp.conf
and /etc/conf.d/ntpd.
William Kenworthy wrote:
Notice the difference in ntptrace between mine below and yours? The
asterisk in your ntpq table indicates that is the chosen server - but
not that it is actually locked to it - ntptrace is showing it is not
locked.
rattus ~ # ntptrace
localhost: stratum 6, offset
Dale wrote:
I added the -g option but have no idea why that will change anything.
According to the man page, it is for when the clock is more than 1000s
off which makes it outside the range ntp will change. Mine is off
only a few seconds and most of the time less than one second. So I
fail
On Friday 07 January 2011 22:48:27 Dale wrote:
Any other ideas?
You could still try chrony.
--
Rgds
Peter. Linux Counter 5290, 1994-04-23.
Peter Humphrey wrote:
On Friday 07 January 2011 22:48:27 Dale wrote:
Any other ideas?
You could still try chrony.
Well, I tried ntp, openntp, the unstable ntp but I may give that a shot
too. Heck, nothing else is working so couldn't hurt to try I guess.
May wait until
On 1/5/2011 12:04 AM, Thanasis wrote:
I think you should prefer openntpd over ntpd, because I think openntpd
is developed by openbsd, which means more secure ...
I tried openntp a couple years ago. It was a giant pain in the ass.
IIRC it was combination of crap defaults, poor docs, and
kashani wrote:
On 1/5/2011 12:04 AM, Thanasis wrote:
I think you should prefer openntpd over ntpd, because I think openntpd
is developed by openbsd, which means more secure ...
I tried openntp a couple years ago. It was a giant pain in the
ass. IIRC it was combination of crap defaults,
On Thu, 2011-01-06 at 14:46 -0600, Dale wrote:
kashani wrote:
On 1/5/2011 12:04 AM, Thanasis wrote:
I think you should prefer openntpd over ntpd, because I think openntpd
is developed by openbsd, which means more secure ...
I tried openntp a couple years ago. It was a giant pain
William Kenworthy wrote:
Dale, can you post (a sanitised) version of what 'ntpq -p' gives after
ntpd has been running for some time, and the sanitised result of
'ntptrace. Also include your full (sanitised) ntp.conf
and /etc/conf.d/ntpd.
This might help us see more detail of what is
On Fri, 7 Jan 2011 14:31:52 Dale wrote:
William Kenworthy wrote:
Dale, can you post (a sanitised) version of what 'ntpq -p' gives after
ntpd has been running for some time, and the sanitised result of
'ntptrace. Also include your full (sanitised) ntp.conf
and /etc/conf.d/ntpd.
This
Paul Colquhoun wrote:
On Fri, 7 Jan 2011 14:31:52 Dale wrote:
This is ntp.conf but I omitted the parts that are commented out.
server 64.6.144.6
server 67.159.5.90
server 67.59.168.233
server 204.62.14.98
Have you tried switching servers?
I'm using
server 0.au.pool.ntp.org
I think you should prefer openntpd over ntpd, because I think openntpd
is developed by openbsd, which means more secure ...
Am 05.01.2011 06:00, schrieb Dale:
William Kenworthy wrote:
Is the clock almost in sync? - if its too far out ntp will silently fail
to sync (by design - large scale time steps can be destructive for
heavily active databases for instance)
That's what i meant in my earlier post and what the
Steffen Loos wrote:
If i remember right your new rig is AMD-Phenom based?! - then just
have a look at
http://support.ntp.org/bin/view/Support/KnownOsIssues#Section_9.2.4.2.7.
If your clocksource is the tsc it's possible youre affected by this
problem.
At
On Tuesday 04 January 2011 01:31:27 Dale wrote:
Anybody else ran into this? Am I missing something that is different
on a 64 bit rig?
I discovered chrony some years ago, which has a sophisticated clock
slewing mechanism, and haven't used ntp since.
Chrony runs on my gateway machine to
Am 04.01.2011 02:31, schrieb Dale:
Hi,
I been watching my clock here for a while. On my old rig, ntp kept the clock
set very, very well. This rig seems to have issues. I tried the stable version
of ntp and it just seems to keep resetting the time but not adjusting the drift
file at all. I
Peter Humphrey wrote:
On Tuesday 04 January 2011 01:31:27 Dale wrote:
Anybody else ran into this? Am I missing something that is different
on a 64 bit rig?
I discovered chrony some years ago, which has a sophisticated clock
slewing mechanism, and haven't used ntp since.
Chrony
Is the clock almost in sync? - if its too far out ntp will silently fail
to sync (by design - large scale time steps can be destructive for
heavily active databases for instance)
Check out the -g option to ntpd in 'man ntpd'
or 'tinker panic 0' in ntp.conf
Also, has ntp.conf specified a
William Kenworthy wrote:
Is the clock almost in sync? - if its too far out ntp will silently fail
to sync (by design - large scale time steps can be destructive for
heavily active databases for instance)
Check out the -g option to ntpd in 'man ntpd'
or 'tinker panic 0' in ntp.conf
Also, has
Try the following and see if it resets time correctly
date 0101010101 /etc/init.d/ntpd restart date
on 01/05/2011 09:39 AM Dale wrote the following:
Thanasis wrote:
date 0101010101 /etc/init.d/ntpd restart date
I got this:
Jan 1 01:05:16 localhost ntpd[5709]: time correction of 315880203
seconds exceeds sanity limit (1000); set clock manually to the correct
UTC time.
I was pretty
Hi,
I been watching my clock here for a while. On my old rig, ntp kept the
clock set very, very well. This rig seems to have issues. I tried the
stable version of ntp and it just seems to keep resetting the time but
not adjusting the drift file at all. I even adjusted manually once and
28 matches
Mail list logo
