Re: [gentoo-user] System Clock Problems

2006-02-14 Thread Benno Schulenberg
Drew Tomlinson wrote:
 I've tried both zeroing this file and removing it altogether. 
 Zeroing doesn't work and if I delete it, it never gets recreated.
  I've even tried touching it but it remains empty.  After
 touching it, I chmod it to ntp:ntp but still remains empty.

From 'man ntpd': ...  After one hour the frequency file is created 
and the current frequency offset written to it.

Benno
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] System Clock Problems

2006-02-14 Thread Drew Tomlinson

On 2/14/2006 6:32 AM Benno Schulenberg wrote:

Drew Tomlinson wrote:
  
I've tried both zeroing this file and removing it altogether. 
Zeroing doesn't work and if I delete it, it never gets recreated.

 I've even tried touching it but it remains empty.  After
touching it, I chmod it to ntp:ntp but still remains empty.



From 'man ntpd': ...  After one hour the frequency file is created 
and the current frequency offset written to it.
  


Right.  I should have been more clear.  Even after 2 hours, there was no 
file.  I suspected file permissions which is I used chown to set the 
file to ntp:ntp.


Thanks,

Drew

--
Visit The Alchemist's Warehouse
Magic Tricks, DVDs, Videos, Books,  More!

http://www.alchemistswarehouse.com

--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] System Clock Problems

2006-02-13 Thread Nick Rout
If your system stopped suddenly the ntp.drfit file may have become corrupted. 
As I understand it this file has a value in it that tells the system how much 
drift there is in the system clock, and uses the figutre to compensate. If the 
figure is way  out then the compensation will be way out.

Take a look at /var/lib/ntp/ntp.drift, if its seems like a large figure, then 
zero it and start again from scratch. ie stop ntpd, set the clock with ntpdate, 
then start the ntpd service again (preferably not while recording with mythtv 
LOL).


On Sun, 12 Feb 2006 12:10:20 -0800
Drew Tomlinson wrote:

 I have Gentoo 2.6.13-r5 kernel running and have used ntpd in 
 broadcastclient mode to keep its time in sync on my home network.  The 
 other day, the system suffered and abrupt shutdown due to a power 
 outage.  Ever since then, the system clock gains about 10 seconds every 
 5 minutes.  Also, I can't get ntpd to sync the clock.  My command line 
 is ntpd -A -b -g -u ntp:ntp.  I've included some output running the 
 command with the debug switch below.
 
 I've also tried to gain more info with the ntpdc utility although I 
 don't really know what I'm doing.  However it appears that ntpd does see 
 my FreeBSD time server even though it's not synced:
 
 ntpdc peers
  remote   local  st poll reach  delay   offsetdisp
 ===
 =192.168.1.2 0.0.0.0  2   647 0.00038 -9.600170 1.98438
 
 The time server is a FreeBSD 6.0 box on my network.  My other FreeBSD 
 box and two Windows boxes get time from it just fine.  Even the Gentoo 
 box will set its clock with ntpd -gq.  I am currently using this brute 
 force method via a cron job as a temporary workaround.
 
 Any ideas on what might have caused this recent change in behavior?
 
 Thanks for your help,
 
 Drew
 
 
 --- Begin debug output ---
 ntpd [EMAIL PROTECTED] Sat Feb 11 19:19:56 PST 2006 (1)
 addto_syslog: ntpd [EMAIL PROTECTED] Sat Feb 11 19:19:56 PST 2006 (1)
 addto_syslog: precision = 3.000 usec
 create_sockets(123)
 addto_syslog: no IPv6 interfaces found
 bind() fd 4, family 2, port 123, addr 0.0.0.0, flags=8
 addto_syslog: Listening on interface wildcard, 0.0.0.0#123
 bind() fd 5, family 2, port 123, addr 127.0.0.1, flags=0
 addto_syslog: Listening on interface lo, 127.0.0.1#123
 bind() fd 6, family 2, port 123, addr 192.168.1.6, flags=8
 addto_syslog: Listening on interface eth1, 192.168.1.6#123
 init_io: maxactivefd 6
 local_clock: time 0 clock 0.00 offset 0.00 freq 0.000 state 0
 bind() fd 8, family 2, port 123, addr 192.168.1.255, flags=8
 io_setbclient: Opened broadcast client on interface 2, socket: 8
 io_setbclient: Opened broadcast clients
 addto_syslog: frequency initialized -36.958 PPM from /etc/ntp/ntp.drift
 local_clock: time 0 clock 0.00 offset 0.00 freq -36.958 state 1
 report_event: system event 'event_restart' (0x01) status 'sync_alarm, 
 sync_unspec, 1 event, event_unspec' (0xc010)
 auth_agekeys: at 1 keys 1 expired 0
 timer: refresh ts 0
 receive: at 15 192.168.1.6-192.168.1.2 mode 5 code 5
 Finding addr 192.168.1.2 in list of addresses
 key_expire: at 15
 peer_clear: at 15 assoc ID 33252 refid INIT
 newpeer: 192.168.1.6-192.168.1.2 mode 3 vers 4 poll 6 10 flags 0x210 
 0x20 ttl 0 key 
 receive: at 15 0.0.0.0-192.168.1.2 mode 5 code 6
 peer 192.168.1.2 event 'event_reach' (0x84) status 'unreach, 1 event, 
 event_reach' (0x14)
 auth_agekeys: at 60 keys 1 expired 0
 transmit: at 79 0.0.0.0-192.168.1.2 mode 3
 receive: at 79 192.168.1.6-192.168.1.2 mode 4 code 1
 clock_filter: popcorn 7.896193 0.000960
 receive: at 82 192.168.1.6-192.168.1.2 mode 5 code 6
 receive: at 82 0.0.0.0-192.168.1.2 mode 5 code 6
 auth_agekeys: at 120 keys 1 expired 0
 transmit: at 143 0.0.0.0-192.168.1.2 mode 3
 receive: at 143 192.168.1.6-192.168.1.2 mode 4 code 1
 clock_filter: n 2 off -9.600170 del 0.000386 dsp 3.937744 jit 1.703977, 
 age 64
 receive: at 148 192.168.1.6-192.168.1.2 mode 5 code 6
 receive: at 148 0.0.0.0-192.168.1.2 mode 5 code 6
 auth_agekeys: at 180 keys 1 expired 0
 transmit: at 206 0.0.0.0-192.168.1.2 mode 3
 receive: at 206 192.168.1.6-192.168.1.2 mode 4 code 1
 clock_filter: n 3 off -9.600170 del 0.000386 dsp 1.938216 jit 1.639332, 
 age 127
 receive: at 215 192.168.1.6-192.168.1.2 mode 5 code 6
 receive: at 215 0.0.0.0-192.168.1.2 mode 5 code 6
 --- End debug output ---
 
 
 -- 
 gentoo-user@gentoo.org mailing list

-- 
Nick Rout [EMAIL PROTECTED]

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] System Clock Problems

2006-02-13 Thread Drew Tomlinson

On 2/13/2006 1:11 PM Nick Rout wrote:

If your system stopped suddenly the ntp.drfit file may have become corrupted. 
As I understand it this file has a value in it that tells the system how much 
drift there is in the system clock, and uses the figutre to compensate. If the 
figure is way  out then the compensation will be way out.

Take a look at /var/lib/ntp/ntp.drift, if its seems like a large figure, then 
zero it and start again from scratch. ie stop ntpd, set the clock with ntpdate, 
then start the ntpd service again (preferably not while recording with mythtv 
LOL).
  
I've tried both zeroing this file and removing it altogether.  Zeroing 
doesn't work and if I delete it, it never gets recreated.  I've even 
tried touching it but it remains empty.  After touching it, I chmod it 
to ntp:ntp but still remains empty.  I'm by no means an expert but I 
don't get it.


Thanks for your reply,

Drew

--
Visit The Alchemist's Warehouse
Magic Tricks, DVDs, Videos, Books,  More!

http://www.alchemistswarehouse.com

--
gentoo-user@gentoo.org mailing list



[gentoo-user] System Clock Problems

2006-02-12 Thread Drew Tomlinson
I have Gentoo 2.6.13-r5 kernel running and have used ntpd in 
broadcastclient mode to keep its time in sync on my home network.  The 
other day, the system suffered and abrupt shutdown due to a power 
outage.  Ever since then, the system clock gains about 10 seconds every 
5 minutes.  Also, I can't get ntpd to sync the clock.  My command line 
is ntpd -A -b -g -u ntp:ntp.  I've included some output running the 
command with the debug switch below.


I've also tried to gain more info with the ntpdc utility although I 
don't really know what I'm doing.  However it appears that ntpd does see 
my FreeBSD time server even though it's not synced:


ntpdc peers
remote   local  st poll reach  delay   offsetdisp
===
=192.168.1.2 0.0.0.0  2   647 0.00038 -9.600170 1.98438

The time server is a FreeBSD 6.0 box on my network.  My other FreeBSD 
box and two Windows boxes get time from it just fine.  Even the Gentoo 
box will set its clock with ntpd -gq.  I am currently using this brute 
force method via a cron job as a temporary workaround.


Any ideas on what might have caused this recent change in behavior?

Thanks for your help,

Drew


--- Begin debug output ---
ntpd [EMAIL PROTECTED] Sat Feb 11 19:19:56 PST 2006 (1)
addto_syslog: ntpd [EMAIL PROTECTED] Sat Feb 11 19:19:56 PST 2006 (1)
addto_syslog: precision = 3.000 usec
create_sockets(123)
addto_syslog: no IPv6 interfaces found
bind() fd 4, family 2, port 123, addr 0.0.0.0, flags=8
addto_syslog: Listening on interface wildcard, 0.0.0.0#123
bind() fd 5, family 2, port 123, addr 127.0.0.1, flags=0
addto_syslog: Listening on interface lo, 127.0.0.1#123
bind() fd 6, family 2, port 123, addr 192.168.1.6, flags=8
addto_syslog: Listening on interface eth1, 192.168.1.6#123
init_io: maxactivefd 6
local_clock: time 0 clock 0.00 offset 0.00 freq 0.000 state 0
bind() fd 8, family 2, port 123, addr 192.168.1.255, flags=8
io_setbclient: Opened broadcast client on interface 2, socket: 8
io_setbclient: Opened broadcast clients
addto_syslog: frequency initialized -36.958 PPM from /etc/ntp/ntp.drift
local_clock: time 0 clock 0.00 offset 0.00 freq -36.958 state 1
report_event: system event 'event_restart' (0x01) status 'sync_alarm, 
sync_unspec, 1 event, event_unspec' (0xc010)

auth_agekeys: at 1 keys 1 expired 0
timer: refresh ts 0
receive: at 15 192.168.1.6-192.168.1.2 mode 5 code 5
Finding addr 192.168.1.2 in list of addresses
key_expire: at 15
peer_clear: at 15 assoc ID 33252 refid INIT
newpeer: 192.168.1.6-192.168.1.2 mode 3 vers 4 poll 6 10 flags 0x210 
0x20 ttl 0 key 

receive: at 15 0.0.0.0-192.168.1.2 mode 5 code 6
peer 192.168.1.2 event 'event_reach' (0x84) status 'unreach, 1 event, 
event_reach' (0x14)

auth_agekeys: at 60 keys 1 expired 0
transmit: at 79 0.0.0.0-192.168.1.2 mode 3
receive: at 79 192.168.1.6-192.168.1.2 mode 4 code 1
clock_filter: popcorn 7.896193 0.000960
receive: at 82 192.168.1.6-192.168.1.2 mode 5 code 6
receive: at 82 0.0.0.0-192.168.1.2 mode 5 code 6
auth_agekeys: at 120 keys 1 expired 0
transmit: at 143 0.0.0.0-192.168.1.2 mode 3
receive: at 143 192.168.1.6-192.168.1.2 mode 4 code 1
clock_filter: n 2 off -9.600170 del 0.000386 dsp 3.937744 jit 1.703977, 
age 64

receive: at 148 192.168.1.6-192.168.1.2 mode 5 code 6
receive: at 148 0.0.0.0-192.168.1.2 mode 5 code 6
auth_agekeys: at 180 keys 1 expired 0
transmit: at 206 0.0.0.0-192.168.1.2 mode 3
receive: at 206 192.168.1.6-192.168.1.2 mode 4 code 1
clock_filter: n 3 off -9.600170 del 0.000386 dsp 1.938216 jit 1.639332, 
age 127

receive: at 215 192.168.1.6-192.168.1.2 mode 5 code 6
receive: at 215 0.0.0.0-192.168.1.2 mode 5 code 6
--- End debug output ---


--
gentoo-user@gentoo.org mailing list