Late night
25 Feb 2010Ugh, late night...which these days, means anything past 9:30pm. Two machines down at work with what I think are unrelated problems.
First one appears to have had OOM-killer run repeatedly and leave the ethernet driver in a bad state; I know, but the OOM-killer kept killing things until we got this bug.
Second one appears to have crashed and/or rebooted, but the hardware clock got reset to December 2001 in the process -- which meant that when it tried to contact the LDAP servers, none of their certificates were valid yet.
Again, ugh. But I did come across this helpful addition to my toolkit:
openssl s_client -CAfile /path/to/CA_cert -connect host:port
which, I just realized, I've rediscovered, along with having the same fucking problem again.
And did I mention I'm up at 5am tomorrow to move some equipment around at work? Ah well, I have safety boots now. I'll be suitably rewarded in Valhalla.
2 Comments
From: benny
28 February 2010 17:30:27
It looks like, according to the other post from September '09, like you implemented ntp. Am I missing something, or did NTP not do it's job?
From: Saint Aardvark
2 March 2010 04:02:41
Yeah, I think ntp is meant to set the hwclock at shutdown (well, some shutdown script anyhow); but because I had to power cycle the machine, that didn't happen. I'm unsure why the battery-backed clock on the thing didn't work.
Add a comment:
Name and email required; email is not displayed.
Related Posts
QRP weekend 08 Oct 2018
Open Source Cubesat Workshop 2018 03 Oct 2018
mpd crash? try removing files in /var/lib/mpd/ 11 Aug 2018