So I deployed my MODx site to my hosting provider following the instructions in the documentation -- I dumped a backup of my dev server’s SQL db, uploaded everything to the host, restored the SQL dump onto the host, and now.. pain.
When I attempt to log into the manager, rather than the manager window, I get a Javascript error popup containing the HTML code of the 500 Internal Server Error page.
In my server’s error_log, the error is reported as:
[Mon Feb 12 15:25:29 2007] [error] [client <redacted>] Premature end of script headers: login.processor.php, referer: http://<redacted>/manager/index.php
[Mon Feb 12 15:25:29 2007] [error] [client <redacted>] PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 1818107 bytes) in /home/<redacted>/html/manager/includes/document.parser.class.inc.php on line 1287, referer: http://<redacted>/manager/index.php
[Mon Feb 12 15:25:29 2007] [error] [client <redacted>] Allowed memory size of 8388608 bytes exhausted (tried to allocate 10 bytes), referer: http://<redacted>/manager/index.php
I’ve not seen this before. Any idea what’s causing it and what I should tell my hosting provider to get it fixed?
[edit: added more detail, clarified title.]
Appologies, Ryan.
I have minimal config information about the server from my provider, but I can tell you it’s a CentOS 4 server running php via suphp. Versions are as follows:
apache 2.0.52
MySQL 4.1.20
PHP 4.3.9
Browser is Safari 2.0 on OS 10.4.8. MODx is 0.9.5, only non-standard plugin is PHx, but everything’s working fine on my local MAMP server.
I do not have direct access to php.ini for the host, but the host seems willing to work with me and make config changes when needed.
-
☆ A M B ☆
- 24,524 Posts
You certainly have phpMyAdmin on your MAMP server, and it’s easy enough to install on your remote server; you can even protect its installation directory or simply remove it when you are done.