This document explains how to upgrade H-Sphere to version 2.3 RC4 and refine this candidate operability by upgrading WebShell and main H-Sphere DB.

• If you are upgrading from 2.3 RC2 or 2.3 RC3, do steps 1-9, leaving out steps 10-13.
• If you are upgrading from 2.3 RC1, do steps 1-9 and 13, leaving out steps 10-12.
• If you are upgrading from 2.2, do steps 1-12, leaving out step 13.
• If you have a version earlier that 2.2, upgrade yourself to 2.2 first.

Requirements

• H-Sphere v.2.2, 2.3 RC 1-3 installed;
• Apache 1.3.23 or higher and PHP 4.1.2 or higher installed on each H-Sphere web box;
• WebShell and update main H-Sphere database
• WebShell vulnerability patch installed;
• gcc compiler installed on each box.

Procedure

1. Make sure to have version 2.2, 2.3 RC1-3 installed:
   # cat ~cpanel/shiva/psoft_config/HS_VERSION
   If you have an older version, contact support@psoft.net or read the upgrade instruction for previous versions.
2. Download 2.3RC4 installation package from the Positive Software web site at http://www.psoft.net/shiv/U23RC4/U23RC4.tgz:
   # wget http://www.psoft.net/shiv/U23RC4/U23RC4.tgz
3. Unpack the downloaded file:
   # tar -xzf U23RC4.tgz
4. Enter the unpacked directory:
   # cd U23RC4
5. Stop H-Sphere Control Panel using the following commands:
   (they depend on the OS type and java servlet running engine):
   Linux + ApacheJServ:
   # /etc/rc.d/init.d/httpdcp stop
   FreeBSD + ApacheJserv:
   # /usr/local/etc/rc.d/apachecp.sh stop
   Any OS + Tomcat:
   # ~cpanel/tomcat/tomcat.sh stop
6. Run the upgrade:
   # make install
7. You need to restart your SiteStudio ImageMaker, the simplest way to do it is to execute:
   killall java
   as root. BE CAREFUL if you have any other java processes running.
8. Start H-Sphere CP using one of the following commands:
   Linux + ApacheJServ:
   # /etc/rc.d/init.d/httpdcp start
   FreeBSD + ApacheJserv:
   # /usr/local/etc/rc.d/apachecp.sh start
   Any OS + Tomcat:
   # ~cpanel/tomcat/tomcat.sh start
9. After your have completed the upgrade, check the version of H-Sphere using the following command:
   # cat ~cpanel/shiva/psoft_config/HS_VERSION
   
   You will get something similar to this:
   2.3.318.20030218
   Where:
   2.3 is the version of H-Sphere,
   318 is H-Sphere the build number,
   20030218 is the build date (in YYYYMMDD format)

Steps 10-12 are required for upgrades from version 2.2.
Skip steps 10-12 if you are upgrading from 2.3 RC1 or 2.3 RC2!

10. H-Sphere 2.2 and earlier versions used the external OpenSRS package and the OpenSRS configuration was placed into the /etc/OpenSRS.conf file. Starting with version 2.3, H-Sphere has an internal OpenSRS engine and should be configured using the admin Control Panel interface. To take OpenSRS data from the /etc/OpenSRS.conf file and migrate them into H-Sphere DB, you need to run the OpenSRSMigrator following the steps below. If you haven't been providing OpenSRS domain registratioin services and don't have the OpenSRS.conf file and the external OpenSRS package installed and configured, skip this step.
    1. Log into your CP box.
    su -l cpanel
    2. Launch OpenSRS migrator to process plans and migrate OpenSRS prices:
    java psoft.hsphere.tools.OpenSRSMigrator
    3. Login as root and restart H-Sphere.
    More on H-Sphere Domain Registrar Manager.
11. Log into your OpenSRS web interface and Re-register your OpenSRS keys to use the Blowfish crypting algorithm. Then go to your admin control panel and select Domain Registrar in the Settings menu. In the OpenSRS settings, enter the generated OpenSRS keys. Don't enter them in the opensrs.conf file. This is required because in version 2.3 H-Sphere doesn't use OpenSRS client and addresses OpenSRS directly using Blowfish.
12. If you are going to charge your customers for summary disk usage, not for disk quotas, enable Summary Disk Usage for all your user/reseller plans. Skip this step if you would like to charge your customers for disk quotas, as in earlier versions:
    1. Log into your control panel server as cpanel:
    su - cpanel
    2. Run the SummaryQuotasUpdate class to add the Summary Disk Usage resource to plans:
    java psoft.hsphere.converter.SummaryQuotasUpdate
    3. Login as root and restart H-Sphere.
    More on Summary Disk Usage.

1. Upgrading WebShell

To upgrade WebShell:

1. Log in as root.
2. Change directory to where you have untarred H-Sphere RC4 installation.
3. Type make webshell and press Enter.

*PHP Update Warning for H-Sphere 2.3 RC4
Once you have updated to version 2.3 RC4, it is highly recommended that you update your PHP to version 4.2.3 or higher to have the new version of WebShell running. However, mind the following:
- the /usr/local/lib/php.ini file is backed up and then replaced during the update (by the H-Sphere default php.ini file).
If you have any extraordinary php.ini settings, check the file after the update and reconfigure it according to your requirements Make sure PHP safe mode is off. There is no way to make Webshell 3 work, if safe mode is turened on.
- new version of PHP doesn't support some of the old PHP scripts that may cause problems;
- osCommerce 2.0 may stop running, so make sure to update osCommerce to version 2.2.

2. Upgrading H-Sphere Database.

To perform H-Sphere main DB update:

1. Log in as root.
2. Change directory to where you have untarred H-Sphere RC4 installation.
3. Type make moddb and press Enter.

This will back up old H-Sphere database and modify H-Sphere DB scheme (increase some fields length, e.g: email, notes, suspend/resume reason etc). Note: You may be prompted for your H-Sphere DB password under some of RedHat OS. Enter the password to complete the procedure.

Step 13 is required for upgrades from 2.3 RC1 only.
If you are upgrading from versions 2.3 RC2 or 2.2, skip this step.
Don't perform this procedure more than once.

1. Log into your control panel server as cpanel:
su - cpanel
2. Run the DiskUsageFix class to fix problems with displaying customers' disk usage:
java psoft.hsphere.converter.DiskUsageFix --process
3. Login as root and restart H-Sphere.

Reseller CP SSL settings format has been changed. If you have been using Reseller CP SSL with RC3 beta, please contact support@psoft.net for technical assistance in upgrading to RC3 public.

H-Sphere 2.3 RC3 and earlier versions used CNAME records for reseller server aliasing. Starting from version 2.3 RC4, H-Sphere uses A records for this purpose which improves reseller transparancy. To force these changes, when you are through with the update, your reseller or you have to:

1. Log into reseller admininstrative panel.
2. Go to E.Manager -> Server aliases.
3. Delete all server aliases in the "Other reseller`s server aliases" section.
4. Click Submit to regenerate reseller server aliases based on A records.

To check if the changes have taken effect, go to E.Manager -> DNS manager and click the Edit icon for this DNS zone. The Type of Built-in DNS records for reseller server aliases should change to "A".