Closed Bug 537622 Opened 15 years ago Closed 15 years ago

MySQL is down on sm-hudson01

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

All
Other
task
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jbalogh, Assigned: fox2mike)

Details

Looks like it didn't come on with the reboot. Things that should happen when this box gets rebooted (AFAIK): 1. Start a time syncer. 2. Start MySQL. 3. Start Hudson.
Back up.
Assignee: server-ops → shyam
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Just a more verbose response, now that I have more time :D (In reply to comment #0) > Things that should happen when this box gets rebooted (AFAIK): > > 1. Start a time syncer. Not how VMWare works. It could be an option, but we prefer to let VMWare Tools handle time syncs. After spending a bit of time on the issue, I think it's fixed. The host on which sm-hudson01 was on, dev-vmware02 was having time sync issues, which I've since fixed. The guests just pick up time from their hosts and so, this should be fine now. > 2. Start MySQL. Wasn't setup to start automagically, has been done so. I don't think I knew you guys were using mysql on the box..so well, we had no idea it was needed. > 3. Start Hudson. Was already in place and hudson was up and running anyway.
(In reply to comment #2) > Just a more verbose response, now that I have more time :D Thanks, we have a happy Chuck Norris now.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.