After create an new account the apache settings are reset

[DevBreak]

Hello,
Another bug in whm destroy my live.
I have custom settings in apache httpd.conf (maxclients, keepalive , etc..) after i create an new account in whm this settings are gone and replaced with default. In this case the default settings are not good for me.

What can i do?

Apache 1.3.39 EA3
RHE4 & FedoraCore 5 - same problem .

Waiting for an urgently solution...

[cpanelkenneth]

Make your changes to httpd.conf, then run /usr/local/cpanel/bin/apache_conf_distiller --update --main

it should preserve your settings then.

[verdon]

Make your changes to httpd.conf, then run /usr/local/cpanel/bin/apache_conf_distiller --update --main

it should preserve your settings then.

Can you explain (just a little) what that does? It sounds as if apache conf settings are actually being set somewhere else?

[cpanelkenneth]

In brief, we have consolidated all management of httpd.conf into a "cPanel" database, found in /var/cpanel/useradata apache_conf_distiller is used to create and maintain that data. httpd.conf is rebuilt based upon that data. We don't recommend modifying the data in /var/cpanel/userdata

[verdon]

Thanks, that's what I was looking for.

[verdon]

So a new protocal would be to run /var/cpanel/useradata apache_conf_distiller whenever any manual edit is done to httpd.conf?

[cpanelkenneth]

So a new protocal would be to run /var/cpanel/useradata apache_conf_distiller whenever any manual edit is done to httpd.conf?

You need to run it with --update --main, otherwise it won't do anything.

Otherwise, correct. After making changes to the global values, run:

/usr/local/cpanel/bin/apache_conf_distiller --update --main

to preserve the changes.

[Rafaelfpviana]

was this suppose to keep the modified or added values that where added between <VirtualHost></VirtualHost> ????

[cpanelkenneth]

No, changes to VirtualHost will not be preserved. Those changes need added to /usr/local/apache/conf/userdata/std/<apache version>/<user name>/custom.conf

The file doesn't actually need to be named customer,conf, as long as it end with .conf

After adding such a file, run:

perl /scripts/ensure_vhost_includes

once that is done, the Include directives will be added to the vhost and retained across httpd.conf regenerattions.

On a side note, there is a bug in 17046 (Current and Edge) that causes the httpd.conf be regenerated by anything that modifies the httpd.conf. Thus, adding a subdomain will cause the entire file be regenerated. This will be fixed in the next build.

[thedavid]

No, changes to VirtualHost will not be preserved. Those changes need added to /usr/local/apache/conf/userdata/std/<apache version>/<user name>/custom.conf

The file doesn't actually need to be named customer,conf, as long as it end with .conf

After adding such a file, run:

perl /scripts/ensure_vhost_includes

once that is done, the Include directives will be added to the vhost and retained across httpd.conf regenerattions.

On a side note, there is a bug in 17046 (Current and Edge) that causes the httpd.conf be regenerated by anything that modifies the httpd.conf. Thus, adding a subdomain will cause the entire file be regenerated. This will be fixed in the next build.

This would've been good as part of documentation, or maybe included in the changelog or something. This is the first I've seen of it, and this was after doing some searching.

Also, how would this work if I wanted to say, change the secure web path for a domain? Rather than serving the pages from /home/username/public_html/ the client would like it served from /home/username/secure_html/

In what way is this possible?

[Rafaelfpviana]

kenneth, i didn't find /usr/local/apache/conf/userdata/std/<apache version>/<user name>/custom.conf, in fact /usr/local/apache/conf/userdata doesn't exist for me.

By the way, would this be the correct way:

perl /scripts/ensure_vhost_includes  --all-users

[mtech-hosting]

Is this distiller something that cpanel came up with or is it new to apache? This seems like an aweful lot of work just to make a few changes here and there and i can see it leading to a whole slew of problems

[cPanelBilly]

Is this distiller something that cpanel came up with or is it new to apache? This seems like an aweful lot of work just to make a few changes here and there and i can see it leading to a whole slew of problems

This is a cPanel thing and it is needed because of the multiple apache versions

[thedavid]

This is a cPanel thing and it is needed because of the multiple apache versions

Does this reply mean that there's no way of making the changes I mentioned above?

[JamieD]

No, changes to VirtualHost will not be preserved. Those changes need added to /usr/local/apache/conf/userdata/std/<apache version>/<user name>/custom.conf

The userdata directory does not exist on my system, if this is manually created will cPanel pick it up, for instance if I created:

/usr/local/apache/conf/userdata/std/1.3/a_user/custom.conf

then ran perl /scripts/ensure_vhost_includes