Article ID: 2509, created on Oct 29, 2007, last review on Apr 27, 2014

  • Applies to:
  • Pro Control Panel Linux

AdditionalInformation

View Knowledge
Knowledge ID 1284
Product : WEBppliance for Linux
Version : 3.5.0
Topic : FAQ

Title
Upgrading to WEBppliance Pro from 3.x, known issues.

Summary
Upgrading to WEBppliance Pro from 3.x, known issues.

Prevention


Details

Following are the known issues while upgrading from LWP 3.x to Webppliance Pro :

--------------------------------------------------------------------------------------------------------

Scenario 1:
 
Conditions :
==========

LWP installed: 3.1.3

The current installation had duplicate installations of webppliance-mysql-3.1.3-4 and mysql-server-3.23.41-1.

Workaround :
==========

Follow the following steps to have the OSI upgrade started on this box:

1. rpm -e --justdb --allmatches mysql-server phpMyAdmin webppliance-mysql

2. Download the rpms from LWP 3.1.3 location and install them with
rpm -Uvh webppliance-mysql-3.1.3-4.i386.rpm phpMyAdmin-2.2.0-ensim4.i386.rpm mysql-server-3.23.41-1.i386.rpm

------------------------------------------------------------------------------------------------------------------------------------------------------------

Scenario 2: 

Conditions :
==========

LWP installed: 3.1.3

The current installation had non red hat MySQL rpms in place of those that come with the LWP.

Workaround :
==========

Follow the following steps to have the OSI upgrade started on this box:

1. rpm -e --nodeps (for all MySQL rpms which are not from redhat - note that MySQL-python21 is from the redhat and hence should not be removed)

2. Download the rpms from the LWP 3.1.3 location location and install them with command
rpm -Uvh mysql-3.23.41-1.i386.rpm mysql-devel-3.23.41-1.i386.rpm

------------------------------------------------------------------------------------------------------------------------------------------------------------

Scenario 3: 

Conditions :
==========

LWP installed: 3.0.3

The current installation had non red hat MySQL rpms in place of those that come with the LWP, also has the newer bind installed and also has installed gcc, cpp, gcc-c++, gcc-g77.

Workaround :
==========

Follow the following steps to had the OSI upgrade started on this box:

1. rpm -e --nodeps (for all MySQL rpms which are not from redhat - note that MySQL-python21 is from the redhat and hence should not be removed)

2. rpm -e gcc binutils cpp gcc-c++ gcc-g77 kernel-source

3. rpm -e --nodeps bind bind-utils bind-devel

4. Download the rpms from the LWP 3.0.2 location and install them with command
rpm -Uvh mysql-3.23.36-1.i386.rpm mysql-devel-3.23.36-1.i386.rpm

5. rpm -Uvh bind-9.1.3-3ensim1.i386.rpm bind-devel-9.1.3-3ensim1.i386.rpm bind-utils-9.1.3-3ensim1.i386.rpm

------------------------------------------------------------------------------------------------------------------------------------------------------------


Attachments


Related Knowledge

Related Links
 
Last ModifiedUsageSatisfiedLast Used
8/20/2004 1:00:32 PM21 10/11/2007 6:33:07 AM

4cc899da08664637a8bc437308d3ddd7 3ccb419cf98083f3bb45808fba8dbc7c 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF