Changing config.inc.php file has caused 500 internal server error

Hi,

Has anyone had this problem before or know how to fix it?

After changing the content of the config.inc.php file (i.e. to change database name etc) it has caused a 500 internal server error which means that although the website works when you type it in directly, Google is not finding it and therefore not listing it (wget http://www.goopticians.com also generates the error). Even if you copy back the original file it still causes the error. It is on a server that my Father runs so we have full (remote) access to it and we have other Modx websites that are all working fine on it.

The website it www.goopticians.com.

Thanks in advance

Version of MODx,: modx-1.0.5
Server OS: Ubuntu Server
Server Version: Apache 2.2.14
PHP Version: 5.3.2
MySQL Version (client and server) : 5.1.41
is pdo_mysql installed: No
your Browser type and version: IE8
if you are using any opcode caching such as eAccelerator, APC, winCache, xCache, etc: No
any relevant errors in core/cache/logs/error.log: PHP Parse error: syntax error, unexpected ’<’ in /var/www/perrigo/manager/includes/document.parser.class.inc.php(746) : eval()’d code on line 1
and any other environment data we should know.: N/A

You likely saved the file with a UTF-8 BOM at the beginning of the file. Resave it without this and it should solve the issue.

Quote from: OpenGeek at Mar 13, 2011, 12:05 PM

You likely saved the file with a UTF-8 BOM at the beginning of the file. Resave it without this and it should solve the issue.

Thanks for the suggestion but this hasn’t solved the problem. The file was edited on the server so shouldn’t have effected this but we checked anyway and it hasn’t. Any other suggestions? We’re thinking it could be a problem with the server itself so if all else fails we’ll be completley rebuilding it this weekend!

On further investigation today we have found that that every time the site is accessed (by a remote user with their browser) the number of instances of Apache increases by 3. These processes never die so over a period of time keep increasing until the server stops responding. Apache directives are all standard and work on other installations. Other sites on this server do not cause the problem, even those which use Modx. Really baffled by this, any help would be much appreciated.

Hi Pinky
Did you find the cause of this bug ?
I'm new to modx and I need to help a friend which has the same bug on his website.