I wont go into any long details on here but both of those how-to's can be found here =>http://www.axihost.net/forum/viewtopic.php?t=5 I have covered most of the more common problems it is also a compilation of alot of information that can be found on rackshack and a few personal work arounds.
have fun

good looking how tos and great work compiling the info

issues:

you forgot to tell them to chmod +x wpinstall-u.sh after downloading it so that it can be run
if it errors you can tell them to run ./oem_installer.sh

Mouse

how well has this one been tested? on which versions of Ensim?

Since many people seem to have problems with Ensim, and I only have 1 production server, I am *VERY* cautious with this upgrade and might not upgrade at all...

thsi is basically a compilation of information gathered from a huge Ensim 3.1.1 upgrade thread in the Ensim Add ons and Developments section of the forum.. Id suggest reading that whole thread first plus RTFM the PDF files from Ensim.com which are linked to in that thread then study this how to and then proceed cautiously.. Mouse

Ta mouse I'll add that as well to chmod the files as well as the oem_installer.sh

What advantage is there upgrading from 3.0 to 3.1.1?

Reseller feature ...

3.0 - 3.1.1
Im stuck here.

Would this be because of the open ssl upgrade? Please let me know what I can do now.


##################################################


WEBppliance 3.1.1-31.
Installer version 1.0-17.
Installer error log:
Wed Sep 18 22:16:36 IST 2002
09/18/02 22:17:38 : error: failed dependencies:
openssl = 0.9.6-13 is needed by openssl-perl-0.9.6-13
openssl = 0.9.6-13 is needed by openssl-python-0.9.6-13

##################################################



Then I did

[root@srv01 applianceupdate]# rpm -Uvh openssl*.rpm
Preparing... ########################################### [100%]
package openssl-perl-0.9.6-13 is already installed
package openssl-python-0.9.6-13 is already installed

....

cd download
rpm -Uhv --replacepkgs openssl*

then try to rerun the install.. Mouse

[root@srv01 applianceupdate]# cd download
[root@srv01 download]# rpm -Uhv --replacepkgs openssl*
error: failed dependencies:
openssl <= 0.9.6 conflicts with openssl096-0.9.6-13

I went into the old download dir for 3.0 and issued the command and it seemed to work.

Although the installation comes up with

Current rpms.

try using
rpm -Uhv --replacepkgs openssl*
then run the ./oem_installer.sh again

As you can see a few messages above this was already tried.

Just a word.... I got a new box yesterday that had 3.1.1 on it seems RS is doing that on restores now.... maybe HS was so worried about that worm messin with his network he wants all new ones with it soon...

WEBppliance 3.1.1-31.
Installer version 1.0-17.
Installer error log:
Sun Sep 22 21:56:19 SGT 2002
09/22/02 21:57:02 :
Unfortunately, there are bugs in the versions of rpm shipped with RedHat 7.1
and 7.2, and their respective updates, that can cause the upgrade to fail to
replace files that it should. In order to prevent this, this install script
requires that you have at least rpm-4.0.4-7x.18.i386.rpm (provided by RedHat
7.3) installed or newer. Please upgrade to this version of rpm or newer, and
then run the upgrade script again. To ease your upgrade, you can find the
relevant RPMs in the /tmp/extrarpms directory. Note that you may also need to
upgrade glibc, popt, and any of the rpm-* RPMs (e.g. rpm-devel, rpm-python,
etc.) that you already have installed along with rpm; you may ignore the other
RPMs present in that directory



Also

i got this

at the /home/new
[root@ns3 new]# rpm -Uhv *.rpm
error: failed dependencies:
libreadline.so.4 is needed by bc-1.06-8

How to solve?

This was a great HOW-TO it definately helped me upgrade from 3.03 to 3.1.1. It did confuse me in some areas and have a few actions from the manual missing. (This is mostly in regards to pre-install actions though)

After reading all the info from this monstrous thread:
http://forum.rackshack.net/showthread.php?...&threadid=10359

and from the manual I was able to do a more or less flawless install.

Missing from the HOW-TO is the pre-upgrade tasks. I took this information from various contributors in the many threads and would like to thank all the people that shared their experiences.

In some cases I had to do a little extra research if I didn't get the answer I was looking for in the threads or manual and since I was very cautious with the upgrade as everybody should be.

Somtimes I found my answer and sometimes I didn't, so I will probably bring up just as many questions as answers below.

FSCK
When you attempt to run fsck you will get an error about damaging your server and the sky falling. This is kind of scary if you havn't ever run fsck before. Fortunately, you can force your server to run fsck on a reboot. I couldn't figure out how to do this using a reboot command though.
I used "shuddown -rF now". The -r tells the server to reboot after shutting down and the -F forces the fsck. Apparently, this creates an advisory file that you can check for errors in /forcefsck. I couldn't find this directory though. Anybody know where it is supposed to be?

MEMTEST
I installed and ran this utility without any problems. The only thing that confused me here was the number or times to run it. The program automatically starts the test again after it finishes. How many times is it supposed to run through the test? I stopped it after its 3rd run.

According to the above HOW-TO you are supposed to download and run wpinstall before adding RPM's to the /tmp/extrarpms directory. The manual says to add the 4.04-7x.18 before hand though.
It probably doesn't matter which order you do it it, since wpinstall will complain about dependancies anyways, but when you don't know if it matters or not, it can be a little disconcerting. I ended up following the manuals advice here and it worked fine.

To check what version of Perl you are running use "Perl -v" from the command line.

I Hope that helps some people with some of the smaller but also important issues.

-Fractal

nm.. re-read post.. lol

-boing?

Had the same problem. I just removed the 2 rpm's.

rpm -ve openssl-python-0.9.6-13
rpm -ve openssl-perl-0.9.6-13

I think both rpm's were installed from "huck"'s openssl fix for ensim 3.0. I don't think the default ensim install has either rpm's installed.

We'll worked fine for me... and all my customer sites seem fine. The whole upgrade process went perfectly smooth....

Beautiful Thanks. will try now.

I've been reading this thread with great interest and I'm currently running Ensim 3.0.3-4. My server is a high traffic production environment and I want to know how easy it is to migrate to 3.1.1. I've read the documentation and read this reference link:

http://www.axihost.net/forum/viewtopic.php?t=5

Is the information in this guide solid. If I follow it to the letter will there be any problems and what should I look out for? Any assistance on this would be appreciated. I worried about messing up this upgrade and not being able to recover. I can't afford any downtime if this upgrade fails.

Actually I would suggest waiting till he re-updates it.. his forum crashed and he lost a seriously updated version of that thread.. Mouse

Welp I succesfully updated from 3 to 3.1.1 , everything is running fine so far

I successfully upgrade from 3.0.3-4 to 3.1.1 without error messages, however, when I log into the control panel it still reports the old verison 3.0.3-4. Any ideas?

Please advise.

Regards,
Gabriel

see my reply at your other post.. Mouse

Forum is back up with all updates.
just as a sub-note to mouse
also to hostseller2
try pico -w installer.err will give you an idea on what went wrong, it should be in the same directory.

more installer.err works even better as you can hit the space bar to the end then be able to scroll back and forth perfectly fast..

In most cases that will find errors, the issues I had went far beyond the scope of what that log listed... Mouse

i upgraded mysql and then went to install the 3.11 patch and get this error ist here a way to fix it??? i have changed mysql and phpmyadmin so far


WEBppliance 3.1.1-31.
Installer version 1.0-17.
Installer error log:
Thu Sep 26 23:48:59 EDT 2002
09/26/02 23:50:01 : error: failed dependencies:
MySQL conflicts with mysql-3.23.41-1
MySQL-devel conflicts with mysql-devel-3.23.41-1

suggest you RTFM..
goto ensim.com and find the upgrade PDF's and read them and your answer will jump out at you.. Mouse

i see it say 3.1.1 but in ensim itself it says 3.1.0-25

First i start he say failure mysql
i install the upgrades from download dir
then restart:

Starting upgrade. This may take several minutes
to hours depending on the number of sites
Performing pre-install check... (this may take a few minute[FAILED]

Failed to install service RPMs.
Installation aborted.

And when i restart now httpd the messagelist is not so long before i start the upgrade but is working at the moment
What is this?
Any Idea?:confused:

hmm i see now i have php 4.2.2 before 4.2.1

Ok Just upgraded my Box from 3.1.0 to 3.1.1 . The whole process went in 20 minutes and my Appliance show 3.1.1 now

Thanks to Mouse & python_dev ...

Mouse you made me RTFM 3 times ..I was so scared before upgrading it

just upgraded mine last night then upgrade php to 4.2.3 thanks alot guys