It Doesn\'t Happen Often
Ryan on May 20, 2005 9:12am
...but occasionally I have a \"bad-day\" at work. Now granted I\'m not scraping up human remains off the ground or anything, (I don\'t think that\'d ever be a *good day* do you?), but in comparison to a normal day at work, yesterday SUCKED!
It\'s murphy\'s law, and that always seems to be the issue in my life. We have a client that one of us is pretty much the goto man for everything. Since he is the goto man, he rarely has time to update documentation, or even give us a heads up on some of the goings on, he\'s just that busy. Well yesterday and today he is out and sure enough, yesterday shit stopped working. I get a call, find out stuff is broken and begin the long painful task of trying to figure it out.
Luckily a more experienced person here was working on the problem too, (unbeknownst to me at the time). We eventually put our heads together, made some progress, but the app still wasn\'t doing what it was supposed to do. All along, in the back of our minds we kept saying, \"maybe we should restart the server\" but all logic was telling us that wouldn\'t make any difference since it was \"working\" just not finding some things that should have been on a remote server.
To make a long story short...(too late)...we redployed some things with some debugging statements that wound up not helping much. Our main man of the application restarted the server in the evening and everthing started working.
Near as we can tell, something on the remote server changed, DNS...something...and the server restart flushed the applications cache. (Which we figured a redeploy would\'ve done that, but we tried that a few times...)
*sigh* Needless to say, I\'ve still got heartburn...I hate stress.
It\'s murphy\'s law, and that always seems to be the issue in my life. We have a client that one of us is pretty much the goto man for everything. Since he is the goto man, he rarely has time to update documentation, or even give us a heads up on some of the goings on, he\'s just that busy. Well yesterday and today he is out and sure enough, yesterday shit stopped working. I get a call, find out stuff is broken and begin the long painful task of trying to figure it out.
Luckily a more experienced person here was working on the problem too, (unbeknownst to me at the time). We eventually put our heads together, made some progress, but the app still wasn\'t doing what it was supposed to do. All along, in the back of our minds we kept saying, \"maybe we should restart the server\" but all logic was telling us that wouldn\'t make any difference since it was \"working\" just not finding some things that should have been on a remote server.
To make a long story short...(too late)...we redployed some things with some debugging statements that wound up not helping much. Our main man of the application restarted the server in the evening and everthing started working.
Near as we can tell, something on the remote server changed, DNS...something...and the server restart flushed the applications cache. (Which we figured a redeploy would\'ve done that, but we tried that a few times...)
*sigh* Needless to say, I\'ve still got heartburn...I hate stress.
comments:
