Resolved Some errors during Plesk update

[Zoo3]

I noticed that Plesk auto-update is failing and I am looking into the problem.

Plesk Installer is outputting the following error.

Exception: Failed to solve dependencies:
passenger-6.0.12-2.centos.7+p18.0.43.0+t220406.1225.x86_64 requires passenger-native-libs = 6.0.12-2.centos.7+p18.0.43.0+t220406.1225
passenger-devel-6.0.13-2.centos.7+p18.0.44.0+t220520.0639.x86_64 requires passenger = 6.0.13-2.centos.7+p18.0.44.0+t220520.0639
Error: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.

I'm unable to update passenger to 6.0.13 with yum. Or rather, there is no update.

Next I ran the plesk repair installation command. It then output the following error.

 Fixing permissions on Panel packages files
ERROR:[Errno 2] No such file or directory: '/opt/plesk/node/9/share/doc/plesk-nodejs9-9.10.1/CHANGELOG.md'

Bootstrapper repair finished.
Errors occurred while performing the following actions: fix Plesk packages permissions.
Check '/var/log/plesk/install/plesk_18.0.43_repair.log' and '/var/log/plesk/install/plesk_18.0.43_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.

exit status 1

plesk_18.0.43_repair.log records no errors. The contents of plesk_18.0.43_repair_problems.log is empty.
Am I having problems with Plesk updates because the version of the component I need is out of date?

---
Plesk 18.0.43, CentOS 7.9, MariaDB 10.5.16

 

[Zoo3]

yum list installed | grep nodejs

nodejs.x86_64                 2:8.17.0-1nodesource           @nodesource       
plesk-nodejs10.x86_64         10.16.0-19102813               @plesk-ext-nodejs
plesk-nodejs12.x86_64         12.4.0-19102813                @plesk-ext-nodejs
plesk-nodejs4.x86_64          4.9.1-18040317                 @plesk-ext-nodejs
plesk-nodejs6.x86_64          6.14.1-18040317                @plesk-ext-nodejs
plesk-nodejs8.x86_64          8.16.0-19102813                @plesk-ext-nodejs
plesk-nodejs9.x86_64          9.10.1-18040317                @plesk-ext-nodejs

I have uninstalled and reinstalled node.js using the Plesk updater with no change.

 

[IgorG]

I'd suggest you contact Plesk Support Team. They will check and fix this packages inconsistency directly on your server.

 

[Zoo3]

Is it impossible to install the latest versions of Passenger and Node myself?

 

[Zoo3]

There also seems to be a problem with component installation in Plesk 18.0.43. I found additional component updates present in the Plesk Installer (Plesk web UI). It was Postfix. But no matter how many times I successfully succeeded in that update, the update appears again.
Next I uninstalled Postfix once I The uninstallation completed without any problems. When I try to reinstall Posfix, the installation fails with the following error.　Qmail could be installed.

Is this the same cause?

Failed to install {'release': '2.centos.7+p18.0.43.0+t220406.1450', 'epoch': '2', 'version': '3.5.14', 'arch': 'x86_64', 'name': 'postfix'}:
Error while downloading packages metainfo: No package(s) available to install. Trying again.
Failed to install {'release': '2.centos.7+p18.0.43.0+t220406.1450', 'epoch': '2', 'version': '3.5.14', 'arch': 'x86_64', 'name': 'postfix'}:
Error while downloading packages metainfo: No package(s) available to install. Trying again.
Failed to install {'release': '2.centos.7+p18.0.43.0+t220406.1450', 'epoch': '2', 'version': '3.5.14', 'arch': 'x86_64', 'name': 'postfix'}:
Number of retries is exceeded.
InstallError: No package(s) available to install

ERROR: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Visit https://support.plesk.com/ to search for a solution.
exit status 1

 

[Zoo3]

The postfix issue was self-resolving.
I installed rpm directly and then installed Posftfix via Plesk UI and the installation was successful.

Similarly I also checked the passenger repository and passenger was still 6.0.12, not 6.0.13.

 

[Zoo3]

Would installing passenger 6.0.13-2 from here make the situation worse or would I succeed?

 

[Zoo3]

I finally got a call from support and the Plesk update was resolved.
I was using yum-priorities and the repo priority was the cause. I commented out the priority line in the repo and the update succeeded.

• CentOS-Base.repo
• epel.repo
• remi.repo