Upgrade Error - 8.1.1 to 8.2.0

[Sekka]

Hi,

I have had a pretty serious error upgrading Plesk from 8.1.1 to 8.2.0.

I started off as I always do by clicking "Install" with the default ticked options (I am assuming required).

After confirming, I was sent back to my update selection screen with 3 messages. Here is a print screen,

http://static.thnk.co.uk/junk/plesk_error.jpg

(I know the Plesk version at the top of this image is 7.5.4, I will explain later).

I thought it odd, but thought nothing of it. After the install was completed, I didn't receive the email from the server, because our email was no longer working.

I went back to the update screen to see if anything was wrong when i noticed this,

http://static.thnk.co.uk/junk/plesk_error2.jpg

I tried upgrading again, same errors, and I tried upgrading to lesser versions, again, same errors.

I then sent the report for the upgrade to a different email address and this is what I got,

http://static.thnk.co.uk/junk/plesk_email.txt

The last part is this,

 (s) system_installed_vixie-cron-4.1-11.EL3.i386.rpm
 (s) system_installed_webalizer-2.01_10-15.ent.i386.rpm
Installing the package psa-8.2.0-cos3.build82070706.15.i586

ERROR while trying to
Check the error reason(see log file: /tmp/psa_8.2.0_cos3.build82070706.15_installing.070711.16.33.log), fix and try again

Aborting...

error: %pre(psa-8.2.0-cos3.build82070706.15) scriptlet failed, exit status 1
error:   install: %pre scriptlet failed (2), skipping psa-8.2.0-cos3.build82070706.15
ERROR: An error occurred during installation of packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

The log it directs me to has pretty much the same thing, 4 lines telling me an error occurred but not saying what error.

So, Plesk is pretty broken. All our websites still work, except our email service is down and won't start.

I haven't tried any other functions in Plesk, as I don't want to cause more damage.

Any ideas or help would be brill.

Thanks,

Steve

 

[shall]

Similar issues as you for the most part, and I got it to install "kinda" 8.2. It says Watchdog is broken now, though. So I ran "up2date -u" to see if it'll give a more detailed error, here it is:


The package psa-watchdog-2.0.2-rhel4.build82070706.15 is not signed with a GPG signature. Aborting...
Package psa-watchdog-2.0.2-rhel4.build82070706.15 does not have a GPG signature.
Aborting...


Befuddled. At least the rest of my server appears to be working.

Hey SWSoft, I'm not fond of beta testing your releases!

 

[shall]

Here's the watchdog failure log:

======================================
START psa-watchdog-2.0.2-rhel4.build82070706.15 upgrading AT Wed Jul 11 16:56:19 CDT 2007
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Trying to start MySQL server... Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Starting MySQL[ OK ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]

ERROR while trying to start MySQL server

Aborting...

STOP psa-watchdog-2.0.2-rhel4.build82070706.15 upgrading AT Wed Jul 11 16:57:25 CDT 2007

======================================

Looks like it's choking on MySQL.

 

[shall]

And the Plesk "Desktop" link is resulting in a very long full page error that starts with:

MySQL query failed: Unknown column 'uid' in 'field list'

 

[jeambeam]

Plesk doesn't support builds of MySQL from mysql.com because it doesn't have status command which is used in Plesk installation scripts.

Originally posted by shall
Here's the watchdog failure log:

======================================
START psa-watchdog-2.0.2-rhel4.build82070706.15 upgrading AT Wed Jul 11 16:56:19 CDT 2007
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Trying to start MySQL server... Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
Starting MySQL[ OK ]
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]
...
Usage: /etc/init.d/mysqld {start|stop|restart|reload} [ MySQL server options ]

ERROR while trying to start MySQL server

Aborting...

STOP psa-watchdog-2.0.2-rhel4.build82070706.15 upgrading AT Wed Jul 11 16:57:25 CDT 2007

======================================

Looks like it's choking on MySQL.

 

[Sekka]

Our hosting providers have escalated the problem to Plesk. See what happens from there I guess.

 

[shall]

Originally posted by jeambeam
Plesk doesn't support builds of MySQL from mysql.com because it doesn't have status command which is used in Plesk installation scripts.

This server was a vanilla install of RHEL4 with Plesk 8.0. MySQL unless it was included with RHEL was never installed apart from Plesk.

 

[Sekka]

Ok, SWSoft are p**sing about on our server, and have decided to screw it up.

No websites nor the PleskCP work now.

I'm getting seriously f**ked off.

They are providing support for us but I can't speak to them directly, only our hosting company can.

Someone is going to hang tomorrow.

 

[shall]

I needed to create a new account on this server today, and it didn't work.

Hey SWsoft, do you think you might have the decency to respond?

 

[meat1oaf]

they neither feel the responsibility nor need to respond...

Why should anyone who charges folks to beta-test their software (then again to fix it) feel otherwise?

 

[phoenixisp]

The guys from swsoft don't monitor these boards. Here it is users helping users, that's it.

This is without a doubt the worst upgrading experience I've had with Plesk, and I've been using it since 2002. But then again, I don't remember many going well. Which is why I tried this out on a test server. Never, ever upgrade Plesk until the 8.2.2 version comes out - the last 2 stands for hotfix.

Hey meat1oaf - Plesk is starting to look like Bill Gates, eh? Releasing beta software.

 

[Amin Taheri]

I am having the same problem that both Sekka and Shall are having.

I am using Red Hat Enterprise Linux AS release 4 (Nahant Update 5)

I submitted support tickets to SwSoft and they have not responded back with anything useful.

The pictures from the first post dont work, so I am posting mine.

This is the error/success message that is on the screen after using the UI based updater for the first time.

I then get two emails from Plesk, one saying success, and one saying failure (received in that order)

I dont know if this is important, but I did not select any NEW components to be installed - only to update components which were marked with the yellow ! picture which are already installed and had an update available.

However now I am unable to create new users in Plesk from the UI - even logged in as the admin account.

Also, up2date is failing with the same problem as listed in previous

Fetching rpm headers...
########################################

Name                                    Version        Rel
----------------------------------------------------------
psa-php4-configurator                   1.2.0          rhel4.build82070706.15noarch
psa-watchdog                            2.0.2          rhel4.build82070706.15i586

Testing package set / solving RPM inter-dependencies...

Downloading headers to solve dependencies...
########################################
psa-php4-configurator-1.2.0 ########################## Done.
The package psa-php4-configurator-1.2.0-rhel4.build82070706.15 is not signed with a GPG signature.  Aborting...
Package psa-php4-configurator-1.2.0-rhel4.build82070706.15 does not have a GPG signature.
 Aborting...

 

[meat1oaf]

The 2=hotfix seems to be right on the money!

I'll tell you... I had delayed the upgrade from 7.5 to 8.0 for SO long - since I was afraid of the possible repercussions. After SEVERAL months (and a few subrevisions to 8.1.1), I finally bit the bullet and did it - and it went without a hitch. So, with the confidence gained from that, I didn't think twice about the upgrade to 8.2 - apparently I should have ;-)

Right now, web sites are up - but I can't access anything that needs DB access - like user creation, or user DBs.

I am right now installing the OS on a new server to migrate the clients to temporarily while I get the software fixed on the current server. My only concern is that will Plesk allow me to run two separate servers at the same time, even if only for migrating data? I foresee some major complications with this... anyone agree or disagree?

 

[Amin Taheri]

ok, I was able to fix my problem and revert back to 8.1.1

cd /root/swsoft/PSA_8.1.1/dist-rpm-RedHat-el4-i386/base/
rpm -U --force *.rpm

This appears to have re-installed the core 8.1.1 RPMs and has maintained all visible settings, all customers and domains, etc.

I can now also add domains again with out the error.

Scared me at first becuase the agreement came back up, but since it still recognized my admin pw and still had the client list my anxiety eased pretty quick.

I'm still keeping an eye on it to make sure that everything is working as expected, but so far so good.

 

[Amin Taheri]

not to double post, but I got this from SWSoft Support

Hello,


As for the first question regarding Plesk upgrade through Plesk updater actually there is some issue to update Plesk via autoinstaller, our developers are working on it. So it would be better to upgrade Plesk manually. I advise you to do the following in order to upgrade Plesk from 8.1 to 8.2:

1) remove 'caching-nameserver' package if it is installed:
# rpm -e caching-nameserver
2) alter the database of Plesk adding the field if it is missing:
# mysql -uadmin -p`cat /etc/psa/.psa.shadow`
mysql> ALTER TABLE psa.subdomains ADD INDEX dom_id_2 (`dom_id`);
3) rename 'root' MySQL user if it exists to other name before upgrade
and rename it back to 'root' after:
mysql> UPDATE mysql.user SET user='ROOT' WHERE user='root';

then perform the following command (please correct the path if needed)
cd /root/psa/PSA_8.2.0/dist-rpm-FedoraCore-2-i386/base/
rpm -Uvh *

and then rename ROOT back to root:
mysql> UPDATE mysql.user SET user='root' WHERE user='ROOT';

As for second question I'm going to pass it to our second line Team, they will help you.

 

[Sekka]

Well,

SWSoft played with our server and broke it even more.

We have now moved to another hosting provider and got a VPS instead of a dedicated. Luckily this new company is on the ball and we now have a webserver running with 8.2 and excellent support.

I've learnt a lot from this experience, the main thing being SWSoft's support is appauling.

Good luck to one and all. I hope Plesk do something to help everyone.