This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
operations:starting_monitoring_9.10.5 [2016/02/25 00:54] Jamie McCallum [FS time is out by minutes, hours, months or years!] |
operations:starting_monitoring_9.10.5 [2016/02/25 00:56] Jamie McCallum [FS time is out by minutes, hours, months or years!] |
||
---|---|---|---|
Line 286: | Line 286: | ||
The problem is the field system actually uses the hardware BIOS time from the pcfs[hb][ke][yg] computer, not the operating system time. If all the times appear OK but the field system is still incorrect then you will need to fix the hardware BIOS time setting. To read the hardware time, as root user; <code>hwclock -r</code> The system time comes from a local GPS receiver which runs an NTP server. Check that the pcfs[hb][ke][yg] system time is indeed correct; <code>ntpd -nq</code> | The problem is the field system actually uses the hardware BIOS time from the pcfs[hb][ke][yg] computer, not the operating system time. If all the times appear OK but the field system is still incorrect then you will need to fix the hardware BIOS time setting. To read the hardware time, as root user; <code>hwclock -r</code> The system time comes from a local GPS receiver which runs an NTP server. Check that the pcfs[hb][ke][yg] system time is indeed correct; <code>ntpd -nq</code> | ||
The offset from the first server in the list should be less than 10 ms. | The offset from the first server in the list should be less than 10 ms. | ||
- | Then write the current system time to the hardware clock. <code>hwclock -w</code> | + | Then write the current system time to the hardware clock, as root user; <code>hwclock -w</code> |
+ | That the hardware clock has gone wrong probably indicates a fault, such as a bad BIOS battery on the motherboard that needs replacing. | ||