+wsgaskins Posted October 20, 2006 Posted October 20, 2006 It lasted awhile from about 11 pm till 1:20 am ....now its dead again. Well, I know that it's well after the server crash, and it appears most of the the rubberneckers here have moved along as well, but I could swear it was *me* that brought the system down. I had just cancelled my monthly subscription and I was in the process of setting up a yearly renewing subscription when things went belly up. *sniff* I didn't know you guys cared about me so much that the server went into convulsions when I left... I'm back now, and hopefully I'm fully re-instated for an extra year, but time will tell...
+beezerb Posted October 20, 2006 Author Posted October 20, 2006 Network Error (tcp_error) A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time. For assistance, contact your network support team. Wish I had been up when the server was. We don't seem to be keeping the same hours.
+birddog14 Posted October 20, 2006 Posted October 20, 2006 it was working for a while last night, but it is not working right now
+ventura_kids Posted October 20, 2006 Posted October 20, 2006 Ultimately we tweaked the server several times today which has been causing additional delay times, but it seems to be up and fine now. nope. it's still broke here. The forums seem ok.
+Team GPSaxophone Posted October 20, 2006 Posted October 20, 2006 Ultimately we tweaked the server several times today which has been causing additional delay times, but it seems to be up and fine now. nope. it's still broke here. The forums seem ok. Well, we all know that the forums are more important anyway
+disenchanted Posted October 20, 2006 Posted October 20, 2006 I guess TITB finally went to bed? Or.. wait... I know... He was waiting for the phones to be answered at WalMart Corporate!
+Jeremy Posted October 20, 2006 Posted October 20, 2006 Network Error (tcp_error) A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time. For assistance, contact your network support team. Wish I had been up when the server was. We don't seem to be keeping the same hours. Has anyone else experience this error? It seems less a site down error and more of a network issue. I checked the logs and the site seemed to be fine during the night. Thanks!
+Okiebryan Posted October 20, 2006 Posted October 20, 2006 Jeremy, I didn't pay attention any more than to see that I was getting "server too busy" errors. It took me dang near all night to copy and enter all the stuff I had to do... The site was down several times overnight, but would be back up in an hour or less every time... then crash again.
+Ambrosia Posted October 20, 2006 Posted October 20, 2006 After struggling for a while, I was happy to get it at just the right time early this morning and to upload all my silly hula pics at once (as well as pics for other caches). I guess that's what we get for trying to access the site in the middle of the night! Hamsters do hafta sleep ya know.
+mudsneaker Posted October 21, 2006 Posted October 21, 2006 >>1:20 am pst. Server Error in '/' Application. -------------------------------------------------------------------------------- Server Too Busy Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Server Too Busy Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80004005): Server Too Busy] System.Web.HttpRuntime.RejectRequestInternal(HttpWorkerRequest wr) +148
+Ambrosia Posted October 21, 2006 Posted October 21, 2006 *shhhh...let the poor hamsters sleep* I'll hafta change my avatar in the morning. Night.
+GrizzlyJohn Posted October 21, 2006 Posted October 21, 2006 (edited) Network Error (tcp_error) A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time. For assistance, contact your network support team. Wish I had been up when the server was. We don't seem to be keeping the same hours. Has anyone else experience this error? It seems less a site down error and more of a network issue. I checked the logs and the site seemed to be fine during the night. Thanks! Oddly enough this may not be your problem. It may be a client side problem. If it is it will be a female dog to track down because it can be really intermittent. This can occur if the client is coming through networks that start adding headers to the packets. Then the packets become too large for a router or server to handle and the packets fragment. Then your server may have problems dealing with those fragmented packets. But at some later point the route between client and server may change and it is not a problem at all. So the error message looks sort of like that server busy error, but I think what is really happening is it is trying to pull the packets together that was sent to it. While it is waiting and trying to do this it times out and it looks like the server is busy and can't reply to the request. On the client side a possible fix is to change the MTU (maxium transmission units) setting. But that is a little dicey because it is a bit of a balancing act. Setting it to high and it makes the problem worse, to low and you will be sending too many packets and your response will slow to a crawl and the server will also seem nonresponsive. I would not recommend anyone mess with that unless you really know what you are doing. But I don't know I am just taking a guess here. Edited October 21, 2006 by GrizzlyJohn
+geocacher_coza Posted October 21, 2006 Posted October 21, 2006 Server still down............................
+vonRichthofen Posted October 21, 2006 Posted October 21, 2006 (edited) Yeehaa server down again Server Error in '/' Application. Server Too Busy Edited October 21, 2006 by vonRichthofen
Team Baker Posted October 21, 2006 Posted October 21, 2006 (edited) Network Error (tcp_error) A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time. For assistance, contact your network support team. Wish I had been up when the server was. We don't seem to be keeping the same hours. Has anyone else experience this error? It seems less a site down error and more of a network issue. I checked the logs and the site seemed to be fine during the night. Thanks! 10/21/2006 06:30am I have been trying for an hour but just keep getting Server TOO Busy? Edited October 21, 2006 by Team Baker
+SUp3rFM & Cruella Posted October 21, 2006 Posted October 21, 2006 It's up again. Try it now, while the batteries are holding up!
+Learned Gerbil Posted October 21, 2006 Posted October 21, 2006 This is what I am currently getting returned from GC.Com- Server Too Busy Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Server Too Busy Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80004005): Server Too Busy] System.Web.HttpRuntime.RejectRequestInternal(HttpWorkerRequest wr) +146
+Chance Encounter Posted October 21, 2006 Posted October 21, 2006 I'm not even getting error messages on this end, just endless churning as the browser attempts to connect. I've tried using both Firefox 2.0 RC3 and IE7.
+Ducky Posted October 21, 2006 Posted October 21, 2006 I'm not even getting error messages on this end, just endless churning as the browser attempts to connect. I've tried using both Firefox 2.0 RC3 and IE7. I forgot I had the browser going It's been trying to get to a cache page for an hour
+michigansnorkelers Posted October 21, 2006 Posted October 21, 2006 I know that someday this site will be up again.
+programmer64 Posted October 21, 2006 Posted October 21, 2006 (edited) This is getting ridiculous! 3 days now I have been unable to get on the site! or at least intermintently. maybe it's time to start a renegade site.... Just kiddin, but my patience is wearing thin with this problem. Edited October 21, 2006 by programmer64
+Buddaman Posted October 21, 2006 Posted October 21, 2006 I'm not even getting error messages on this end, just endless churning as the browser attempts to connect. I've tried using both Firefox 2.0 RC3 and IE7. I forgot I had the browser going It's been trying to get to a cache page for an hour Same here at 8;37 est
+HaLiJuSaPa Posted October 21, 2006 Posted October 21, 2006 I'm not even getting error messages on this end, just endless churning as the browser attempts to connect. I've tried using both Firefox 2.0 RC3 and IE7. Us too at the moment
+DeRock & The Psychic Cacher Posted October 21, 2006 Posted October 21, 2006 This is getting old real fast!
+Thrak Posted October 21, 2006 Posted October 21, 2006 Network Error (tcp_error) A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time. For assistance, contact your network support team. Wish I had been up when the server was. We don't seem to be keeping the same hours. Has anyone else experience this error? It seems less a site down error and more of a network issue. I checked the logs and the site seemed to be fine during the night. Thanks! YES. I got it a buttload of times that day (and evening until I gave up trying).
+HaLiJuSaPa Posted October 22, 2006 Posted October 22, 2006 It's funny, right after I did my forum entry on this yesterday morning I tried again and it was up and been up since.
+Lil Devil Posted October 22, 2006 Posted October 22, 2006 right after I did my forum entry on this yesterday morning I tried again and it was up and been up since. Thanks for fixing it!
+CaspianJVC Posted October 24, 2006 Posted October 24, 2006 Site down??? it just sits there loading for me. No server error.
+Amtraker Posted October 24, 2006 Posted October 24, 2006 Site down??? it just sits there loading for me. No server error. Tue Oct 24, 2006 2:17 AM PDT same problem for me. Page says loading but nothing shows up. After a LONG time it finally aborts with: The connection to the server was reset while the page was loading.
+Cache Liberation Front Posted October 26, 2006 Posted October 26, 2006 Servers fall down go BOOM again? MrW.
+wsgaskins Posted October 26, 2006 Posted October 26, 2006 It's up and down intermittently for me.... more like those danged internet tube must be clogged again. Who's been betting on them horses?
+Cache Liberation Front Posted October 26, 2006 Posted October 26, 2006 It's up and down intermittently for me Ah, in the IT world I think they call that the "Lewinsky Syndrome." MrW.
+Jeremy Posted October 26, 2006 Posted October 26, 2006 We're tweaking the applications so they don't recycle as often as they used to when we relied more on in-memory storage. Translation: We made some changes this hour to clear it up a bit.
Jeepstr Posted October 26, 2006 Posted October 26, 2006 Got it. Yes I just had this problem about 5 minutes ago
+kayak-cowboy Posted October 27, 2006 Posted October 27, 2006 Still down? This is the message I get when trying to get to Geocaching.com. 8:50pm Eastern Daylight time. Server Error in '/' Application. Server Too Busy Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Server Too Busy Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80004005): Server Too Busy] System.Web.HttpRuntime.RejectRequestInternal(HttpWorkerRequest wr) +146 Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
+Okiebryan Posted October 27, 2006 Posted October 27, 2006 I can only imagine what it must be like to be a volunteer reviewer and have a que of caches waiting to be approved when the site is pulling a Monica Lewinski. Probably makes for some VERY long and frustrating nights.
+PeterNoG Posted October 27, 2006 Posted October 27, 2006 I've been getting "server busy" for about the last half hour.
+Team Four Paw Posted October 27, 2006 Posted October 27, 2006 I'm assuming that would be to store all the error logs... cause I don't think that would fix the application...
+trippy1976 Posted October 27, 2006 Posted October 27, 2006 I can only imagine what it must be like to be a volunteer reviewer and have a que of caches waiting to be approved when the site is pulling a Monica Lewinski. Probably makes for some VERY long and frustrating nights. Nah, they just have a [insert beverage of choice], catch up on some [insert favorite show on TIVO] episodes and wait patiently for it all to be right again.
+mtn-man Posted October 27, 2006 Posted October 27, 2006 I can only imagine what it must be like to be a volunteer reviewer and have a que of caches waiting to be approved when the site is pulling a Monica Lewinski. Probably makes for some VERY long and frustrating nights. Amazingly, I did a quick run through on a bunch of caches right in the window when the site was up late this afternoon. I had actually been oblivious to the site being down some today, pulled up the queue and went to work. It was lightning fast when I was working. Again, oddly enough, I left work to hit the 6:30 PM EDT Fed Ex drop box. Sorry, I guess my flurry of reviewed caches broke the server. I am sure it is frustrating to those that got cache notifications only to find the site down.
+Mr Lost Posted October 27, 2006 Posted October 27, 2006 Here is what I get (Copy and Paste): Server Error in '/' Application. Server Too Busy Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Server Too Busy Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80004005): Server Too Busy] System.Web.HttpRuntime.RejectRequestInternal(HttpWorkerRequest wr) +146 Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
+mtn-man Posted October 27, 2006 Posted October 27, 2006 I can only imagine what it must be like to be a volunteer reviewer and have a que of caches waiting to be approved when the site is pulling a Monica Lewinski. Probably makes for some VERY long and frustrating nights. Nah, they just have a [Heineken], catch up on some [Eye for an Eye (Judge Extreme Akim)] episodes and wait patiently for it all to be right again. Filled in the blanks. Dude, do you have cameras in my house?
Recommended Posts