H-Sphere SSE Versions

For more information contact us

Updating H-Sphere Single Server Edition to 3.0 Patch 2

08 Feb 2007


Release Notes  |     Install  |     Change Log  |     Package List

This document explains how to upgrade H-Sphere SSE to 3.0 Patch 2.



Consider this before you update H-Sphere SSE:

  • The upgrade won't work without a valid H-Sphere SSE license to cover all accounts in the system!

  • It is required to customize server configuration files indirectly via respective template files. All custom changes in major default configuration files for Apache, FTP, PHP, DNS, MySQL, and PostgreSQL are removed with each update! Please carefully follow this update instruction to customize config file templates!

  • If you have a mail server running on the same box as the CP server, and CP server uses port 80, change CP port to 8080 in /hsphere/local/home/cpanel/apache/conf/httpd.conf or contact H-Sphere support.

  • Make sure that port 144 (localhost:144) is opened on all mailboxes.



  1. Download the H-Sphere SSE 3.0 Patch 2 install/update script:

    # wget http://www.psoft.net/shiv/HS/releases/U30.0/U30.0P2SSE/U30.0P2SSE


    # fetch http://www.psoft.net/shiv/HS/releases/U30.0/U30.0P2SSE/U30.0P2SSE

    Make sure that permissions to /usr/bin/wget are set to 0755 during the installation.
  2. Stop H-Sphere SSE using one of the following commands:

    # /etc/rc.d/init.d/httpdcp stop


    # /usr/local/etc/rc.d/apachecp.sh stop

    Stop SiteStudio ImageMaker by running:

    # /hsphere/shared/SiteStudio/imaker.sh stop

  3. Run the update script:

    # sh ./U30.0P2SSE

    You will see a help window with a prompt to enter update options.

  4. Update H-Sphere.
    • If one of the following conditions is met:

      1. if you have customized versions of H-Sphere SSE *nix packages or other system packages that you update via native OS package manager;
      2. if your default config files (Apache, PHP, mail, FTP, databases) are customized not by means of config file templates;

      H-Sphere update will be as follows:

      1. Update H-Sphere SSE core (templates, classes, jars):

        cpupdate [OPTIONS]

      2. In case a, exclude respective packages from being updated by the H-Sphere update script. To do this, type:

        hspackages [ ips=<IP1>,<IP2>,...<IPN>] exclude=add:<pattern1>,<pattern2>,...<patternN> skip=preparing

        Here, <IPx> are physical server IPs, and <patternx> are packages to exclude. For detailed syntax see command line interface of the H-Sphere Updater wrapper.

        To make sure you have successfully excluded the packages, run:

        hspackages [ ips=<IP1>,<IP2>,...<IPN>] exclude=show skip=preparing

        Warning: Please be very careful in excluding the packages from the update list! You must have serious reasons to do this!

      3. In case b, type the following command to create default config file templates to be customized afterwards:

        hspackages ctemplates=php,httpd,ftpd,mysql,pgsql

        For syntax and details please thoroughly read about customizing config files by means of templates.

        Important: This command will create default config file templates in respective directories. After that, you should customize them according to the custom configuration you had before. Typical reasons for such customization may be the use of Zend Optimizer, ChiliASP, ColdFusion Apache modules, etc.

      4. Update H-Sphere related packages:


    • Otherwise, if neither a or b is met:

      • to update H-Sphere SSE and Site Studio, type:

        update [OPTIONS]

      • to update only H-Sphere SSE, enter:

        hsupdate [OPTIONS]

      • to update only Site Studio, enter:

        sitestudio [OPTIONS]

      Important: The above mentioned options can be used very flexible with a variety of sub-parameters. For example, you may specify the ips=LIST_OF_IPs or groups=LIST_OF_LSERVER_GROUPS parameters to run the update only on particular physical servers to affect only particular logical server groups (Web, mail, etc.). Also if you run the update with the force parameter, new or updated packages will be installed by force, regardless of conflicts. More on SSE update/install script options

    Note: After the update, you'll be able to add more servers or services to the cluster by following the Adding Servers and Services documentation.

  5. If you have faced problems on the stage of running post-configuration scripts, you don't need to resume the update from the beginning. Choose the deploy mode to install and run post-configuration scripts once more:

    deploy [OPTIONS]

    More about H-Sphere update/install script options.
  6. H-Sphere update script will automatically launch H-Sphere SSE CP after the update. Check if H-Sphere is running, and if not, start CP Apache:

    # /etc/rc.d/init.d/httpdcp start


    # /usr/local/etc/rc.d/apachecp.sh start

  7. Start ImageMaker if your H-Sphere SSE is integrated with SiteStudio, for Linux & FreeBSD:

    # /hsphere/shared/SiteStudio/imaker.sh start

  8. Check the version of H-Sphere by executing the following command on your CP box:

    # cat ~cpanel/shiva/psoft_config/HS_VERSION

    You will see a line similar to this:



    3.0.0 is the version of H-Sphere,
    814 is the H-Sphere build.


Post-Update Issues

After you have updated H-Sphere SSE, please make sure you meet the following requirements:

  • Customization. If you have custom H-Sphere templates, you may probably need to update them according to changes introduced in this version.

  • Ownership. Templates, HTML pages, images, Javascript and CSS files have cpanel:httpdcp ownership. H-Sphere updater checks and automatically sets correct ownership and permissions on respective default and custom files and directories. Please make sure however that newly created custom files have correct ownership and permissions (this does not relate to H-Sphere packages).

  • Set up Kronolith Reminders If you use Kronolith reminders, make sure to set them up.

Copyright 1998-2018. Positive Software Corporation.
All rights reserved.