It's 1:13AM on Sunday, and I'm at work :(

[agallag]

...preparing for the DST rollover. I have to run a script just after 3am against our 2000+ servers to make sure they all roll forward properly.

They wouldn't even let me run the script from home "just in case", even though I live 15 minutes away and could drive in if the remote access poops out. Also, even in the office I'm still technically remote, because the primary datacenter is 30 minutes from here. The secondary is 45 minutes away, and the branch servers are as much as a 4 hour flight away. Then there's the servers in London, Singapore, etc...

Here's hoping everything happens smoothly. I'm stocked up with coffee and Doritos, and the pub downstairs is open until 2am (or is that 3am? today it's both), so I'm good to go.

[agallag]

P.S. George Bush sucks for messing with DST.

[agallag]

Hey, it looks like MURC's clock is off a bit. It's only 1:38am, and murc time is showing as a few minutes after 3am (at least for me here in Eastern Standard/Daylight Time). At least we know it rolled into DST properly.

[agallag]

3:30 AM report: All is well so far. The lights are still on, and the servers have all rolled forward successfully. Yay.

[Jon P. Inghram]

Glad it worked!

[Brian Ellis]

Yup, MURC has been about 28 minutes out for ages.

[agallag]

Well, we made it through the night. Finally came home around 10am, went to bed, got paged just after I fell asleep, then got to bed again at 11:30am, and slept until 4:30 when I got paged again.

In order, the biggest problems were:

1. Java
2. Java
3. Homegrown application that interfaces with RightFax
4. Java

Did I mention that Java was also a problem? What a mess. There's so many apps that install their own embedded JVM, then they forget about it and don't provide patches for it. Urg.

[Fat Tone]

I hope you are getting compensated for all this.

Reminds me of the days when I had to, twice a year, dial in to 12 sites on a 56K modem and reset the clocks. I had about 40 minutes to do it, or else start renaming lots of files! Not so bad when the clocks go forward, but when they go back there was the risk of losing data.

[Byock]

I feel your pain. I only had about 68 servers, and maybe 100 desktops.

I want to fly to Washington and kick someone in the nuts for messing with it. I think I would prefer to follow Arizona and eliminate DST all together.

[agallag]

I hope you are getting compensated for all this.

Not officially, but the boss will probably let me take some time off for the ordeal.

Reminds me of the days when I had to, twice a year, dial in to 12 sites on a 56K modem and reset the clocks. I had about 40 minutes to do it, or else start renaming lots of files! Not so bad when the clocks go forward, but when they go back there was the risk of losing data.

Ouch, bet you automated that process right quick.

[Jessterw]

It's things like this that make me ever so happy I no longer work in that part of the IT field. I remember all the hoopla I had to do to appease management during the Y2K 'crisis' - much ado about nothing just as I need it would be (as far as it affected our systems).

Hopefully your boss is better than my former about actually delivering on that time off.

I'll add another vote for getting rid of DST. My work hours and sleep patterns are off enough as it is without having to adjust for that.