• 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

Resolved Upgrade to Plesk 17.8.11 failed - log4cplus

BobClaas

Basic Pleskian
When trying to upgrade it fails on the following error.

Code:
Attempt to remove 'psa-spf2' to resolve conflict has succeeded
Exception: Failed to solve dependencies:
plesk-lmlib-0.2.4-0centos.6.180209.1429.x86_64 requires log4cplus >= 1.2.0.1
plesk-lmlib-0.2.4-0centos.6.180209.1429.x86_64 requires liblog4cplus-1.2.so.5()(64bit)

Where can i find these dependencies or is there another solution?
 
Try to resolve this issue with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation

and after that run upgrade procedure again.
Also make sure that version of installed log4cplus is really >= 1.2.0.1:

# rpm -qa | grep log4cplus
log4cplus-1.2.0.1-0centos.7.180209.1429.x86_64
 
I did the reinstall and repair. The current version of log4cplus is still log4cplus-1.1.2-centos6.15011616.x86_64

# yum install http://autoinstall.plesk.com/PSA_17...plus-1.2.0.1-0centos.6.180209.1429.x86_64.rpm
Results in missing other dependencies, which i can't find

Error: Package: plesk-lmlib-0.2.3-centos6.825.16120615.x86_64 (@PLESK_17_5_3-dist)
Requires: liblog4cplus-1.1.so.9()(64bit)
Removing: log4cplus-1.1.2-centos6.15011616.x86_64 (@/log4cplus-1.1.2-centos6.15011616.x86_64)
liblog4cplus-1.1.so.9()(64bit)
Updated By: log4cplus-1.2.0.1-0centos.6.180209.1429.x86_64 (/log4cplus-1.2.0.1-0centos.6.180209.1429.x86_64)

Then i found this thread
#ln -s /usr/lib64/liblog4cplus-1.1.so.9.0.1 /usr/lib64/liblog4cplus.so

On some servers, the workaround does not work. Only a remove with --nodeps has helped:
1) rpm -e --nodeps log4cplus.x86_64

2) wget [URL='http://autoinstall.plesk.com/PSA_17.0.17/dist-rpm-CentOS-7-x86_64/engine/log4cplus-1.1.2-centos7.16071418.x86_64.rpm']http://autoinstall.plesk.com/PSA_17...e/log4cplus-1.1.2-centos7.16071418.x86_64.rpm


3) rpm -i http://autoinstall.plesk.com/PSA_17...e/log4cplus-1.1.2-centos7.16071418.x86_64.rpm

4) rpm -qi log4cplus | grep Vendor
shows:Vendor : Plesk[/URL]

Both didn't work, but removing package with rpm -e --nodeps log4cplus.x86_64 i could reinstall it.

This resulted in:
Plesk pre-upgrade check
/usr/bin/sw-engine: error while loading shared libraries: liblog4cplus-1.1.so.9: cannot open shared object file: No such file or directory

rpm -i http://autoinstall.plesk.com/PSA_17...e/log4cplus-1.1.2-centos7.16071418.x86_64.rpm
error: Failed dependencies:
libc.so.6(GLIBC_2.14)(64bit) is needed by log4cplus-1.1.2-centos7.16071418.x86_64
libc.so.6(GLIBC_2.17)(64bit) is needed by log4cplus-1.1.2-centos7.16071418.x86_64

I dont know where to move from here...
 
just something i noticed looking at your attempts. You seem to be on CentOS 6. Your original entry suggests that.
I did the reinstall and repair. The current version of log4cplus is still log4cplus-1.1.2-centos6.15011616.x86_64
whereas as part of your attemps to resolve you try to load packages for CentOS7?
 
Another thought on that...

I seem to remember that log4cplus was loaded from the EPEL repo, which clashed with the plesk / centos one.

Please check if you got the epel repo enabled. If so, please temporarily disable, run yum update, to get the latest centos one, then attempt upgrade, and finally reenable the EPEL repo.

Just a thought :)

Cheers,
Tom
 
Thanks for helping.
It was centos6 log4cplus that is installed.
Disabled repel and followed your advise.

ran plesk installer and got:
Plesk pre-upgrade check
/usr/bin/sw-engine: error while loading shared libraries: liblog4cplus-1.1.so.9: cannot open shared object file: No such file or directory
 
Hi,
that would indicate that plesk thinks liblog4cplus-1.1 is there while it is not,
what do you get at the moment from a version check?
# rpm -qa | grep log4cplus
 
I was installing the log4cplus of plesk 17.8.11 while i still was on 17.5.8
Removing log4cplus and installing it from 17.5.8 fixed the issue.
 
Back
Top