Failed update from 11.0.9 to 11.5.30

[webbing]

Tried to update Plesk from 11.0.9 update #60 to the latest stable version, which is 11.5.30. The process collapses shortly after the start, with the attached error log.

Probably the most important lines are at the end. Does anybody know how to solve this issue?

Thank you in advance for your answers.

Attempt to remove 'php53-common' to resolve conflict has succeeded
Traceback (most recent call last):
File "/usr/local/psa/bin/yum_install", line 224, in ?
main()
File "/usr/local/psa/bin/yum_install", line 210, in main
inst, rem = installer.resolve(to_install, opts.remove, opts.tries)
File "/usr/local/psa/bin/yum_install", line 144, in resolve
raise Exception("Failed to solve dependencies:\n" + '\n'.join(msgs))
Exception: Failed to solve dependencies:
php53-common conflicts with php-common
Execute command /usr/local/psa/admin/bin/send-error-report install
Error: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

 

[IgorG]

Have you tried to remove package php53-common manually before upgrade?

 

[webbing]

Have you tried to remove package php53-common manually before upgrade?

I tried to remove it via the Plesk installer (remove PHP 5.3, install PHP 5) but it didn't worked.

Can you please send me some information about how should I do it manually?

Thank you!

 

[IgorG]

Try to use rpm package manager.

 

[webbing]

I tried to remove as sugested php53-common using the rpm package manager (yum). Unfortunately this process removed another 32 packages (which were related with php53-common) and most of the server services (including the Plesk engine) went down.

 

[IgorG]

I have suggested to use rpm but not yum package manager!
rpm can remove packages more finely, without considering the complex dependencies and so on. yum more blunt tool.
Now I suggest you contact Support Team.

 

[webbing]

Managed to solve the problem by applying http://kb.parallels.com/en/118306 and the SSH upgrade procedure.