• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

librpm and librpmdb installation error

EduardoG

Basic Pleskian
Hi all.
I've installed a new centos x86 server for testing purposes on a virtual machine.
centos 5.5 is just updated, all latest official versions.

When I try to run plesk10 installer, I get errors about some missing libs.
ldd command shows me the missing libs:
librpmdb-4.3.so => not found
librpm-4.3.so => not found
The problem is that it's asking for old versions, as I already have them installed:
[root@centos ~]# rpm -qa |grep rpm
rpm-devel-4.4.2.3-20.el5_5.1
rpm-libs-4.4.2.3-20.el5_5.1
rpm-4.4.2.3-20.el5_5.1
rpm-python-4.4.2.3-20.el5_5.1

[root@centos ~]# locate librpm
/usr/lib/librpm-4.4.so
/usr/lib/librpmbuild-4.4.so
/usr/lib/librpmdb-4.4.so
/usr/lib/librpmio-4.4.so
How should I manage this issue?
 
Try to create symlinks to librpmdb-4.3.so and librpm-4.3.so from 4.4 at least.
 
Thanks, IgorG, already tried that, but ldconfig doesn't take care of them when updating.
Any other idea, but copying and renaming? :)
 
Thanks, IgorG, already tried that, but ldconfig doesn't take care of them when updating.
Any other idea, but copying and renaming? :)
Stupid me! I was running the wrong installer, for centos 4.2, which was located in the same directory.
I'm sorry :-(
 
Yes, really, described problem was suspiciously improbable :)
 
Back
Top