This document explains how to update your H-Sphere to 2.3 Patch 1. To perform this update, you have to be logged in as root.

Procedure

1. Make sure to have H-Sphere 2.2 build 275 or later installed:
   # cat ~cpanel/shiva/psoft_config/HS_VERSION
   
2. 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
3. Run the update script by typing:
   sh ./U23P1
Note: The help shows. Choose what you want to update and follow the help.
4. To update H-Sphere, type:
   # install
5. If you have updated H-Sphere database when updating to any of H-Sphere 2.3 release candidates, skip this step. Otherwise, type:
   # moddb
   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).
6. To update WebShell to version 3.0 and php to version 4.3.0, type:
   # webshellphp
   To Update WebShell to version 3.0 without updating PHP, type:
   # webshell
   You need to update WebShell with PHP if your PHP is older than 4.2.3.

   Note: With WebShell update -
   - 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 custom php.ini settings, check the file after the update and reconfigure it according to your requirements. Make sure PHP safe mode is off.
   - the 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.

7. If you updated SiteStudio, restart your SiteStudio ImageMaker. The simplest way to do it is type:
   killall java
   Kill these processes one by one 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:
   
   Where:
   2.3 is the version of H-Sphere,
   325 is H-Sphere the build number,
   is the build date (in YYYYMMDD format)
   
   

Stop here if you have already installed H-Sphere 2.3 Final by following our instructions.

10. If you have updated H-Sphere database when updating to any of H-Sphere 2.3 release candidates, skip this step. Otherwise, type:
    # make moddb
    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).
11. If you have configured and used H-Sphere domain registrar manager with any of H-Sphere 2.3 release candidates, skip this step.
    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. At this point, you need to migrate OpenSRS data from the /etc/OpenSRS.conf file into H-Sphere DB using the OpenSRSMigrator tool. 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 as cpanel:
    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.
12. If you have configured your OpenSRS account settings to work with any of H-Sphere 2.3 release candidates, skip this step.
    Go to 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.
13. Starting with version 2.3 RC4, H-Sphere uses A records instead of CNAME records for reseller server aliasing to improve reseller transparancy. To force these changes on resellers' control panels, you or your resellers have to:
    1. Log into the reseller admininstrative panel.
    2. Go to E.Manager -> Server aliases.
    3. Delete all server aliases in the "Other reseller`s server aliases" section.