WHM apache settings break website

[mealto]

So we tried to edit apache settings inside WHM and when we click save, it broke parts of our website. The error message was the usual file not in proper location (php error). Not sure of the exact wording but it's the message that you receive when you use php include to include a file and it's not in the right location. Had to quickly revert back to the httpd.conf file and add keepalive, etc... manually. Any ideas what happened here?

 

[Infopro]

What settings did you change?

 

[mealto]

Just the keepalive, tiemout settings. Noticed these settings are no longer in our httpd.conf file, we used to do this manually. Maybe a more recent update of WHM took control of this and removed it? So tried to add this back.

 

[Infopro]

That setting is located here.
WHM » Service Configuration » Apache Configuration » Global Configuration

 

[mealto]

Yes, that was where we made the changes and broke something so php include did not work. Not sure why so asking here.

 

[JaredR.]

What is the exact change that you made, and what is the exact error message you saw as a result? Can you copy and paste the error message? Without knowing the exact change that was made, and the exact error message that resulted, it is difficult to even guess as to what happened.

 

[mealto]

We changed these values:

Timeout 30
ServerLimit 256
MaxClients 150
MaxRequestsPerChild 10000
KeepAlive On
KeepAliveTimeout 10
MaxKeepAliveRequests 1000

After saving, all our websites loaded fine except for the php include error. I don't remember the exact error and cannot find one on the web that I can copy here. It's the same error that you receive when you use php include to include a file that does not exist. We use php include on some parts of our website.

We do have nginxcp installed and have instructed it to pass .html files to apache since some of our php code runs inside .html. Something seems to tell me that this may have been the issue here.

Any ideas?

 

[Infopro]

Just the keepalive, tiemout settings. Noticed these settings are no longer in our httpd.conf file, we used to do this manually. Maybe a more recent update of WHM took control of this and removed it? So tried to add this back.

So if you changed this and saved, again, the website will break, again?