On Tue, 2011-07-19 at 08:35 +0200, Per Jessen wrote:
Roger Oberholtzer wrote:
On Mon, 2011-07-18 at 12:05 +0200, Per Jessen wrote:
To stick to the legal metaphors, I think the judge will dismiss your claim as hear-say :-) At least until you present evidence that the server is configured but not used ("ntpq -p" will show the peers).
I finally got a chance to run this (after boot, logged in and network up, time still wrong):
# ntpq -p ntpq: read: Connection refused
At this point, could you also do 'pidof ntpd', please. I'm pretty certain ntpd isn't running.
But it is! I see it in the process list. It is always there. When I restart it, I get a message (in /var/log/ntp) from the original one that it is shutting down. Then the messages from the newly started one.
After boot (real time was 21.48), I see this is /var/log/messages:
Jul 18 23:48:59 barracuda ntpd[3033]: ntpd 4.2.6p3@1.2290-o Tue Jun 7 03:10:56 UTC 2011 (1) Jul 18 23:48:59 barracuda ntpd[3034]: proto:
So the question now is - _who_ adjusted the system clock? It was _not_ ntpd, because that is only just starting.
/var/log/ntp has (wireless up at 23:54:00):
18 Jul 23:48:59 ntpd[3034]: Deferring DNS for ntp1.sth.netnod.se 1 18 Jul 23:49:02 ntpd[3069]: host name not found: ntp1.sth.netnod.se 18 Jul 23:50:04 ntpd[3069]: host name not found: ntp1.sth.netnod.se 18 Jul 23:52:06 ntpd[3069]: host name not found: ntp1.sth.netnod.se 18 Jul 23:54:00 ntpd[3034]: Listen normally on 4 wlan0 192.168.1.17 UDP 123 18 Jul 23:54:01 ntpd[3034]: Listen normally on 5 wlan0 fe80::227:10ff:fe71:6724 UDP 123 18 Jul 23:54:01 ntpd[3034]: peers refreshed 18 Jul 23:54:01 ntpd[3034]: new interface(s) found: waking up resolver 18 Jul 23:54:03 ntpd[3069]: DNS ntp1.sth.netnod.se -> 192.36.144.22
what about the next 20-30mins of log?
The system had been running for about 60 minutes when I took the logs. That is all there was. Nothing more in either file.
My /etc/sysconfig has:
NTPD_OPTIONS="-g -u ntp:ntp"
My /etc/ntp.conf file is:
server 127.127.1.0 fudge 127.127.1.0 stratum 10 driftfile /var/lib/ntp/drift/ntp.drift logfile /var/log/ntp keys /etc/ntp.keys trustedkey 1 requestkey 1 server ntp1.sth.netnod.se iburst
All fine.
So, it seems that the time source is retried, but nothing happens. And, the -p option is failing.
Because ntpd has left the building.
Or has decided to hide in the basement.
A wild guess at what is happening - before ntp starts, something adjusts your system clock 2 hours forward. ntp starts, but has no network, so just resumes normal working mode. Network comes up, ntpd say "yippee!", gets fresh time from netnod.se and then leaves as the time gap is more than the sanity check of 1000s.
Seems as good a guess as any. The other player here is boot.clock. I will try disabling ntp and see if the time comes up correctly. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org