Since version 1.0.3, ispCP provides an update script that can be used both for migrate to a new ispCP version and for regenerate all configuration files such as apache vhost files, bind files… This is utile when you have completely destroyed your system by changing manually one or more configuration files and that your system is in unworkable state.

When you run the ispcp-update script, all your manually changes are removed and then, all configuration files are regenerated by using ispCP default package configuration files templates.

Note that if you have changed manually the ispCP templates, you should take care about possible syntax errors.

To regenerate all your configuration files, you must process like this:

<cli> # cd /var/www/ispcp/engine/setup # perl ispcp-update </cli>

Modifying the template files in parts/ is not enough to apply the modification to existing domains. The config files of the affected services have to be regenerated. The following steps will guide you through the process

<cli> # /etc/init.d/ispcp_daemon stop </cli>

<cli> mysql -u root -p </cli> It will prompt for the password.

In the mysql promtp enter: <cli> USE ispcp; </cli>
To regenerate all the domains configs: <cli> UPDATE `domain` SET `domain_status` = 'change' WHERE `domain_status` = 'ok'; </cli> To regenerate all the subdomains configs: <cli> UPDATE `subdomain` SET `subdomain_status` = 'change' WHERE `subdomain_status` = 'ok'; </cli> To regenerate all the aliases configs: <cli> UPDATE `domain_aliasses` SET `alias_status` = 'change' WHERE `alias_status` = 'ok'; </cli> To regenerate all aliases subdomain configs: <cli> UPDATE `subdomain_alias` SET `subdomain_alias_status` = 'change' WHERE `subdomain_alias_status` = 'ok'; </cli> To regenerate all the emails configs: <cli> UPDATE `mail_users` SET `status` = 'change' WHERE `status` = 'ok'; </cli>

<cli> quit </cli>

<cli> # /var/www/ispcp/engine/ispcp-rqst-mngr </cli>

<cli> # /etc/init.d/ispcp_daemon start </cli>