A programmer's nightmare

I call it the 7:30 PM Ghost... lame name it might be, but it can't get any more appropriate than that -_-


Its not the first time we planned to wrap things out before the sky turns dark, and its not the first time we were hit by unexplainable phenomena during our testing.

Picture this, I came to office 7:45 am today to perform migration, and the testing was smoothly carried out all the way till 5:00 pm, before all the minor bugs uncovered during the process were fixed, we had another migration around 6:30 pm.

Then around 7:45 pm, problems began creeping out...

First the provision service failed for no reason, then CRS can't run (never mind you don't know what they are, they're just programs we've written for this project), and eventually the migrated server died off just like that...

After a brief dinner (I didn't had any, in fact, i ate sandwich and bread for breakfast and lunch, i was too sicked to eat anything actually) and when we return to test, we decided to restart the server...

Now 10:00 pm. the server's memory usage is still very very high, at times we encounter problem like conference server died, remoting calls not responding... as usual, no bugs in our program, just purely network issues...


Recall SMU days, at times we were so happy that today's migration was so smooth and started planning where for dinner, only to be held back by unknown "ghosts" that appear after the 7:30 pm mark...

Then in the phase 1 of this MMC project, there were a couple of occassion that we actually spent the whole night debugging stupid network problems... "ghosts" as it would be... Why don't they appear earlier in the morning? Why must they only appear when we have prepared to wrap things up?

Ahh... 10:04 pm now, I'm ready to go catch ghost now :D
Wish me good luck :D hohohohoho