• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk 12.5.30 update failed

DimitrisG

Basic Pleskian
ypeError: an integer is required
error: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0x48badd0>> failed, aborting!
Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_12_5_30', sequence='pkgs', stage='rollback', sequence_order='1', operation='install', exec_cmd='rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; touch /var/lock/parallels-panel-upgrade-failure.flag; :'', m_arch='', output: ~empty
[2015-10-31 20:06:06.672537] Execute command /usr/local/psa/admin/bin/send-error-report install --version 12.5.30
[2015-10-31 20:06:06.697861] Error: Failed to run the Yum utility.
The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.


Since then my Plesk Panel has been upgraded (Plesk version 12.5.30 Update #8) but it's a mess.

I am getting a blank page instead of the Backup Manager, I can't list the SSL certificates on a domain, some buttons are missing text.

Is there any way to fix this or to roll back?

ps. Plesk is installed on a Centos 6.5 system
 
The funny thing is that I am still having the old Parallels logo on the top right corner. Is there any way to force the upgrade using the console? (since my system is system is "up-to-date" according to plesk)
 
Thanks for your reply. Unfortunately the plesk repair tool didn't help. Which log files should I post?

Thanks again,
Dimitris
 
My plesk is completely broken. None of the new 12.5.30 pages are working (backups, databases, SSL certificates). Please help... :(
 
Last edited:
Hi DimitrisG,

There is only an error in your installation log for phpMyAdmin:
Code:
ERROR 1049 (42000): Unknown database '-Br'
ERROR 1049 (42000): Unknown database '-Br'
ERROR at line 16: USE must be followed by a database name
ERROR 1046 (3D000) at line 23: No database selected

WARNING!
Some problems are found during create pmadb(see log file: /var/log/plesk/install/plesk_12.5.30_installation.log)
Did you use special characters for your database - names?

Is the installation log the only log - file at /var/log/plesk/ ?
 
Nope I only use Latin and numbers. There are lots of log files but this one was created during the upgrade. Here is the list of all my log files in /var/log/plesk. Let me know if you want to have a look at a different one.

Thanks again for your help.
 
Hi DimitrisG,

please post the following logs:

/var/log/plesk/repair-20151031-205904.log
/var/log/plesk/repair-20151031-205909.log
/var/log/plesk/repair-20151031-210015.log
/var/log/plesk/repair-20151101-014546.log

/var/log/plesk/install/plesk_12.0.18_repair.log
/var/log/plesk/install/plesk_12.5.30_repair.log

/var/log/plesk/install/autoinstaller3.log
 
Hi DimitrisG,

first, I did notice, that you have a "libMagick" - issue. Please try to solve that issue with the help of the forum threads:



Further, I would suggest to disable non-CentOS repositories ( Epel, atomic, or what ever else you have as additional repos enabled ) and use afterwards the commands:

Let yum do a cleanup and list your enabled repositories:
yum clean all && yum repolist
( please post it with your next answer! )

Use the Plesk autoinstaller:
/usr/local/psa/admin/sbin/autoinstaller --select-product-id plesk --select-release-current --upgrade-installed-components

... followed by:
/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base

... followed by:
plesk repair all -v
You should get new logs, which should be viewed to investigate issues/problems/errors and warnings.


Consider to delete old logs from time to time, which you don't need any more. It is quite difficult to keep track of when unnecessary logs are kept. I doubt that you will ever investigate logs from 2014 for example. I recommend monthly clean-ups :D
 
Last edited by a moderator:
Hello again. Sorry for taking so much time to reply. I've uninstall ImageMagick and removed all non-CentOS repositories. Here is the output of "yum clean all && yum repolist".

Loaded plugins: fastestmirror, priorities
Cleaning repos: base extras plesk-php-5.2 plesk-php-5.3 plesk-php-5.4 plesk-php-5.5 plesk-php-5.6 updates
Cleaning up Everything
Cleaning up list of fastest mirrors
Loaded plugins: fastestmirror, priorities
Determining fastest mirrors
* base: centosmirror.netcup.net
* extras: centosmirror.netcup.net
* updates: centosmirror.netcup.net
base | 3.7 kB 00:00
base/primary_db | 4.6 MB 00:00
extras | 3.4 kB 00:00
extras/primary_db | 32 kB 00:00
plesk-php-5.2 | 2.9 kB 00:00
plesk-php-5.2/primary_db | 14 kB 00:00
plesk-php-5.3 | 2.9 kB 00:00
plesk-php-5.3/primary_db | 14 kB 00:00
plesk-php-5.4 | 2.9 kB 00:00
plesk-php-5.4/primary_db | 14 kB 00:00
plesk-php-5.5 | 2.9 kB 00:00
plesk-php-5.5/primary_db | 14 kB 00:00
plesk-php-5.6 | 2.9 kB 00:00
plesk-php-5.6/primary_db | 14 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 2.6 MB 00:00
repo id repo name status
base CentOS-6 - Base 6575
extras CentOS-6 - Extras 44
plesk-php-5.2 PHP v 5.2 for Plesk - x86_64 31
plesk-php-5.3 PHP v 5.3 for Plesk - x86_64 32
plesk-php-5.4 PHP v 5.4 for Plesk - x86_64 32
plesk-php-5.5 PHP v 5.5 for Plesk - x86_64 32
plesk-php-5.6 PHP v 5.6 for Plesk - x86_64 32
updates CentOS-6 - Updates 652
repolist: 7430
[root@server]#

I also used the autoinstaller & repair but nothing changed. All the new 12.5.30 Plesk pages (like Database, Backup Manger etc) still don't work. I am attaching my new logs, please let me know if you think of something. :(

autoinstaller3.log
plesk_12.5.30_repair.log
repair-20151112-023438.log
 
Hello,

I'm experiencing the same issues Dimitris was having:
After server upgrade on a CentOS6.9 from Plesk 12.0.18 to 12.5 Plesk is slightly disfunctional.

- SSL certificates are not showing in subscriptions tools (They are in hosting settings)
- Blank page for Backup Manager
- Plesk top Menu for smb (Subscriptions) is messed-up.

How do you get out of this?
I already run the plesk installer
--select-release-current --upgrade-installed-components
and
--reinstall-patch --install-component base
and repaired and reconfigure Plesk (it fixed a broken references in the table 'smb_users')
plesk repair all -v finished:
Error messages: 2; Warnings: 6; Errors resolved: 1
exit status 1

Here is the info I have:
The first installation hung, I had to restart it manually then it proceed OK UNTIL near the end
===> Installing phpMyAdmin
Trying to create pmadb... ERROR 1102 (42000) at line 20: Incorrect database name ''

WARNING!
Some problems are found during create pmadb(see log file: /var/log/plesk/install/plesk_12.5.30_installation.log)

Continue...

ERROR 1049 (42000): Unknown database '-Br'
ERROR 1049 (42000): Unknown database '-Br'
ERROR at line 16: USE must be followed by a database name
ERROR 1046 (3D000) at line 23: No database selected

WARNING!
Some problems are found during create pmadb(see log file: /var/log/plesk/install/plesk_12.5.30_installation.log)

Congratulations!
All stages of the installation/upgrade have been finished.
psa is now running on your system.
To complete the system configuration process, please proceed to URL:
https://<servername>.com:8443/ or
https://127.0.0.1:8443/

Thanks for your reply. Unfortunately the plesk repair tool didn't help. Which log files should I post?

Thanks again,
Dimitris
 
Last edited:
I can confirm that the error has no impact. We've seen it before in a similar situation.
 
Back
Top