| 1 |
Jeff Cranmer wrote: |
| 2 |
> On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote: |
| 3 |
>> Define crashing? |
| 4 |
>> |
| 5 |
>> This looks more like problems with yout TZ variables than ntpd. |
| 6 |
>> |
| 7 |
>> try "ntpq -p" to check if its actually running/locked. If ntpd is |
| 8 |
>> freewheeling, it is prpbably because your time is too far from lock so |
| 9 |
>> it will silently fail (default config). |
| 10 |
>> |
| 11 |
>> If ntpd has really crashed (ps aux will confirm), try running the daemon |
| 12 |
>> manually from a console - if it "segfaults" or comes up with a missing |
| 13 |
>> library, try "ldd /usr/sbin/ntpd" to find which lib is needed and fix. |
| 14 |
>> |
| 15 |
>> BillK |
| 16 |
>> |
| 17 |
> ntpd -p returns: |
| 18 |
> ntpq: read: Connection refused |
| 19 |
> |
| 20 |
> /etc/init.d/ntpd status returns: |
| 21 |
> * status: crashed |
| 22 |
> |
| 23 |
> /etc/init.d/ntpd stop returns |
| 24 |
> * Caching service dependencies |
| 25 |
> ... |
| 26 |
> [ ok ] |
| 27 |
> * Stopping ntpd ... |
| 28 |
> * start-stop-daemon: no matching processes found |
| 29 |
> |
| 30 |
> I tried running /usr/sbin/ntpd from a console, and nothing much happens. |
| 31 |
> There now appears to be a process running for ntpd, but my time is still |
| 32 |
> wrong. |
| 33 |
> |
| 34 |
> ps -aux shows |
| 35 |
> root 21470 0.0 0.0 26140 1908 ? Ss 07:22 0:00 |
| 36 |
> /usr/sbin/ntpd |
| 37 |
> |
| 38 |
> ntpq -p now returns |
| 39 |
> remote refid st t when poll reach delay offset |
| 40 |
> jitter |
| 41 |
> ============================================================================== |
| 42 |
> ntp.cox.net .GPS. 1 u 5 64 7 42.229 1800133 |
| 43 |
> 3.020 |
| 44 |
> 235-69-67-68.st 130.88.200.6 3 u 4 64 7 47.125 1800132 |
| 45 |
> 1.457 |
| 46 |
> clock.team-cymr 172.16.65.22 2 u 3 64 7 50.691 1800132 |
| 47 |
> 0.905 |
| 48 |
> sulfur.mednor.n 164.67.62.194 2 u 1 64 7 88.498 1800131 |
| 49 |
> 2.870 |
| 50 |
> |
| 51 |
> After a few minutes, I repeated ntpq -p, and got connection refused. |
| 52 |
> The program is crashed. No error messages appear in the command window. |
| 53 |
> |
| 54 |
> The offset is large, which may be why it's crashing. There may be some |
| 55 |
> problem setting the hardware clock, since I had an error on bootup |
| 56 |
> stating that I was unable to set the hardware clock by any method until |
| 57 |
> I set clock_systohc="NO" |
| 58 |
> in /etc/conf.d/hwclock (which just prevents it trying to set the |
| 59 |
> hardware clock). |
| 60 |
> |
| 61 |
> hwclock --debug output may be useful: |
| 62 |
> hwclock from util-linux 2.20.1 |
| 63 |
> hwclock: Open of /dev/rtc failed: No such file or directory |
| 64 |
> No usable clock interface found. |
| 65 |
> hwclock: Cannot access the Hardware Clock via any known method. |
| 66 |
|
| 67 |
No kidding the offset is large. If you just sent this email a few |
| 68 |
minutes ago. The email's send date is "Tue, 10 Jan 2012 07:33:49 -0500". |
| 69 |
The mail server which received it logged it as on "Tue, 10 Jan 2012 |
| 70 |
10:33:53 -0700", which suggests you're about five hours off. |
| 71 |
|
| 72 |
Hm. That sounds like your tz (-0500) is being applied twice. |
Archives