Ensim® Pro and Ensim Basic 3.7 for Linux® (LS) Upgrade GuideApril 2, 2004
Introduction
This guide provides instructions for upgrading to the latest version of Ensim® Pro and Ensim Basic 3.7 for Linux® (LS) from the following versions.
- Ensim WEBppliance 3.5.20 for Linux
- Ensim WEBppliance 3.5.21 for Linux
![]()
For simplicity, we refer to Ensim Pro and Ensim Basic 3.7 for Linux (LS) as “Ensim Control Panel” throughout this document.
Sections in this guide include:
About the upgrade
Upgrading to the latest version of Ensim Control Panel simply involves downloading the Installer script, then running this Installer file on the target server.
![]()
Sites hosted on Ensim Control Panel will be accessible during the upgrade and services such as Web, FTP, and Email will continue to function, except when the site is being upgraded. However, the control panels will be inaccessible during the length of the upgrade. This could typically range from a few minutes to a few hours depending on the number of sites hosted on the server.
The time required to upgrade may vary depending on your server hardware (CPU and memory resources available), the speed of your network connection, and the number of sites hosted on Ensim Control Panel server.
Typically, the time required to upgrade the core Ensim Control Panel server is approximately 45 to 50 minutes and the time required to upgrade the sites hosted on Ensim Control Panel is approximately 1 minute per site.
So, assuming there are 20 sites hosted on the Ensim Control Panel server, it will take 65 to 70 minutes to complete the upgrade (45 to 50 minutes for the server and 20 minutes for 20 sites).
Before you upgrade
The following section describes the minimum system requirements and provides a checklist to help you prepare for the Ensim Control Panel upgrade.
System requirements
To upgrade to the latest version of Ensim Control Panel, your system needs to meet these requirements:
Table 1. System requirements for upgrading to Ensim Control Panel System requirements for upgrading to Ensim Control Panel Kernel version 2.4.20 or later Disk space At least 2 GB (free space) CD-ROMs (Optional) Two Ensim Control Panel CD-ROMs (if you want the Installer to obtain the Ensim Control Panel installation files from the CD-ROMs)Note: When you upgrade Ensim Control Panel, the Installer upgrades the operating system files and the Ensim Control Panel files on your server. Since the Ensim Control Panel CD-ROMs contain only the control panel installation files, the Installer obtains the operating system files from Ensim’s FTP server or a local FTP server (if you have configured a local FTP server). If you are using a local FTP server, please ensure that the FTP server is updated with the latest installation files from Ensim’s FTP server. For instructions, please refer to the document Setting up a local FTP server to install Ensim Pro and Ensim Basic 3.7 for Linux (LS) at http://www.ensim.com/support/pro/linux/ 37_index.html.
Other requirements
Upgrading the Red Hat kernel
Before upgrading to the latest version of the Ensim Control Panel, ensure that you have kernel 2.4.20 or greater running on your server; otherwise the upgrade will fail with an error. To verify the kernel version currently running on your server, log on to the server as the root user and run the following command at the prompt.
#uname -r
Depending on the kernel version currently running on your server, you must either install or upgrade kernel 2.4.20 and boot the server using this kernel.
![]()
Kernel 2.4.2. You must upgrade it to kernel 2.4.20 or greater and mkinitrd to mkinitrd 3.3.10-1. If you install kernel 2.4.20 instead of upgrading, the upgrade process fails since there is a conflict between the previous and the later versions of mkinitrd.
Kernel 2.4.7 or greater. You can either install or upgrade kernel 2.4.20 or greater on the server. However, it is highly recommended that you install the new kernel instead of upgrading to it, since the server can still boot using the older version of the kernel if there is an issue with the newer version.![]()
To upgrade the kernel:
- Download the latest version of the kernel from either Ensim’s FTP server ftp://ftp.ensim.com, your local FTP server or an external site.
- If you are using Ensim’s FTP server or your local FTP server to download the files, connect to the server with the following user name and password.
User name: ensimwpl
Password: ensim94089
#ncftp -u ensimwpl -p ensim94089 <ftp_server_name>
where <ftp_server_name> is the host name of the FTP server from where you want to download the kernel.
- Change to the apt/redhat/7.3/en/i386/RPMS.kernel directory on the FTP server.
#cd apt/redhat/7.3/en/i386/RPMS.kernel
- Download the file to the server on which you want to upgrade Ensim Control Panel.
#mget kernel-2.4.20-<release>.<processor_type>.rpm
where:
<processor_type> is the type of the processor in your server
<release> is the latest release of kernel 2.4.20 you have downloaded- Optional: If you have kernel 2.4.2 currently running on your server, you must also download mkinitrd-3.3.10-1 to the server.
#mget mkinitrd-3.3.10-1.i386.rpm
- Upgrade or install kernel 2.4.20 depending on the kernel version currently running on your server.
- If you have kernel 2.4.2 currently running on your server, upgrade the kernel and mkinitrd using the following commands.
#rpm -Uvh kernel-2.4.20-<release>.<processor_type>.rpm mkinitrd-3.3.10-1.i386.rpm
where:
<processor_type> is the type of the processor in your server
<release> is the latest release of kernel 2.4.20 you have downloaded- If you have kernel 2.4.7 or greater currently running on your server, install kernel 2.4.20 on the server using the following command.
#rpm -ivh kernel-2.4.20-<release>.<processor_type>.rpm
where:
<processor_type> is the type of the processor in your server
<release>- Perform post-upgrade tasks, if necessary.
- GRUB. If your server uses the GRUB boot loader, modify the default option in the GRUB configuration file grub.conf to point to the kernel version 2.4.20-<release>,
where <release> is the latest release of kernel version 2.4.20 installed on your server.
Note the usage of values for the default option.
0 indicates that the kernel version indicated by the first instance of the title option will be selected.
1 indicates that the kernel version indicated by the second instance of the title option will be selected.
Example. If the kernel version 2.4.20-20.7 is displayed in the first instance of the title option, set the default option to 0.
- LILO. If your server uses the LILO boot loader, please follow the instructions given below.
- Update the LILO configuration file to include the latest version of the kernel.
Example. If you had kernel 2.4.18-27.7 running on the server and you have installed kernel 2.4.20-20.7, you must update the LILO configuration file as follows:
![]()
If you have installed kernel 2.4.20 and chosen to retain the old kernel definition, you will be allowed to choose between the two kernels when you restart the server. You must boot the server using kernel 2.4.20 or greater before you upgrade Ensim Control Panel.
- Verify the changes made to the LILO configuration file using the following command.
#lilo -v -t
If the command results in error messages, you must edit the file to resolve the errors.
- If the changes to the LILO configuration file are successfully verified in step 4, update the LILO configuration settings using the following command:
#lilo -v
- Restart the servers using the following command.
#reboot
Upgrade checklist
Use the following checklist to verify that you have adequately prepared your system for a successful upgrade.
Table 2. Upgrade checklist Task StatusNote: Please back up the entire hard disk before upgrading to prevent loss of data if the upgrade fails.
¨ To ensure that all sites are consistent:
- Log on as the Appliance Administrator.
- Select Site Manager from the left navigation bar.
- In the Display field at the bottom of the page, click the arrow and select All Sites.
Sites that are inconsistent display the following message:
This site is currently in an inconsistent state. This may be the result of an active or failed edit.
See Sites using Microsoft Frontpage Server Extensions left in an inconsistent state for information on restoring a site to its consistent state. ¨ Microsoft FrontPage must be consistent on all your sites for the upgrade to succeed.To verify that Microsoft FrontPage is consistent on all sites, log on to the server as the root user and run the following command at the prompt:# /usr/local/frontpage/version5.0/bin/owsadm.exe -o check -p all ¨
- Have you verified the kernel version installed on your server?
You must have kernel version 2.4.20 or later installed on your server. If you have a previous version, you must upgrade to version 2.4.20. For instructions, please refer to the section Upgrading the Red Hat kernel.
¨ Refer to the section, Appendix A: Using the Ensim Control Panel Pre-upgrade Checker to review your customizations for compatibility. ¨
- If you have configured the Installer to obtain the Ensim Control Panel installation files using a local FTP server or the Ensim Control Panel CD-ROM, verify that the Installer has access to these repositories.
- Local FTP server: The Installer obtains the installation files from the specified FTP server. You need to specify the server name or IP address, the installation tree directory name, and the user name and password. If you are using anonymous FTP, set the user name to “anonymous” and the password to your “email address.”
- Ensim Control Panel CD-ROM: Two Ensim Control Panel CD-ROMs. Please ensure that the Installer has access to the CD-ROMs for obtaining the control panel installation files. Also ensure that it has access to Ensim’s FTP server or a local FTP server (if you have configured one) for obtaining the operating system files.
¨
Upgrading to the latest version of Ensim Control Panel
The following section provides instructions for upgrading to the latest version of Ensim Control Panel.
There are two modes of upgrading Ensim Control Panel.
- Curses-based. This method requires users to download the Installer script LWPInstaller.sh and run it on the command line with the parameters listed in Table 3. This method employs the default mode and is recommended for standard users.
![]()
If you are using the curses-based upgrade method, and using the system console to run LWPInstaller.sh, you should encounter no issues. However, if you are remotely logging in through a terminal application, please be aware that the curses-based upgrade will work if the terminal type is set to xterm or linux. You can always run the command
echo $TERMto determine your terminal setting.
If neither of the above two terminal types is detected, the Installer script displays a message that it is switching to the text mode.
- Text-based. This method is similar to the curses-based method, except that the Installer script is executed with the --classic option. For instructions, please refer the section Appendix B: Ensim Control Panel (LS) Installer for Advanced Users. This method is recommended for advanced users.
Table 3 lists the parameters required for the installation script, LWPInstaller.sh.
![]()
Before you upgrade, ensure that you meet the system and software requirements specified in the section Before you upgrade.
The following section describes the steps to upgrade Ensim Control Panel.
![]()
To upgrade Ensim Control Panel:
- Log on to the server on which you want to upgrade Ensim Control Panel.
- Download the Installer script from the Ensim support page http://www.ensim.com/support/downloads.html.
- Run the script by typing the following command at the prompt. Refer to Table 3 for the parameter descriptions.
#sh LWPInstaller.sh -- --ftp_server=<ftp_server_url> --no-quotacheck
--email=<email_address> --cdrom=<yes/no>![]()
The LWPInstaller.sh script is a wrapper that embeds the Installer script. The additional hyphens (--) are necessary to indicate to the wrapper that all parameters successive to the hyphens (--) must be passed on to the embedded Installer script.
- Optional: If you chose the Ensim Control Panel CD-ROM option, you will be prompted to insert the CD-ROMs (disk 1 and disk 2). Note that the installer will still need to connect to Ensim's FTP server or the local FTP server to download the operating system’s RPMs.
- Insert the Ensim Control Panel CD-ROM (labeled Ensim Control Panel CD 1) in the disk drive of your target server and press Enter.
- After copying the files from Ensim Control Panel CD 1, the disk is automatically ejected and you are prompted for disk 2.
- Insert the Ensim Control Panel CD-ROM (labeled Ensim Control Panel CD 2) in the disk drive of your target server and press Enter.
![]()
In the following example, the command upgrades Ensim Control Panel using the curses-based, or default mode.
#sh LWPInstaller.sh -- --ftp_server=ftp.ensim.com --no-quotacheck --email=admin@example.com --cdrom=nThe Installer starts upgrading your existing version of Ensim Control Panel. All the services and add-ons provided by Ensim Control Panel are installed. If you encounter problems during the upgrade, please use the information in Appendix C: Troubleshooting upgrade issues to resolve the issues.
![]()
This process takes some time and depends on the number of sites hosted on the server. You may encounter disk quota warnings during the upgrade; these warnings are not indicative of any problem with the upgrade and may be disregarded.
The Installer automatically runs the Pre-upgrade Checker before upgrading to Ensim Control Panel. At the end of the check, it displays the number of errors or warnings encountered. The results of the pre-upgrade check (list of checks, status of each check, and details about errors or warnings) are logged in the /var/log/ensim/installer.err log file. See Appendix A: Using the Ensim Control Panel Pre-upgrade Checker for details of the Pre-upgrade Checker and its results.
Please refer to the setup.log file located at /var/log/appliance/ for details.
![]()
Do not disconnect if the upgrade has been initiated over a remote connection, using Telnet or SSH. However, if you are disconnected due to technical reasons, reconnect to your server and locate the message "WEBppliance is upgraded to 3.7.1-<build_version>" in the file /var/log/appliance/history. The message indicates that the Ensim Control Panel upgrade has been completed.
If you are unable to locate the message, run the command, ps -ax
If there are RPM processes active, the command will list out the RPMs (running RPM processes indicate that the upgrade is in progress). Do not interrupt the upgrade.
After the upgrade is completed successfully, restart the server manually using the command: #/etc/rc.d/init.d/webppliance restart
Post-upgrade tasks
This section explains the tasks that you need to do when you finish upgrading Ensim Control Panel.
Upgrading the Apache 1.3 configuration file
Ensim Control Panel leaves the httpd_app.conf file untouched during the upgrade, as it may contain changes made by you or other installed Web-based applications. The httpd_app.conf file is preserved so that custom modifications are not lost. However, because of this, some of the new Web-based features will not be available to the upgraded sites.
In order to take advantage of the new features, you need to merge your custom configuration changes with the template httpd_app.conf provided by Ensim Control Panel.
![]()
To upgrade the Apache 1.3 file httpd_app.conf:
- Back up your existing /etc/httpd/conf/httpd_app.conf file.
- Copy the file /usr/lib/opcenter/apache13/install/httpd_app.conf to
/etc/httpd/conf/httpd_app.conf- Replace all instances of LOCALIP and LOCALHOST in /etc/httpd/conf/httpd_app.conf with the Ensim Control Panel server IP address and the host name, respectively.
- Modify the /etc/httpd/conf/httpd_app.conf file and add your custom configuration parameters.
- Since you are upgrading from WEBppliance 3.5.x, add the following line to the merged httpd_app.conf file. This will allow Tomcat 3 to work
LoadModule jk_module modules/mod_jk-eapi.so- Restart Apache by using the following command.
#/etc/rc.d/init.d/httpd13 restart
Upgrading the SquirrelMail file config.php
After the upgrade, some sites are unable to access SquirrelMail. To resolve this, you will need to upgrade the SquirrelMail file config.php.
![]()
To upgrade the SquirrelMail file, config.php:
- Back up the original config.php file located in
/home/virtual/<domain>/var/www/squirrelmail/config.- Copy the config.php file located in
/etc/virtualhosting/templates/sqmail/var/www/squirrelmail/config/config.php to the broken site’s directory
(/home/virtual/<domain>/var/www/squirrelmail/config/config.php).- After copying the file, change the file owner and group to match that of the original file.
- If the original config.php file has been modified by Site Administrators, then they should merge the old and new config.php files.
Regenerating Sendmail configuration file after an upgrade
Ensim Control Panel does not regenerate the Sendmail configuration file after an upgrade in order to retain any customizations made to the file. However, you may need to regenerate the file after an upgrade to take advantage of new service features or security fixes.
![]()
Before you regenerate the Sendmail configuration file, back up your existing Sendmail configuration file using the following command.
#cp /etc/sendmail.cf <directory>/sendmail.cf.bak
where <directory> is the directory in which you want to copy the file.
To regenerate the file after an upgrade:
Appendix A: Using the Ensim Control Panel Pre-upgrade Checker
Customers sometimes customize Ensim Control Panel to meet the unique needs and complexities of their hosting environment. An upgrade process, however, adversely impacts these customizations, and requires appropriate actions to retain them during an upgrade or recover them after the upgrade. Such customizations also have the potential to fail the upgrade.
The Ensim Control Panel Pre-upgrade Checker is a tool that evaluates the compatibility of customizations (on an existing Ensim Control Panel server) with the latest version of Ensim Control Panel. The tool provides a report that conveys possible conflicts and ways to resolve them. The Pre-upgrade Checker ensures that existing Ensim Control Panel servers can be efficiently upgraded.
The Installer automatically runs the Pre-upgrade Checker before upgrading an existing version of the Ensim Control Panel. At the end of the check it displays the number of errors or warnings encountered. The results of the pre-upgrade check (list of checks, status of each check, and details about errors or warnings) are logged in the /var/log/ensim/installer.err log file.
Interpreting the results of the pre-upgrade check
As the Pre-upgrade Checker performs each check, it displays the name and brief description of the check and the outcome of the check.
The outcome can be any of the following:
- OK. Displayed when the check is successful
- WARNING. Displayed when the check encounters an exception that may interfere with the upgrade process
- ERROR. Displayed when the check encounters an exception that will interfere with the upgrade process and cause it to fail
When the outcome of the check is a warning or an error, details about the exception are provided. More details can be found in the Pre-upgrade Checker report in the installer.err file available in the /var/log/ensim directory.
The Pre-upgrade Checker report provides the following information:
- A detailed list of exceptions observed on hosted sites
- A detailed list of exceptions observed on the server
- Recommended actions to be performed before the upgrade
- Recommended actions to be performed after the upgrade
![]()
The actions recommended provide broad solutions for resolving the observed exceptions. If these actions for resolving the exceptions are appropriate for your server, you must execute them as mentioned. After performing the recommended pre-upgrade actions, you must restart the upgrade by executing the LWPInstaller.sh script. To restart the upgrade, please follow the instructions from step 3 specified in the section Upgrading to the latest version of Ensim Control Panel
At the end of the check, a summary of the results is displayed, in the following format:
SUMMARY for <hostname>: <n> error(s), <m> warning(s), <k> domain(s) with issues
Where:
<hostname> is the name of your Ensim Control Panel server
<n> indicates the number of errors
<m> indicates the number of warnings
<k> indicates the number of domains for which exceptions have been observed
Impact of customizations on the upgrade process
The following sections list additional customizations that need to be addressed before or after the upgrade.
![]()
If you have customized Ensim Control Panel, we recommend that you contact Ensim Support to verify the impact of these customizations on the upgrade process. Ensim provides professional services that help you with the upgrade process.
The following is a list of:
Customizations that do not require pre-upgrade or post-upgrade actions
The following customizations do not require any pre-upgrade or post-upgrade actions.
- Files added to /usr/lib/opcenter/fastcgi/extras
- Customization files added to /usr/lib/ensim_python/site-packages/vh3/custom/
- Files modified in /etc/virtualhosting/ipranges
- Files modified in /etc/appliance/customization
- Files modified in /etc/virtualhosting/templates that do not belong to SquirrelMail
Customizations that require pre-upgrade or post-upgrade actions
The following customizations require either pre-upgrade or post-upgrade actions.
- Bind mounting directories under a site’s file system
![]()
Ensim Control Panel disables sites before upgrading them resulting in loss of bind mounted directories. If the bind mounted directory is essential for Ensim Control Panel to proceed with the upgrade, then the upgrade fails. This has been observed with the bind mounted directory, /usr/lib/perl.
- Pre-upgrade action required?
Yes.
Unmount the bind mounted directory using the following command:
umount <dir_name>
where <dir_name> is the absolute path of the bind mounted directory.- Post-upgrade action required?
Yes. Your bind mounted directories will be lost. You will require to bind mount the unmounted directories using the following command.
mount -b <dir_to_mnt> <bindmount_dir>
where:
<dir_to_mnt> is the absolute path of the directory you want to mount
<bindmount_dir> is the absolute path of the location where you want to mount the directory- Files modified in /usr/lib/opcenter/bind/named_conf_zone.tmpl
- Pre-upgrade action required?
Yes. Back up your named_conf_zone.tmpl file.
- Post-upgrade action required?
Yes. Your modifications may be lost after the upgrade. To resolve this issue, re-apply your changes back into /usr/lib/opcenter/bind/named_conf_zone.tmpl.
- DTML modifications to files under /usr/lib/opcenter
- Pre-upgrade action required?
Yes. Back up your custom DTML files.
- Post-upgrade action required?
Yes. Your modifications may be lost after the upgrade. To resolve this issue, re-deploy your custom DTML files to /usr/lib/opcenter.
- PHP binaries replaced with files owned by the PHP RPMs
- Pre-upgrade action required?
Yes. Your custom PHP binaries may be replaced with binaries from the (possibly older) PHP RPM shipped with Ensim Control Panel during the upgrade. To resolve this issue, either obtain, or build, a PHP RPM that is compatible with Fedora Core 1.0, and place the PHP RPM in the /tmp/oem/extrarpms directory before you run ./LWPInstaller.sh.
- Post-upgrade action required?
No.
- Existing MySQL RPMs installed with InnoDB support binaries replaced with files owned by the MySQL RPMs
- Pre-upgrade action required?
Yes. Your existing MySQL RPMs with InnoDB support binaries may be replaced with binaries from the (possibly older) MySQL RPM shipped with Ensim Control Panel during the upgrade. To resolve this issue, either obtain, or build, a MySQL RPM with InnoDB support and place the RPM in the /tmp/oem/extrarpms directory before you run ./LWPInstaller.sh.
- Post-upgrade action required?
No.
- Modifications made to the file /usr/lib/opcenter/fastcgi/httpd-tmpl.conf
- Pre-upgrade action required?
Yes. Back up your httpd-tmpl.conf file.
- Post-upgrade action required?
Yes. Your modifications may be lost after the upgrade. To resolve this issue, re-apply your changes to /usr/lib/opcenter/fastcgi/httpd-tmpl.conf.
- Modifications made to the non-config files owned by the RPM database
- Pre upgrade action required?
Yes. Back up the binaries.
- Post-upgrade action required?
Yes. Custom-compiled files owned by an RPM (which is part of the Ensim Control Panel service—if you are upgrading from WEBppliance 3.5) are replaced during the upgrade.
To see if a file is owned by an RPM, run the command, rpm -qf <full_path_of_binary>. If the command returns the name of a RPM, then the file will be replaced during the upgrade. Do not restore the file as the file may not be compatible with the new upgraded Ensim Control Panel environment.
For example, if you have compiled a binary that is linked against libcrypto.so.2 (a library file provided by WEBppliance/Red Hat Linux 7.3), and then upgraded your WEBppliance/Red Hat Linux 7.3 to Ensim Control Panel, the binary is unusable, as libcrypto.so.2 is replaced with libcrypto.so.4 in the new environment.
To ensure compatibility, recompile your binaries under a Fedora Core 1.0 system, or obtain the appropriate RPMs/source-rpms that are compatible with Fedora Core 1.0.
- Conflicts with existing MySQL RPMs
- Pre-upgrade action required?
Yes. Running ./LWPInstaller.sh may fail with the following RPM conflicts.
mysql conflicts with mysql-3.23.54a-3.73
mysql-devel conflicts with mysql-devel-3.23.54a-3.73
mysql-server conflicts with mysql-server-3.23.54a-3.73To resolve these conflicts, add mysql, mysql-devel, and mysql-server to the
/tmp/oem/extrarpms/exclude.list file. This step will exclude these RPMs from getting replaced during the upgrade process.- Post-upgrade action required?
No.
- OpenSSH upgraded to a version higher than version 3.1
- Pre-upgrade action required?
Yes. Running ./LWPInstaller.sh may fail with the following RPM dependency errors.
openssh = 3.1p1-6 is needed by openssh-askpass-3.1p1-6
libcrypto.so.1 is needed by openssh-3.4p1-1
libcrypto.so.1 is needed by openssh-clients-3.4p1-1
libcrypto.so.1 is needed by openssh-server-3.4p1-1To resolve these dependency errors, do one of the following:
- Either obtain, or build an OpenSSH RPM with a version number newer than the one provided by the Ensim Control Panel installation. Place this RPM in the /tmp/oem/extrarpms directory before you run ./LWPInstaller.sh.
or
- Place the following files in /tmp/oem/extrarpms/exclude.list file
openssh
openssh-askpass
openssh-clients
openssh-serverThis step will exclude these RPMs from getting replaced during the upgrade process.
- Post-upgrade action required?
No.
- Modifications made to the file /var/www/html/index.shtml
- Pre upgrade action required?
Yes. Back up the file /var/www/html/index.shtml.
- Post-upgrade action required?
Yes. Modifications made to the Ensim Control Panel root level file/var/www/html/index.shtml may be lost after the upgrade. To resolve this issue, re-apply your changes to the file /var/www/html/index.shtml.
- Modifications made to the file /etc/php.ini
- Pre-upgrade action required?
Yes. Back up the file /etc/php.ini
- Post-upgrade action required?
Yes. Modifications made to the /etc/php.ini file may be lost after the upgrade. To resolve this issue, re-apply your changes to the file or restore from your backup.
- Modifications made to the files /etc/httpd/conf/virtual/site<n>
- Pre-upgrade action required?
Yes. Back up changes to any of the /etc/httpd/conf/virtual/site<n> files.
- Post-upgrade action required?
Yes. Modifications made to any of the /etc/httpd/conf/virtual/site<n> files may be lost after the upgrade (your changes will be lost even when performing an enable/disable). To resolve this issue, you must add the modifications again to all these files manually.
![]()
Ensim Control Panel supports Apache 1.3 and 2.0. Please ensure that you make post-upgrade modifications in the code section pertinent to Apache 1.3. The code section is delimited by the following tags:
<ifDefine HTTPD13>
...
</ifDefine>
You can also make post-upgrade modifications in the code section pertinent to Apache 2.0. The code section is delimited by the following tags:
<ifDefine HTTPD20>
...
</ifDefine>- Modifications made to the files /etc/proftpd/site<n> or /etc/proftpd/site<n>.anonftp
- Pre upgrade action required?
Yes. Back up your changes to any of the /etc/proftpd/site<n> or /etc/proftpd/site<n>.anonftp files.
- Post-upgrade action required?
Yes. Modifications made to the files /etc/proftpd/site<n> and /etc/proftpd/site<n>.anonftp will be lost after the upgrade (your changes will be lost even when performing an enable/disable). To resolve this issue, re-apply your changes back to the file or restore from your backup.
- Modifications made to the file /etc/logrotate.conf
- Pre-upgrade action required?
Yes. Back up the file /etc/logrotate.conf.
- Post-upgrade action required?
Yes. Modifications to the Ensim Control Panel root level file /etc/logrotate.conf may be lost after the upgrade. To resolve this issue, re-apply your changes back to the file or restore from your backup.
- Modifications made to default Service Plans
- Pre-upgrade action required?
Yes. Save the settings of your default Service Plan.
- Post-upgrade action required?
Yes. The Ensim Control Panel upgrade will overwrite the default Service Plan. To resolve this issue, re-apply your changes to the default Service Plan.
- Sites using Microsoft Frontpage Server Extensions left in an inconsistent state
- Pre-upgrade action required?
No.
- Post-upgrade action required?
Yes. When these sites go into an inconsistent state, the following error message displays:
The document root of the web server where you are trying to install the server extensions already contains a disk-based web.To resolve this issue:
Appendix B: Ensim Control Panel (LS) Installer for Advanced Users
As an advanced user, you can opt for a text-based upgrade of Ensim Control Panel by running the Installer script LWPInstaller.sh with the --classic option at the command prompt.
To do so, download the Installer script from the Ensim support page http://www.ensim.com/support/downloads.html, then run the script with the parameters listed in Table 3.
![]()
To upgrade Ensim Control Panel:
- Log on to the server on which you want to upgrade Ensim Control Panel.
- Download the Installer script from the Ensim support page http://www.ensim.com/support/downloads.html.
- Run the script using the --classic option. Refer to Table 3 for parameter descriptions.
#sh LWPInstaller.sh -- --classic --ftp_server=<ftp_server_url> --no-quotacheck
--email=<email_address> --cdrom=<yes/no>![]()
The LWPInstaller.sh script is a wrapper that embeds the Installer script. The additional hyphens (--) are necessary to indicate to the wrapper that all parameters successive to the hyphens (--) must be passed on to the embedded Installer script.
- Optional: If you chose the Ensim Control Panel CD-ROM option, you will be prompted to insert the CD-ROMs (disk 1 and disk 2). Note that the installer will still need to connect to Ensim's FTP server to download the operating system’s RPMs.
- Insert the Ensim Control Panel CD-ROM (labeled Ensim Control Panel CD 1) in the disk drive of your target server and press Enter.
- After copying the files from Ensim Control Panel CD 1, the disk is automatically ejected and you are prompted for disk 2.
- Insert the Ensim Control Panel CD-ROM (labeled Ensim Control Panel CD 2) in the disk drive of your target server and press Enter.
![]()
In the following example, the command upgrades Ensim Control Panel using the text-based, or --classic option.
#sh LWPInstaller.sh -- --classic --ftp_server=ftp.ensim.com --no-quotacheck --email=admin@example.com --cdrom=n
Appendix C: Troubleshooting upgrade issues
If you encounter problems that you cannot troubleshoot or resolve using the information in Table 4, or the log files (see Log files), contact Ensim for online support at https://onlinesupport.ensim.com
Log files
Ensim Control Panel creates log files that record the various actions and events that qualify an upgrade. You may refer to the log files to troubleshoot fault points encountered during the upgrade. The log files are emailed to the specified email address.
Feedback and support
To take advantage of Ensim's support services or to find additional product documentation, visit the Ensim support site, http://support.ensim.com.
To log in to Ensim online support, go to https://onlinesupport.ensim.com.
To provide feedback about Ensim products or documentation, please use the feedback form at http://www.ensim.com/about/feedback.asp.
Legal and copyright notice
This document contains information proprietary to Ensim Corporation and its receipt or possession does not convey any rights to reproduce, disclose, manufacture, or sell anything it might describe. Reproduction, disclosure, or use without Ensim’s specific written authorization is strictly forbidden.
Ensim Corporation makes no representations or warranties with respect to the content or use of this document. It also reserves the right to revise this document at any time without the obligation to notify any person of such revision.
Ensim, the Ensim logo, and ServerXchange are registered trademarks of Ensim Corporation.
All other trademarks and copyrights are the property of their respective owners.
© 2004 Ensim Corporation. All rights reserved.
|
Ensim
Corporation www.ensim.com Contact Ensim www.ensim.com/about/contact.html |