phpBB : Critical Error
Admin Emeritus
SL Member
Joined: Jan 2005
Posts: 14,570
From: University Place, WA
Yeah, SL and IB were both down at the same times (and oddly I was getting no answer to phone calls, either), so this may have been more than someone just deciding to do some unscheduled maintenance on the live servers...
Hopefully we will get some answers, and will be able to pass them on to you.
Hopefully we will get some answers, and will be able to pass them on to you.
Admin Emeritus
SL Member
Joined: Jan 2005
Posts: 14,570
From: University Place, WA
Michael Anders at InternetBrands.com wrote:
Today’s site downtime was caused by a rather large hardware failure – it had absolutely nothing to do with maintenance or anyone tinkering with anything else – it really was unexpected...
Today’s site downtime was caused by a rather large hardware failure – it had absolutely nothing to do with maintenance or anyone tinkering with anything else – it really was unexpected...
Senior Member
SL Member
Joined: Aug 2006
Posts: 1,906
From: N38° 37', W90° 17'
Ugh. I'm getting this error again, and hard. It took about 10 refreshes just to get here.
Originally Posted by kb.siteground.com
I am receiving phpBB: Critical Error Could not connect to the database error.
This error means that you have not configured your PhpBB's database settings properly. Revise the configuration file of phpBB which is config.php located in the directory where your forum resides.
This error means that you have not configured your PhpBB's database settings properly. Revise the configuration file of phpBB which is config.php located in the directory where your forum resides.
Originally Posted by phpbbstyles.com
Then either of the following may be true;
1. The database connection information in 'config.php' is wrong.
2. The database service on the server is not running.
1. The database connection information in 'config.php' is wrong.
2. The database service on the server is not running.
Senior Member
SL Member
Joined: Aug 2006
Posts: 1,906
From: N38° 37', W90° 17'
Dear IB,
Please either fix the database configuration, or improve your fail-over/redundancy between database servers. Random site-wide downtime is unacceptable.
Sincerely,
Users of ScionLife
Please either fix the database configuration, or improve your fail-over/redundancy between database servers. Random site-wide downtime is unacceptable.
Sincerely,
Users of ScionLife
Admin Emeritus
SL Member
Joined: Jan 2005
Posts: 14,570
From: University Place, WA
Dogbert, we are getting their attention more these days, and not only getting quicker responses, but are building a better relationship with the folks there.
For example, this morning (Pacific time) it took about a half hour from my initial report to their getting the problem under control (11:26 reported, 11:53 cleared).
I don't know what was done to clear the problem (and I'm not sure they are sure yet of the cause), but we are getting much better response now than we were in the recent past.
For example, this morning (Pacific time) it took about a half hour from my initial report to their getting the problem under control (11:26 reported, 11:53 cleared).
I don't know what was done to clear the problem (and I'm not sure they are sure yet of the cause), but we are getting much better response now than we were in the recent past.
Senior Member
SL Member
Joined: Aug 2006
Posts: 1,906
From: N38° 37', W90° 17'
Well, I guess my only gripe about this entire situation is that it's still unresolved when they keep saying "oh, it's fixed now." You just don't do that, especially when you apparently don't even know what's wrong or what to fix.
Granted, I have absolutely no idea how SL's back-end works, and I can only hazard shot in the dark guesses because I work for a hosting company myself, but I would guess that there's a database server in a distributed environment that's going down and hosing the entire site. If this is the case, then the environment needs stronger fail-over options and better redundancy, plain and simple. If it's a case of a bad configuration file, then it needs to be fixed.
Where's that angry shaking Tomas smiley...
Granted, I have absolutely no idea how SL's back-end works, and I can only hazard shot in the dark guesses because I work for a hosting company myself, but I would guess that there's a database server in a distributed environment that's going down and hosing the entire site. If this is the case, then the environment needs stronger fail-over options and better redundancy, plain and simple. If it's a case of a bad configuration file, then it needs to be fixed.
Where's that angry shaking Tomas smiley...
