| 1 |
On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote: |
| 2 |
|
| 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 |
|
| 18 |
ntpd -p returns: |
| 19 |
ntpq: read: Connection refused |
| 20 |
|
| 21 |
/etc/init.d/ntpd status returns: |
| 22 |
* status: crashed |
| 23 |
|
| 24 |
/etc/init.d/ntpd stop returns |
| 25 |
* Caching service dependencies ... |
| 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 |
| 36 |
0:00 /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 |
| 53 |
window. |
| 54 |
|
| 55 |
The offset is large, which may be why it's crashing. There may be some |
| 56 |
problem setting the hardware clock, since I had an error on bootup |
| 57 |
stating that I was unable to set the hardware clock by any method until |
| 58 |
I set clock_systohc="NO" |
| 59 |
in /etc/conf.d/hwclock (which just prevents it trying to set the |
| 60 |
hardware clock). |
| 61 |
|
| 62 |
hwclock --debug output may be useful: |
| 63 |
hwclock from util-linux 2.20.1 |
| 64 |
hwclock: Open of /dev/rtc failed: No such file or directory |
| 65 |
No usable clock interface found. |
| 66 |
hwclock: Cannot access the Hardware Clock via any known method. |
| 67 |
|
| 68 |
Jeff |
Archives