![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Apr. 22nd, 2015 09:47 amWoke up at 5:15 when the cat knocked my cell phone off the headboard and onto my head. Got up, fed the cats.
Looked at my cell phone and saw the overnight batch jobs for the office hadn't run, or hadn't made it to the point where emails are sent out (normally I get an email around 2:30 AM, then one around 4 AM, then another at around 5). Pulled out the laptop, remoted in, found a crash message, clicked through it, waited for the jobs to run.
Cat threw up. Got up and cleaned it, went back to waiting for one job to finish so I could start off another one manually (the 5 AM job relies on files created by the 2:30 job, but if those files aren't generated then the 5 AM job has to be run by hand once the new files get made).
Suddenly got a message from the backup software that one of the other servers had crashed. Couldn't ping it. Pulled up the VMware console for its blade, saw a bluescreen. Spent the better part of 20 minutes trying to alleviate this, then decided I was better off coming to work to fix it in person.
Problem was eventually fixed and we are now running a bit behind, but at least running. Not sure if the cat is past the situation that made him throw up, but he seemed like he was doing better when I left.
I have had better mornings than this, but at least things got fixed. And at least spending time in the helicopters has taught me not to panic when things get hairy.
If I am cranky today, this is why.
Looked at my cell phone and saw the overnight batch jobs for the office hadn't run, or hadn't made it to the point where emails are sent out (normally I get an email around 2:30 AM, then one around 4 AM, then another at around 5). Pulled out the laptop, remoted in, found a crash message, clicked through it, waited for the jobs to run.
Cat threw up. Got up and cleaned it, went back to waiting for one job to finish so I could start off another one manually (the 5 AM job relies on files created by the 2:30 job, but if those files aren't generated then the 5 AM job has to be run by hand once the new files get made).
Suddenly got a message from the backup software that one of the other servers had crashed. Couldn't ping it. Pulled up the VMware console for its blade, saw a bluescreen. Spent the better part of 20 minutes trying to alleviate this, then decided I was better off coming to work to fix it in person.
Problem was eventually fixed and we are now running a bit behind, but at least running. Not sure if the cat is past the situation that made him throw up, but he seemed like he was doing better when I left.
I have had better mornings than this, but at least things got fixed. And at least spending time in the helicopters has taught me not to panic when things get hairy.
If I am cranky today, this is why.
