• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Plesk 9.x to 10.x upgrade fails and deadlocks with psa version mismatch error

R

rjcain

Guest
Hi,

I've got my upgrade from 9.5.2 to 10.x in a pickle.

eg:
Code:
# /usr/local/psa/admin/sbin/autoinstaller   --select-release-id PLESK_10_0_1 --install-everything
consistently comes up with the error:

Code:
...yada yada ... all ok ... then...
===> Upgrading database
 Trying to start service mysqld... done
 Trying to establish test connection... connected
done
 Trying to find psa database... version is 0952
DATABASE ERROR!!!
Previous product version is 10.0.0, but previous database
version is 0952. 
...

.... then fails.

it doesnt matter what release i try to go up to or down to - i'm now, according to the autoinstaller, stuck between version 10.0.0 and version 10.4.4; it wont allow me back to 9.5.2 where i came from, nor forward. doesn't matter what other command options i try.

seems there's a bit of code in autoinstaller that 'should' be calling some sort of database updater, which presumably should culminate in setting that db version field. but somehow, it seems to have tripped over itself/didn't set it when it should have.

i'm pretty sure these are the two versions of 'version' - one for code and one for database i suppose:

Code:
[root@server109-228-18-91 ~]# cat /usr/local/psa/version
10.0.0 CentOS 5 108101004.13
[root@server109-228-18-91 ~]#

- Vs.

Code:
[root@server109-228-18-91 ~]# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa -e "select * from misc where param='version'"
+---------+------+
| param   | val  |
+---------+------+
| version | 0952 |
+---------+------+

they no longer match and they've left me in deadlock.

i've just spent several days upgrading the box (Fasthosts VPS) to latest versions Centos (5.7),PHP(5.3.8),MySQL(5.5.18); having to trash it and start again just seems way out of order for something that should be fixable with a simple mysql script.

i see many people have been posting on the web with this same, or near identical problem.

is there anyone out there who can help me find a solution to this?

any help/advice would be very much appreciated.

thanks
 
Back
Top