Jeremy Posted October 27, 2004 Share Posted October 27, 2004 We will be down for between 1-2 hours this evening. Details here Link to comment
Jeremy Posted October 27, 2004 Author Share Posted October 27, 2004 Oh. Forums will remain online since they are not affected by the database changes, though some links from here will not work if they link back to geocaching.com (like profiles) Link to comment
+TotemLake Posted October 27, 2004 Share Posted October 27, 2004 Thanks for the heads up! Link to comment
+CompuCash Posted October 28, 2004 Share Posted October 28, 2004 thanks for the notice and thanks for the added hardware - you guys rock! Link to comment
Keystone Posted October 28, 2004 Share Posted October 28, 2004 -- BUMP -- Good luck with the update! Link to comment
+planetrobert Posted October 28, 2004 Share Posted October 28, 2004 keep up the good work, and also get some rest tonight so you can go caching tomarrow... ...and pray that everything works till you get back. Jeremy, YOU ROCK!!!!!!! Link to comment
+haggaeus Posted October 28, 2004 Share Posted October 28, 2004 ok it looks the db is being brought up. Just got an interesting error: Cannot open database requested in login 'ASPState'. Login fails. Login failed for user 'sa'. Now, I have never worked with MS SQL server, but I remember it is based on Sybase and 'sa' is the Sybase superuser account... does it mean the website is accessing the db with db administrator privileges? Just curious. Link to comment
+TeamEimi Posted October 28, 2004 Share Posted October 28, 2004 (edited) Hi, the DB server update seems to have significantly improved the performance (atleast for now, maybe the load is not even close to 100% yet). Anyway, even from the other side of the planet pages load now in a flash. Thank you for this. One comment though. It seems there is currently lot of caching going on. Unless the final aim (and actual state is that (page)cache is refreshed EVERY TIME when live data changes, then it would benefit both the server and users if there was a little notification about the delay...(people are always eager to see instantly the latest logging, image, cache description or little thingy that they just uploaded). Anyway, as your DB is apparently read-mostly, I assume you can reach that refresh per every update state and this slight annoyance will not happen anymore. Thanks, dad@teameimi Edited October 28, 2004 by TeamEimi Link to comment
+Markwell Posted October 28, 2004 Share Posted October 28, 2004 Heheh... 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 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032 Link to comment
+Moose Mob Posted October 28, 2004 Share Posted October 28, 2004 Heheh... 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 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032 I had that also... as well as a couple "page not found" errors. It went away pretty quick though and haven't seen it since. Link to comment
Elias Posted October 28, 2004 Share Posted October 28, 2004 Heheh... Server Error in '/' Application. Markwell - What page did that happen on? Elias Link to comment
+ZackJones Posted October 28, 2004 Share Posted October 28, 2004 Markwell: FWIW, the error you posted is from the web server, not the database server. Zack Link to comment
+Markwell Posted October 28, 2004 Share Posted October 28, 2004 What page did that happen on? Heheh... Illinois State search page from advanced. It then cleared itself later. I've been getting partial responses from various pages all day long. Sometimes they work, others I get a message similar to the one above. ================================== I'm also getting an error searching for a travel bug by keyword: Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. Link to comment
+Markwell Posted October 28, 2004 Share Posted October 28, 2004 And again just now with a travel bug... The Batmobile Link to comment
Jeremy Posted October 28, 2004 Author Share Posted October 28, 2004 We had to wait a bit for our database replication to set itself up again. This will (hopefully) fix the server too busy errors. Elias also updated some configuration files on the web servers which will help. Link to comment
Jeremy Posted October 28, 2004 Author Share Posted October 28, 2004 I'm also getting an error searching for a travel bug by keyword: Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. Since I did a lousy job with the search engine for travel bugs, I went ahead and set it back up to do a 'like' search on the travel bug name. Link to comment
Recommended Posts