forums | blogs | polls | tutorials | downloads | rules | help
Home-> forums-> Off Topic-> General Chatter

What happened to Herena Forge?

Submitted by sol77 on Mon, 2007-05-28 11:33

Been gone for a while and just came back to check on my DS sites.
So did the link change to HF or is the DNS server I use hacked?

This is what I got..

forums: 
General Chatter
»
Sharkull's picture
Submitted by Sharkull on Tue, 2008-05-20 14:50

Quote:
TikiWiki is not properly set up:

Unable to connect to the database !

Go here to begin the installation process, if you haven't done so already.

Too many connections
»
Submitted by PhoeniX on Tue, 2008-05-20 15:23

I get that occasionally, but the site usually returns within a reasonable period of time.
»
Submitted by ghastley on Wed, 2008-06-11 16:44

I notice that recently the forge just doesn't respond when it's being hormonal, instead of getting the "Not set up" error, which seemed to be its fave problem before.

I suspect the DB problem was due to not releasing concurrent threads whenever there was a failure, which could be because of max threads in use, so if it got too busy it died. It may be that fixing that lets it hit a monthly bandwidth limit or something like that.

I know this site uses Drupal instead of TikiWiki, and probably a different database, but maybe Sol can comment on the database failure modes he's seen?
»
Sharkull's picture
Submitted by Sharkull on Thu, 2008-06-12 02:32

Database problems could be caused by some form of corruption (bad file, missing key data, disk error...) or a logical issue (tables bloated with orphaned rows, inefficient queries, overdue routine db logfile purging...). The thing is, these problems should throw ODBC errors as long as the database service provider is still running. Of course if the service is busy processing, the errors may not show up before the web service times out on the query. Then I'd expect to see a proper error page served (like the "not set up" error you mentioned). So, when there is no error message at all, I suspect one of two things:
1. Host problems / throttling / server unavailability.
2. Problems with the page scripts (TikiWiki) causing a memory leak or the web service to lock-up and be unavailable for processing requests.

Without access to server logs for troubleshooting, I doubt there is much more that could be said...
»
Submitted by sol77 on Fri, 2008-06-13 07:38

ghastley wrote:
I know this site uses Drupal instead of TikiWiki, and probably a different database, but maybe Sol can comment on the database failure modes he's seen?

I don't know enough about databases to be of any help there, I rely on the folks I'm buying the hosting from to keep things working.

But learning more is always good so if you told me what to look for I could see what I can dig up. First I will go check to see what logs are available to me though..
»
Submitted by PhoeniX on Fri, 2008-08-01 14:13

Been down for several days now. Hope OC hasn't pulled the plug. Sad

Edit: Probably hasn't pulled the plug because Scourgeweb is down also. :?
»
Submitted by ghastley on Fri, 2008-08-01 15:28

At this time of year, maybe OC's on vacation, so hasn't noticed. I'm not sure if there are any "deputies" to take over and fix anything.
»

Pages