| 1 |
On 03/03/2012 05:55 AM, Mick wrote: |
| 2 |
> I am sure that the CMOS battery is dead in this old box and this may be |
| 3 |
> related to it, but the error persists even when I restart chronyd after I set |
| 4 |
> the date manually: |
| 5 |
> |
| 6 |
> chronyd[3105]: Fatal error: settimeofday() failed |
| 7 |
> chronyd[3424]: Could not settimeofday |
| 8 |
> chronyd[3105]: Fatal error: settimeofday() failed |
| 9 |
> chronyd[3424]: Fatal error: settimeofday() failed |
| 10 |
> |
| 11 |
> This is what syslog shows: |
| 12 |
> |
| 13 |
> Mar 3 13:47:12 lappy chronyd[3424]: chronyd version 1.26 starting |
| 14 |
> Mar 3 13:47:12 lappy chronyd[3424]: Set system time, error in RTC = |
| 15 |
> 1169296056129876.500000 |
| 16 |
> Mar 3 13:47:12 lappy chronyd[3424]: Could not settimeofday |
| 17 |
> Mar 3 13:47:12 lappy chronyd[3424]: Linux kernel major=3 minor=2 patch=1 |
| 18 |
> Mar 3 13:47:12 lappy chronyd[3424]: hz=100 shift_hz=7 freq_scale=1.00000000 |
| 19 |
> nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000 |
| 20 |
> Mar 3 13:47:12 lappy chronyd[3424]: Could not open IPv6 NTP socket : Address |
| 21 |
> family not supported by protocol |
| 22 |
> Mar 3 13:47:12 lappy chronyd[3424]: Could not open IPv6 command socket : |
| 23 |
> Address family not supported by protocol |
| 24 |
> Mar 3 13:47:12 lappy chronyd[3424]: Frequency -36.574 +- 0.028 ppm read from |
| 25 |
> /etc/chrony/chrony.drift |
| 26 |
> Mar 3 13:47:21 lappy chronyd[3424]: System trim from RTC = |
| 27 |
> 1169296066498122.500000 |
| 28 |
> Mar 3 13:47:22 lappy chronyd[3424]: System's initial offset : |
| 29 |
> 2147481497.991868 seconds fast of true (step) |
| 30 |
> Mar 3 13:47:22 lappy chronyd[3424]: Fatal error : settimeofday() failed |
| 31 |
> |
| 32 |
> Should I worry about this? |
| 33 |
|
| 34 |
Maybe the hardware clock is too far off? Does hwclock -w change anything? |
Archives