Database Error

Permalink
I was working on a site yesterday and all was fine but when I came in this morning I had this error:

Catchable fatal error: Argument 1 passed to ConfigStore::__construct() must be an instance of Database, null given, called in D:\Hosting\5063581\html\concrete\models\config.php on line 48 and defined in D:\Hosting\5063581\html\concrete\models\config.php on line 136

I upgraded to the latest release from 5.4.2 yesterday before I started making edits so don't know if this has anything to do with it.

Any help appreciated as this is a pretty big week for the client and they need their site up.

PassionForCreative
 
GregJoyce replied on at Permalink Reply 1 Attachment
GregJoyce
Hi Stephen, any chance you can get us the environment info for this site? Failing that, can you post a phpinfo()?
You can upload the attached file to like, [site root]/phpinfo.php and it will come back with the right information.
GregJoyce replied on at Permalink Reply
GregJoyce
Also can you verify that the settings in config/site.php are correct and that you can connect to the db with them?
allcomm21 replied on at Permalink Reply
I am having a similar problem when I try to log in to my site. Getting an error message:
mysql error: [1054: Unknown column 'uDefaultLanguage' in 'field list'] in EXECUTE("select uID, uName, uIsActive, uIsValidated, uTimezone, uDefaultLanguage from Users where uName = 'admin' and uPassword = '8aaefd95c9b60a30f1637da2aa6a9529'")

I also updated Concrete earlier today. And I installed the Database Manager add-on. (although it didn't work when I tried it)

Any help or suggestions would be much appreciated. I can't log on, so I don't have my environment.
triplei replied on at Permalink Best Answer Reply
triplei
any chance you can go to
yourdomain.com/index.php/tools/required/upgrade and see if there is a database migration which still needs to run?

it looks like there column missing on your user table.
allcomm21 replied on at Permalink Reply
That did it. Thanks!
CasaViewAG replied on at Permalink Reply
CasaViewAG
i was having a similar problem with a database error and i just reran the script form here even though it said i was up to date and vala, problem solved. thanks
PassionForCreative replied on at Permalink Reply
PassionForCreative
It was just a case of Godaddy being Godaddy. No warning email to say that they were going to be doing system maintenance or anything? Just a site that was down for about 5 hours.

By the time business hours on the East Coast of the US came round the site came back up. We moved hosts though becasue we can't afford that to happen again.
Pixelfixer replied on at Permalink Reply
Pixelfixer
Stephen, did Godaddy give you any indication of what they did to cause this problem? I am getting exactly the same error, first reported by my client's customer saying the site is down and reporting errors. I have no idea what could have caused this nor how to resolve it. I am suspicious of my provider, Netfirms, (whom I have already begun migrating my sites from) since I know they have been doing excessive maintenance on my shared server due to email server issues (unrelated to me).

Anyway, if you or anyone else has an idea for me on how I could get my clients site back up without having to redo everything, I'd really appreciate it!
PassionForCreative replied on at Permalink Reply
PassionForCreative
Hi Pixelfish,

Nothing, not even an acknowledgement of break of service as far as I'm aware. I had suggested to the client thatthey move their hosting away from GoDaddy before we put the site live but this forced their hand.

They are hosted on FullFlavourMedia's Concrete5 specific shared hosting now. These boxes are tuned for C5 so you can turn on the APC opcode for increased site speed. I'm directing larger or more complex sites this way now. About $100 per year instead of the small money you pay for GoDaddy but worth it if you don't lose a day here and there sorting out issues for clients that aren't of your making.
Pixelfixer replied on at Permalink Reply
Pixelfixer
I finally got it fixed, thanks to the info found throughout this forum and multiple trial & error attempts. The root cause turned out to be a failed upgrade attempt from a 5.3.x version to 5.4.2.2. It appears the upgrade does not complete. So, in finding the instruction to use "http://www.yoursite.com/index.php/tools/required/upgrade.php" to complete the upgrade was the answer to my problem. Unfortunately, I tried a few other things first which made my problem worse. I finally went through the upgrade script to get back to my original error screen and then initiated the upgrade.php command. I thought I should log this to hopefully save someone else the hassle.
1PLM replied on at Permalink Reply
Hi,
I have been getting database connection errors on my host's webserver. Everything on my ConC5 site worked and looked good until Now all my domains under Concrete5 on the server throws the following error below. How do I Fix this as 5 domains are Now Under Water....

Catchable fatal error: Argument 1 passed to ConfigStore::__construct() must be an instance of Database, null given, called in /usr/local/4admin/apache/vhosts/MyWebsite.com/concrete5.4.2.2/concrete/models/config.php on line 48 and defined in /usr/local/4admin/apache/vhosts/MyWebsite.com/concrete5.4.2.2/concrete/models/config.php on line 136
allcomm21 replied on at Permalink Reply
I am absolutely no expert like some of these guys (thank goodness for them), and please forgive this elementary stab at a solution... but when I've gotten errors like this, the basic problem is that your site is no longer connected to your database at your hosting company. The error message looks like a nightmare, but it's really not that complicated. You may just have to re-establish the database connection. Sometimes you have to give your site "permission" to access the database, which you do through the cpanel at the host. You may want to look at the config/site.php file to make sure it's got the right name and password for the database. BUT... if it's affecting several sites, and it started all at once, it could be a server issue, and you should check with the hosting company.