On Thu, 5 Feb 2015 16:39:42 +0000 Mark Rogers mark@more-solutions.co.uk allegedly wrote:
I have a little (headless) ARM box running Debian with a built in clock module, but whose battery had died. On replacement the box failed to get an IP address via DHCP.
On investigation it appears that because the clock was "wrong" it couldn't perform DHCP queries ("Unable to setup timer"). I think "wrong" doesn't just mean inaccurate (it was claiming to be in 1928) but corrupt (hwclock reported corrupt registers).
The clock would get reset by a time server as soon as it got online, but without valid clock it couldn't get online to get the valid clock...
Anyone know any more about this or able to point to a general workaround for next time this happens?
Obvious question. Do you have to use DHCP? I always give servers fixed IP addresses. A headless debian box sounds like a "server" to me.
Mick ---------------------------------------------------------------------
Mick Morgan gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312 http://baldric.net
---------------------------------------------------------------------