• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Upgrade from 12.0.18 to 12.5.30 leads to several errors/login impossible

andsrv

New Pleskian
Hi,

today I tried to upgrade my Plesk Panel from version 12.0.18 to 12.5.30. The upgrade went through, but afterwards I was not able to login in to the control panel. The only thing that was given on the login page was this error:
ERROR: Plesk\Lock\Exception
Lock Manager error: 'No such file or directory'.

I uninstalled all Plesk packages and reinstalled them. After that I tried to fix it with the bootstrapper repair, but that didn't work either and I got several error messages in the installation, installation problems and repair log which are attached as seperate files.

It would be great, if anyone had a solution for the problem.
 

Attachments

  • plesk_12.5.30_installation_problems.txt
    1.1 KB · Views: 5
  • plesk_12.5.30_installation.txt
    171 KB · Views: 2
  • plesk_12.5.30_repair.txt
    11.8 KB · Views: 3
In Plesk 12.5 version for fixing all installation or post-installation problems use command

# plesk repair installation
 
Hmm... in this case looks like that upgrade process was not completed successfully. Use bootstrapper repair in this case.
 
I already did that, too. The bootstrapper repair completed with errors, which can be found in the repair log (attached to my first post)
 
Please do the following


1) Type "plesk version" and check which version is installed on the server.


2) mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa

select * from misc where param='version';


compare both and check whether the version showing is 12.0.18 or 12.5.30


3) If the "plesk version" showing 12.0.18 and mysql showing 12.5.30


Restore the psa, apsc and mysql from preupgrade dump.

/var/lib/psa/dumps



4) Reply if the issue still persists (with the screenshot of the error)
 
Hi Christy,
thank you for the ideas. I tried them. After typing "plesk version" I got this error message: "open /usr/local/psa/version: no such file or directory"

I also tried to restore the databases from the dump and got some error messages while trying to restore the apsc database (screenshot attached).

Now it shows me a slightly different error message on the login page (screenshot also attached below).
Bildschirmfoto 2015-11-17 um 21.32.26.pngBildschirmfoto 2015-11-17 um 21.22.58 (2).png
Again, thank you for your help :)
 
Upgrade corrupted the Plesk.
It seems that you have restore wrong pre upgrade dump. Please restore the first preupgrade dump or restore from the daily backup befoer upgrading


Do it after gunzip
---
mysql -uadmin -p`cat /etc/psa/.psa.shadow ` psa < dumpfile
mysql -uadmin -p`cat /etc/psa/.psa.shadow ` apsc < dumpfile
--

Also cross check the packages on the server is plesk 12.0 or plesk 12.5

rpm -qa | grep 12.0

You can perform the following the steps to make plesk up

1) Open the file
cat /usr/local/psa/version
12.5.30 CentOS 6 1205151023.17

2) Login to Plesk database after taking the current database backups

Run the below
mysql> alter table Modules add `plesk_max_version` varchar(30) DEFAULT NULL;
mysql> alter table domains add `icpStatus` int(1) NOT NULL DEFAULT '0';
mysql> alter table domains add `icpPermit` varchar(255) DEFAULT NULL;
mysql> alter table domains add `external_id` varchar(255) DEFAULT NULL;
mysql> alter table db_users add `external_id` varchar(255) DEFAULT NULL;
mysql> alter table data_bases add `external_id` varchar(255) DEFAULT NULL;
mysql> alter table db_users add `role` varchar(255) DEFAULT NULL;
 
Back
Top