[Case 48712] Joomla White Screen Caused by httpd.conf
A few months ago I had an issue that all my Joomla sites did not function (white screen on public and administrator), I finally found out that after clicking on proceed for this option:
Home " Service Configuration " Apache Configuration " Memory Usage Restrictions
Two line of code were added to /usr/local/apache/conf/httpd.conf
RLimitMEM 146724864
RLimitCPU 240
The above killed all the Joomla sites on my server but standard HTML pages were fine.
Once the above lines are removed then everything works fine.
More recently after WHM/cPanel updates the following lines keep getting added every few weeks:
RLimitMEM 146724864
RLimitCPU 240
I need to edit and remove via SSH or roll back the system file to a version without the above lines.
Please advise how I stop this happening.
Steve.
-
Hello :) Ensure you run the Apache distiller after commenting out those lines in the httpd.conf file to ensure the changes are preserved: Apache Distiller Thank you. 0 -
Ok thanks I'll take a look. The version of the file first time was 1.27, then up to 1.32 were ok, then the lines popped in again, then 1.34 0 -
The link just appears to take me to an unrelated page and I can't find anything like that in my WHM 0 -
I ran this command, and it did some 'stuff' /usr/local/cpanel/bin/apache_conf_distiller --update 0 -
I'm not sure why that document would not load correctly for you... what document does it send you to? The task you are trying to accomplish requires that you use the command line, so you won't find the distiller in WHM. As described in the document that Michael linked: If you must modify your httpd.conf Apache configuration file directly, perform the following steps: Make the necessary changes to your httpd.conf file. Run the Apache configuration distiller script as the root user with the following command: /usr/local/cpanel/bin/apache_conf_distiller --update The Apache configuration distiller script does not make changes to your Apache configuration. The distiller script updates the datastores in the /var/cpanel/userdata directory. The Apache configuration distiller script does not guarantee that cPanel & WHM will not overwrite your direct modifications to your httpd.conf file. To test whether cPanel & WHM will overwrite your modifications, perform the following steps: Create a copy of your httpd.conf file with your direct modifications. Run the /scripts/rebuildhttpdconf script to rebuild your httpd.conf file. If your changes are still present in your httpd.conf file, then cPanel & WHM will not overwrite your modifications. This does not guarantee that the lines will not be added back, but in most cases it will prevent it. 0 -
I do want to point out that internal case number 48712 is open to update the page used for "Memory Usage Restrictions" so that it includes a warning and instructions for removing the entries that are added to the Apache configuration file. Please feel free to monitor our change log for this case number: cPanel - Change Logs Thank you. 0 -
I did the above steps i.e. update and ran distiller. However this morning the line were automatically added again and Joomla sites stopped working again. Currently rolled back file from 1.35 to 1.34. 0 -
[quote="iamSR, post: 1712291">I did the above steps i.e. update and ran distiller. However this morning the line were automatically added again and Joomla sites stopped working again. Currently rolled back file from 1.35 to 1.34.
Are you sure that "WHM Home " Service Configuration " Apache Configuration " Memory Usage Restrictions" was not accessed again, or are you the only person who uses this server as "root"? Thank you.0 -
I am the only person who has access to WHM as root 0 -
Could you open a support ticket using the link in my signature so we can review your server and verify those entries were not added some other way, or that your changes to the httpd.conf were configured properly? You can post the ticket number here so we can update this thread with the outcome. Thank you. 0 -
Ticket has now been submitted. 0 -
[quote="iamSR, post: 1714992">Ticket has now been submitted.
Please post the ticket number here so we can update this thread with the outcome. Thank you.0
Please sign in to leave a comment.
Comments
12 comments