Is this week over yet?
Jul. 14th, 2004 09:41 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sierciaLife? Completely insane. Work? Making me wish I were dead.
So, Monday, come into the office to chaos from the carpeting/moving/disaster of the weekend. Half the office is off moving servers because we're changing our hosting facilities. The other half is running around crazy trying to get settled into new digs. Get maybe a third of the way settled into new digs myslef, but not too much because officemate is away on vacation.
This is when I'm reminded that I'm supposed to do a big important upgrade on D's server Monday night. Spend the rest of Monday getting remote access set up to connect to D. Go home at 7, spend 30 minutes with Widget, then start getting files in place on D's server. Wiley cooks dinner, and I start the upgrade, which goes easily, at 9 and finish at 11. Okay.
Come in Tuesday morning to D having questions about server config. Spend first couple of hours at work fielding calls from D. No problem. Then I get the big bad call that D's server keeps hanging up (this is very very bad). Welcome to hell. At the office until after 8, trying to figure out D's server problem. I think we have it licked, J and I (J rocks for staying late to help me, too) head for home. By the time I get home (and this is a 10 minute commute) I have mail saying server is down again. But they got the minimum of work done so they're good for the night.
Get to office today before 10, start working on the server. Even rolling them back does not seem to work, and they are very very broken. We get the bright idea (thinking at this point that there's software corruption on their server) to move their db to one of our local servers - we'll stop bringing down Merlin for the entire library, and they will have a stable work environment to get their Trax work done. This will allow us some breathing room.
Great idea, except that as soon as we bring them over to our healthy, working server, we start seeing the SAME PROBLEM. FUCKFUCKFUCKFUCKFUCKFUCK.
Finally, we figured it out, at about 8:30 tonight. They were doing something that we shouldn't have allowed them to do, but we didn't realize it would break the software so badly. *headdesk*
Spent the next hour trying to clean up the mess, I'll be up around 7 am to connect into their server to fix things there, and then hopefully we'll be done. I'm glad it wasn't technically a bug in our software, and they certainly can't complain about our support responsiveness.
Now, since my Indian takeout will be ready soon, I am going home.
So, Monday, come into the office to chaos from the carpeting/moving/disaster of the weekend. Half the office is off moving servers because we're changing our hosting facilities. The other half is running around crazy trying to get settled into new digs. Get maybe a third of the way settled into new digs myslef, but not too much because officemate is away on vacation.
This is when I'm reminded that I'm supposed to do a big important upgrade on D's server Monday night. Spend the rest of Monday getting remote access set up to connect to D. Go home at 7, spend 30 minutes with Widget, then start getting files in place on D's server. Wiley cooks dinner, and I start the upgrade, which goes easily, at 9 and finish at 11. Okay.
Come in Tuesday morning to D having questions about server config. Spend first couple of hours at work fielding calls from D. No problem. Then I get the big bad call that D's server keeps hanging up (this is very very bad). Welcome to hell. At the office until after 8, trying to figure out D's server problem. I think we have it licked, J and I (J rocks for staying late to help me, too) head for home. By the time I get home (and this is a 10 minute commute) I have mail saying server is down again. But they got the minimum of work done so they're good for the night.
Get to office today before 10, start working on the server. Even rolling them back does not seem to work, and they are very very broken. We get the bright idea (thinking at this point that there's software corruption on their server) to move their db to one of our local servers - we'll stop bringing down Merlin for the entire library, and they will have a stable work environment to get their Trax work done. This will allow us some breathing room.
Great idea, except that as soon as we bring them over to our healthy, working server, we start seeing the SAME PROBLEM. FUCKFUCKFUCKFUCKFUCKFUCK.
Finally, we figured it out, at about 8:30 tonight. They were doing something that we shouldn't have allowed them to do, but we didn't realize it would break the software so badly. *headdesk*
Spent the next hour trying to clean up the mess, I'll be up around 7 am to connect into their server to fix things there, and then hopefully we'll be done. I'm glad it wasn't technically a bug in our software, and they certainly can't complain about our support responsiveness.
Now, since my Indian takeout will be ready soon, I am going home.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
(no subject)
Date: 2004-07-15 07:28 pm (UTC)If it makes you feel any better, I got a call for a job interview. I'm nervous, though - I have to interview with three different people. *eep*
(no subject)
Date: 2004-07-16 02:06 am (UTC)(no subject)
Date: 2004-07-16 04:31 am (UTC)(no subject)
Date: 2004-07-15 09:59 pm (UTC)(no subject)
Date: 2004-07-16 02:08 am (UTC)(no subject)
Date: 2004-07-27 06:16 pm (UTC)(no subject)
Date: 2004-07-27 06:34 pm (UTC)You'll be getting a call for an interview today or tomorrow, I think they're trying to get people in on Thursday and Friday.