H-Sphere Versions

For more information contact us

Updating H-Sphere to 2.4.2 Beta 3

21 Dec 2004

 

Release Notes  |     Install  |     Change Log  |     Package List


WARNING:
This H-Sphere version is outdated and is not supported. Please refer to latest supported versions.

This document explains how to upgrade H-Sphere to 2.4.2 Beta 3 from 2.3.1 Patch 9 and up. If your H-Sphere is lower than 2.3.1 Patch 9 (build 2.3.1.385), please upgrade to 2.3.1 Patch 9 first.

To upgrade from a version lower than 2.2, please contact H-Sphere support.


 

Pre-Requisites

Consider this before you update H-Sphere:

  • SpamAssassin 3.02 is very resource-consuming, therefore make sure you have at least 1Gb of RAM on a mail server before upgrading to 2.4.2.
  • Bayesian spam filtering in SpamAssassin manager is very resource-consuming. Therefore 2.4.2 update disables this feature by default.
  • To support the latest version of SpamAssassin, we update perl on mail servers for RedHat 7.2 and FreeBSD 4.x.
    On RedHat 7.2, perl is updated from 5.6.0 to 5.6.1 and has no impact on custom perl modules.
    On FreeBSD 4.x, perl is updated from 5.0.0.5 to 5.8.5, which requires re-installation of custom modules for the newer version.
    Therefore, if:
    - you run web and mail on the same server AND
    - this server runs FreeBSD 4.x AND
    - you have custom perl modules,
    please:
    - before you start the update, make sure you have the sources of your custom modules
    - compile and reinstall the custom modules after the update.
  • The upgrade won't work without a valid H-Sphere license to cover all accounts in the system!

  • Please refer to the list of operating systems supported by H-Sphere.

  • Before the upgrade make sure you've upgraded:

  • 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.

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

 

Procedure

  1. Make sure you have H-Sphere 2.3.1 Patch 9 or higher installed:
    # cat ~cpanel/shiva/psoft_config/hsphere.properties | grep HS_VERSION
    If you have an older version, contact support or read how to upgrade from previous versions.
  2. Download the 2.4.2 Beta 3 upgrade package:
    Linux:
    # wget http://www.psoft.net/shiv/HS/U24/U24.2b3/U24.2b3
    FreeBSD:
    # fetch http://www.psoft.net/shiv/HS/U24/U24.2b3/U24.2b3
  3. Make sure that permissions to /usr/bin/wget are set to 0755 during the installation.
  4. Stop H-Sphere using one of the following commands:
    Linux:
    # /etc/rc.d/init.d/httpdcp stop
    FreeBSD:
    # /usr/local/etc/rc.d/apachecp.sh stop
    Stop SiteStudio ImageMaker by running:
    # /hsphere/shared/SiteStudio/imaker.sh stop
  5. Run the update script:
    # sh ./U24.2b3

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

  6. Update H-Sphere.
    • to update H-Sphere and Site Studio, type:

      update

    • to update only H-Sphere, enter:

      hsupdate

    • to update only Site Studio, enter:

      ssupdate

      Important: To use SiteStudio, make sure it is not lower than 1.6 Patch 1.

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

  7. If your system database is not in UNICODE (UTF-8), convert it to UTF-8.
  8. [-] If you have a custom CP URL...
    If you have customized your CP URL, log in as root and run the jakarta_servlet_upt.pl script to apply custom servlet name and mount point to Tomcat configuration files and to the index page template ~cpanel/shiva/shiva-templates/index.html:
    cd ~cpanel/shiva/psoft_config
    ./jakarta_servlet_upt.pl
    The script replaces old servlet name and mount point in the following files:
    ~cpanel/hsphere/WEB-INF/web.xml
    ~cpanel/apache/etc/mod_jk.conf
    ~cpanel/jakarta/conf/server.xml
    ~cpanel/shiva/shiva-templates/index.html
    Original configuration files are backed up:
    ~cpanel/hsphere/WEB-INF/web.xml.ORG
    ~cpanel/apache/etc/mod_jk.conf.ORG
    ~cpanel/jakarta/conf/server.xml.ORG
    ~cpanel/shiva/shiva-templates/index.html.ORG
  9. Upgrade your Winbox to 2.4.2 Patch 5 (latest Winbox in this H-Sphere branch).
  10. H-Sphere update script will automatically launch H-Sphere CP after the update. Check if H-Sphere is running, and if not, start CP Apache:
    Linux:
    # /etc/rc.d/init.d/httpdcp start
    FreeBSD:
    # /usr/local/etc/rc.d/apachecp.sh start
  11. Start ImageMaker if your H-Sphere is integrated with SiteStudio, for Linux & FreeBSD:
    # /hsphere/shared/SiteStudio/imaker.sh start
  12. Check the version of H-Sphere by executing the following command on your CP box:
    # cat ~cpanel/shiva/psoft_config/hsphere.properties | grep HS_VERSION

    You will see a line similar to this:
    HS_VERSION = 2.4.2.480.20041221
    Where:
    2.4.2 is the version of H-Sphere,
    480 is the H-Sphere build,
    20041221 is the build date (in YYYYMMDD format)

 

Post-Update Issues

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

  • Winbox Update. Don't forget to upgrade Winbox to 2.4.2 Patch 5 (latest Winbox in this H-Sphere branch) if you haven't done this yet.

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



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