Package Management/YUM Repository(s)
Good morning,
We're experiencing a 'strange' issue after installing RHEL 6 from the DVD media. It appears that there's two (2) different repository listings for a great deal of the installed packages. However, there are issues showing up such as :
==================================================
php: /usr/lib/libxml2.so.2: no version information available (required by php)
php: /usr/lib/libxml2.so.2: no version information available (required by php)
php: /usr/lib/libxml2.so.2: no version information available (required by php)
php: /usr/lib/libxml2.so.2: no version information available (required by php)
php: /usr/lib/libxml2.so.2: no version information available (required by php)
Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/xmlreader.so' - /usr/lib64/php/modules/xmlreader.so: symbol xmlTextReaderSetup, version LIBXML2_2.6.28 not defined in file libxml2.so.2 with link time reference in Unknown on line 0
Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/xsl.so' - /usr/lib64/libxslt.so.1: symbol xmlXPathCompiledEvalToBoolean, version LIBXML2_2.6.27 not defined in file libxml2.so.2 with link time reference in Unknown on line 0
==================================================
I check the `libxml2` installation:
==================================================
[root@someserver /etc]$> yum info libxml2
==================================================
The issue here (it appears) is the repository : rhel-x86_64-server-6 vs anaconda-RedHatEnterpriseLinux-201009221801.x86_64...
I don't have a single clue as to 'how' this may have occurred during the installation, as I didn't execute or monitor the process. My question would be, is there any way that I can correct this with having to reimage the whole damn system (again!)? Can any/all of the packages pointing to the `anaconda-RedHatEnterpriseLinux-201009221801.x86_64` install to use the RHN Support repository (`rhel-x86_64-server-6`)? I have the feeling this is most likely a) something that I'm not alone in seeing and b) corrected by some process and/or command(s) that are just not apparent to me at this point in time...
Any/all input is greatly appreciated, and please let me know if I've not included anything relevant to the issues here that would help out. Thanx SO MUCH in advance for the assistance!!!
Responses
Hi Michael,
Can you check whether there is a repo file corresponding to anaconda-RedHatEnterpriseLinux-201009221801.x86_64 configured in /etc/yum.repos.d/*.repo? If so, you can try disabling it (set enabled=0 in the .repo file) and see if that resolves your yum issue.
Regarding the php issue, are you using the php package from the Red Hat channel/media, or did you install php from somewhere else (such as the upstream version)?
Regards,
John Ruemker, RHCA
Red Hat Technical Account Manager
Online User Groups Moderator
Are you using a Red Hat Network Satellite, or connecting directly to RHN? You can check by seeing if serverURL in /etc/sysconfig/rhn/up2date points to https://xmlrpc.rhn.redhat.com/XMLRPC or to a different location.
The reason I ask is that the only way I can figure your system is showing this alternate repository without having a repo configured in /etc/yum.repos.d/ is that you are registered to a custom channel on your Red Hat Network Satellite. Channels from RHN and RHNS do not use /etc/yum.repos.d/ repositories, and instead are accessed via the yum-rhn-plugin. Knowing whether your system is pointing to RHN or a custom location will tell us where this channel might be coming from.
Regarding php version, you can run:
# rpm -q php
The current version offered by Red Hat in RHEL 6 is php-5.3.2-6.el6[.0_1], and so if your differs from this (or the command doesn't return a result), it means you obtained php from somewhere else. This would be relevant because that version may depend on a different version of libxml2 than what we offer, resulting in the errors you are seeing. If you are using the RHEL 6 version, we'll need to do some further investigation to determine the cause of your error.
Regards,
John Ruemker, RHCA
Red Hat Technical Account Manager
Online User Groups Moderator