• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Error updating xmlrpc-c

DougCurtis

Basic Pleskian
It looks like plesk is requiring a specific version of xmlrpc-c since xmlrpc-c-c++ is dependent on it.

Loaded plugins: downloadonly, product-id, rhnplugin, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package xmlrpc-c.x86_64 0:1.16.24-1209.1840.el6 will be updated
--> Processing Dependency: xmlrpc-c = 1.16.24-1209.1840.el6 for package: xmlrpc-c-c++-1.16.24-1209.1840.el6.x86_64
---> Package xmlrpc-c.x86_64 0:1.16.24-1210.1840.el6 will be an update
---> Package xmlrpc-c-client.x86_64 0:1.16.24-1209.1840.el6 will be updated
---> Package xmlrpc-c-client.x86_64 0:1.16.24-1210.1840.el6 will be an update
--> Running transaction check
---> Package xmlrpc-c.i686 0:1.16.24-1209.1840.el6 will be installed
--> Processing Dependency: libxml2.so.2(LIBXML2_2.4.30) for package: xmlrpc-c-1.16.24-1209.1840.el6.i686
--> Processing Dependency: libxml2.so.2 for package: xmlrpc-c-1.16.24-1209.1840.el6.i686
---> Package xmlrpc-c.x86_64 0:1.16.24-1209.1840.el6 will be updated
--> Running transaction check
---> Package libxml2.i686 0:2.7.6-14.el6 will be installed
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:

1. You have an upgrade for xmlrpc-c which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of xmlrpc-c of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude xmlrpc-c.otherarch ... this should give you an error
message showing the root cause of the problem.

2. You have multiple architectures of xmlrpc-c installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.

3. You have duplicate versions of xmlrpc-c installed already.
You can use "yum check" to get yum show these errors.

...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).

Protected multilib versions: xmlrpc-c-1.16.24-1210.1840.el6.x86_64 != xmlrpc-c-1.16.24-1209.1840.el6.i686
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

#yum update --exclude xmlrpc-c.i686
Loaded plugins: downloadonly, product-id, rhnplugin, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package xmlrpc-c.x86_64 0:1.16.24-1209.1840.el6 will be updated
--> Processing Dependency: xmlrpc-c = 1.16.24-1209.1840.el6 for package: xmlrpc-c-c++-1.16.24-1209.1840.el6.x86_64
---> Package xmlrpc-c.x86_64 0:1.16.24-1210.1840.el6 will be an update
---> Package xmlrpc-c-client.x86_64 0:1.16.24-1209.1840.el6 will be updated
---> Package xmlrpc-c-client.x86_64 0:1.16.24-1210.1840.el6 will be an update
--> Finished Dependency Resolution
Error: Package: xmlrpc-c-c++-1.16.24-1209.1840.el6.x86_64 (@PSA_11_5_30-thirdparty)
Requires: xmlrpc-c = 1.16.24-1209.1840.el6
Removing: xmlrpc-c-1.16.24-1209.1840.el6.x86_64 (@anaconda-RedHatEnterpriseLinux-201206132210.x86_64/6.3)
xmlrpc-c = 1.16.24-1209.1840.el6
Updated By: xmlrpc-c-1.16.24-1210.1840.el6.x86_64 (rhel-x86_64-server-6)
xmlrpc-c = 1.16.24-1210.1840.el6
Available: xmlrpc-c-1.16.24-1200.1840.el6.x86_64 (rhel-x86_64-server-6)
xmlrpc-c = 1.16.24-1200.1840.el6
Available: xmlrpc-c-1.16.24-1200.1840.el6_1.4.x86_64 (rhel-x86_64-server-6)
xmlrpc-c = 1.16.24-1200.1840.el6_1.4
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Is there an updated xmlrpc-c-c++?
 
Back
Top