Thread:Project:Support desk/old mysql database resulting in Cannot contact the database server/reply (2)

Well, that's the weird thing.

I looked at all the settings in the LocalSettings from my March2014 archive - especially $wgDBuser	  $wgDBpassword	     and made sure they were matched.

Now I tried to actually copy over the LocalSettings from March2014 to my new install to see what would happen. Interestingly enough, I started seeing it trying to do "Login Required" then "Waiting" and finally getting to HTTP 500 Internal Server Error, not the (cannot contact the database server)

Ok, let me be thoroughː There are various differences between this LocalSettings file and the old one.

The old LocalSettings Contains (but the new one doesn't)ː $wgGroupPermissions['*']['read'] = false; $wgWhitelistRead = array ("Special:Userlogin", "MediaWiki:Common.css", "MediaWiki:Common.js", "MediaWiki:Monobook.css", "MediaWiki:Monobook.js", "-"); $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['createaccount'] = false;
 * 1) Disable reading by anonymous users

The new LocalSettings contains (but the old one doesn't)ː

require_once "$IP/skins/Vector/Vector.php"; ... $wgPhpCli = "C:/Bitnami/mediawiki-1.24.1-0/php\php.exe";

Ah... Found one important difference - done due to my tired state, no doubt.

$wgDBname          = "mediawiki_bitnami"; I accidentally reversed it to "bitnami_mediawiki" in the new LocalSettings.

So, now at least I get HTTP 500 page with the new LocalSettings.

I also don't know if this matters

Old LocalSettingsː $wgSitename     = "Fred's Wiki!"; $wgMetaNamespace = "Fred's Wiki!";

new LocalSettingsː $wgSitename     = "fred's Wiki!"; $wgMetaNamespace = "fred's Wiki!";

Certainly, no difference either way.

so, how would I now troubleshoot HTTP500?