Home » Community » Forum Listing » Technical Support »
server is slow
Along with the even more ominous:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
D:\USR\RUBBERSLUG.COM\BOARD\../image_handle.asp, line 30
Sensei turns blue, then is lost from sight behind a curtain of sweatdrops.
Don't panic! It's not as bad as it seems, trust me.
Look on the bright side:
a) No data will be lost. I can see the database from my computer and everything is there, I just can't reboot it from my computer right now (normally, I can).
b) I'm even surprised that the database still works well enough to run this forum. When it crashed, I was thinking the whole thing just turned off and no one would be able to hit the site for a few days.
c) It'll be back and faster than ever. I was optimizing the site right before it crashed. Did a pretty good job before the whole thing just cratered on me. I was working on the ability to use the search box to look at actual cels.
e) A reboot should fix everything. If it doesn't, then commence sweatdrops for comic effect.
f) This event will certainly result in another amusing voting poll. The lobster machine will, again, be an option somehow.
Man, right after I wrote a message saying about how this server is an old piece of junk. I think it heard me and it's just getting back at me.
I posted a message on the cels.org forum about this. Here's a summary:
- updating now will work, mostly, but it's not a good idea since the database randomly fails to respond.
- nothing really permanently bad will happen to any work you did on your site before sunday.
Sorry for the inconvenience. It's been a long day.
The site is working great for me now, so I guess the reboot was successful? It's faster too, my gallery has NEVER loaded this fast. ^_^
It's faster because I was making a lot of changes right before the crash, but we have NOT rebooted the thing yet. I'll post a message when it's done. The only reason I've left the site running at all is that it seems to only fail under high traffic right now.
We just finished with our real life work at 6 AM, so I think we should be able to get the server running in top condition again by this afternoon. (i.e. - regardless of traffic load, no more silly database errors)