focuslabllc/ee-master-config

A Database Error Occurred

Opened this issue · 3 comments

rickprince commented

We've been getting this issue intermittently after each new deployment (using springloops.io for git to ftp). I can't seem to pinpoint exactly what the issue is, it doesn't seem to be url specific as I get the same error no matter what urls I visit, including admin.php. The error:

A Database Error Occurred
Unable to connect to your database server using the provided settings.

Filename: core/EE_Config.php

Line Number: 207

And .htaccess just in case:

<IfModule mod_rewrite.c>
        RewriteEngine On
        # Removes index.php from ExpressionEngine URLs
        RewriteCond $1 !\.(gif|jpe?g|png)$ [NC]
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^(.*)$ /index.php?/$1 [L]
</IfModule>

Any clues to how I can troubleshoot?

iso100 commented

Make sure your environment is configured properly and that the expected
environment is being activated there.
On Oct 18, 2013 4:21 AM, "rickprince" notifications@github.com wrote:

We've been getting this issue intermittently after each new deployment
(using springloops.io for git to ftp). I can't seem to pinpoint exactly
what the issue is, it doesn't seem to be url specific as I get the same
error no matter what urls I visit, including admin.php. The error:

A Database Error Occurred
Unable to connect to your database server using the provided settings.

Filename: core/EE_Config.php

Line Number: 207

And .htaccess just in case:

RewriteEngine On # Removes index.php from ExpressionEngine URLs RewriteCond $1 !.(gif|jpe?g|png)$ [NC] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /index.php?/$1 [L]

Any clues to how I can troubleshoot?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/28
.

rickprince commented

I assume the right environment is being activated, but I couldn't be sure as the error stops me from logging in. Is there a way I can tell which config file is currently active? I thought it might be a database connection issue (remote host might have some weird mysql setup or something) but then I noticed the same error on my local MAMP setup.

Should I set debug settings to true inside config.master.php so I can see some output? If so, which one?

erikreagan commented

@rickprince I suggest you open the env.config.php file and at the bottom add in exit(ENV); to see what environment is getting triggered.