Automatically create proxy subdomain DNS entries in WHM.
This can be enabled on the Tweak Settings page.
Enabling this option will allow WHM to automatically create DNS entries for the following 4 subdomains for every user’s account (where example.com stands for the user’s domain):
* cpanel.example.com
* webmail.example.com
* webdisk.example.com
* whm.example.com
These subdomains allow users to easily access the features included with a cPanel installation.
We can use /scripts/proxydomains to create DNS entries manually.
Reference: http://cpanel.net
Problem importing one of the Python modules required to run yum
Error: There was a problem importing one of the Python modules required to run yum. … Cannot allocate memory.
Solution: Python frequently runs into the memory limits set inside WHM and cPanel. You may be able to resolve this issue by increasing the per process memory limit in the WHM Tweak Settings feature, or by running EasyApache from the command line to minimize its memory footprint.
Reference: http://cpanel.net
Error: Cannot open/read repomd.xml file for repository … No more mirrors to try
This error typically indicates that the mirrors listed in your /etc/yum.repos.d/ are out of date or temporarily unavailable.
If the mirrors are in the process of syncing, this issue may correct itself after a short time. If not, you may need to update the list of mirrors Yum is using.
Problems building Apache with your custom modules
If you have problems building Apache with your custom modules, and you are unable to troubleshoot the problem, run
/scripts/easyapache –skip-custom-optmods
This builds Apache and PHP without any custom modules.
From WHM
Access the WHM equivalent found in EasyApache’s Help section.
In order to remove a custom module from the server, simply delete the files you have created when you issued the above commands. The module will be removed from all future builds and the EasyApache interface.
Reference: http://cpanel.net/
Cpanel/WHM ways to configure PHP
DSO — Provides PHP through libphp4.so or libphp5.so (aka, mod_php). This option is usually the fastest way to execute PHP requests; however, this option uses the system user called “nobody” to serve all PHP requests.
suPHP — Provides PHP through mod_suphp. Using this option is probably the most flexible way of serving PHP requests and is generally very secure. Under this option, PHP scripts will be executed by the user who owns the VirtualHost serving the request.
FCGI — This option serves PHP through mod_fcgid. This is a fast way of serving PHP requests but will most likely require that you tweak php.conf. You can enable suEXEC to execute PHP scripts under the user who owns the VirtualHost that is serving the request or, if suEXEC is disabled, PHP will be served by the system user ‘nobody’.
