GoDaddy $1.99 Domains

Update VHCS 2.4.7 to VHCS ISP Control Panel in Debian

This update we have divided in to several steps so that it will be easy to understand 

1)General Information

 Download the newest VHCS2 release using the following command

 # wget

Turn off the VHCS Daemon in your machine if it is running using the following command

# /etc/init.d/vhcs2_daemon stop

 Make a backup of the current VHCS files of your system

 # mv /var/www/vhcs2/gui/ /var/www/vhcs2/gui_bcp_yyyymmdd
 # mv /var/www/vhcs2/engine/  /var/www/vhcs2/engine_bcp_yyyymmdd

Unpack the downloaded archive using the following command

 #tar -xjf vhcs2.4.7.1.tar.bz2

2)Existing vhcs2.conf Update

This file is located at /etc/vhcs2/vhcs2.conf

 Lines to add

BuildDate = 03.01.2006

Version =

VHCS_LICENSE = VHCS<sup>&reg;</sup> Pro v2.4.7.1<br>build:2006-01-03<br>Spartacus

3)Postfix update

Edit /etc/postfix/

and search for the vhcs2-arpl line (near the end) replace the flags=D to flags=O

The complete line should look like this:

vhcs2-arpl unix - n n - - pipe flags=O user=vmail argv=/var/www/vhcs2/engine/messager/vhcs2-arpl-msgr

4)Engine Update

Copy the new engine files

# cp -a /mydir/engine/ /var/www/vhcs2/

Copy your crypt key from the old /engine_bcp_yyyymmdd/ to /engine/

# cp /var/www/vhcs2/engine_bcp_yyyymmdd/ /var/www/vhcs2/engine/

Copy your crypt key from the old /engine_bcp_yyyymmdd/ to /engine/messager/

# cp /var/www/vhcs2/engine_bcp_yyyymmdd/ /var/www/vhcs2/engine/messager/

5)Backup Engine Update

Check and maybe change the crontab line for the backup

# crontab -e

if line looks like:

/var/www/vhcs2/engine/tools/vhcs2-backup-all yes &>/var/log/vhcs2/vhcs2-backup-all-mngr.log

change it too:

/var/www/vhcs2/engine/backup/vhcs2-backup-all yes &>/var/log/vhcs2/vhcs2-backup-all-mngr.log

Don't forget to make the same modification to your /etc/vhcs2/crontab/working/crontab.conf file

6)Mailbox Engine Update

because of a bug in the catchall adresses we have to rebuild the /etc/postfix/vhcs2/aliases

# mv /etc/vhcs2/postfix/working/aliases /etc/vhcs2/postfix/working/aliases-SAVE

# cp /mydir/configs/postfix/working/aliases /etc/vhcs2/postfix/working/aliases

7)Delete unneeded engine file

# rm /var/www/vhcs2/engine/setup/vhcs2-cfg-subst

8)Finish Engine Updates

Set correct engine permissions:

# /var/www/vhcs2/engine/setup/

9)GUI Update

Copy the new GUI files

# cp -a /mydir/gui/ /var/www/vhcs2/

Copy your crypt key from the old /gui_bcp_yyyymmdd/include/vhcs2-db-keys.php to /gui/include/vhcs2-db-keys.php

# cp /var/www/vhcs2/gui_bcp_yyyymmdd/include/vhcs2-db-keys.php /var/www/vhcs2/gui/include/vhcs2-db-keys.php

Set correct gui permissions:

# /var/www/vhcs2/engine/setup/

10)Database Update

Updated languages completely by importing the languages.sql For example with phpmyadmin or over commandline. All languages are changed. Please use languages.sql because it's the only way to update lang_english which is not update-able by language file. languages.sql is located in:

configs/database/languages.sql2) Delete all wrong added and not shown catchalls for alias domains

DELETE FROM `vhcs2`.`mail_users` WHERE `sub_id`='0' AND `mail_type` = 'alias_catchall';3) Change status for all mail-addresses:

UPDATE `vhcs2`.`mail_users` SET `status` = 'change' WHERE `status` = 'ok';

Now you should execute the VHCS engine manually, because users/customers may have made system changes during your update operation

This will take some time

# /var/www/vhcs2/engine/vhcs2-rqst-mngr

Now you can start the VHCS daemon

# /etc/init.d/vhcs2_daemon start

Now VHCS is successfully updated