Lorem ipsum dolor sit amet, consectetur adipiscing elit lobortis arcu enim urna adipiscing praesent velit viverra sit semper lorem eu cursus vel hendrerit elementum morbi curabitur etiam nibh justo, lorem aliquet donec sed sit mi dignissim at ante massa mattis.
Vitae congue eu consequat ac felis placerat vestibulum lectus mauris ultrices cursus sit amet dictum sit amet justo donec enim diam porttitor lacus luctus accumsan tortor posuere praesent tristique magna sit amet purus gravida quis blandit turpis.
At risus viverra adipiscing at in tellus integer feugiat nisl pretium fusce id velit ut tortor sagittis orci a scelerisque purus semper eget at lectus urna duis convallis. porta nibh venenatis cras sed felis eget neque laoreet suspendisse interdum consectetur libero id faucibus nisl donec pretium vulputate sapien nec sagittis aliquam nunc lobortis mattis aliquam faucibus purus in.
Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque. Velit euismod in pellentesque massa placerat volutpat lacus laoreet non curabitur gravida odio aenean sed adipiscing diam donec adipiscing tristique risus. amet est placerat in egestas erat imperdiet sed euismod nisi.
“Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque velit euismod in pellentesque massa placerat”
Eget lorem dolor sed viverra ipsum nunc aliquet bibendum felis donec et odio pellentesque diam volutpat commodo sed egestas aliquam sem fringilla ut morbi tincidunt augue interdum velit euismod eu tincidunt tortor aliquam nulla facilisi aenean sed adipiscing diam donec adipiscing ut lectus arcu bibendum at varius vel pharetra nibh venenatis cras sed felis eget dolor cosnectur drolo.
When running a 'yum check-update', I would receive an error. The error continued even after running 'yum clean all'.The error is shown below:# yum check-updateSetting up repositoriescore 100% |=========================| 1.1 kB 00:00updates 100% |=========================| 1.2 kB 00:00extras 100% |=========================| 1.1 kB 00:00Reading repository metadata in from local filesprimary.xml.gz 100% |=========================| 1.0 MB 00:00Traceback (most recent call last):File "/usr/bin/yum", line 29, in ?yummain.main(sys.argv[1:])File "/usr/share/yum-cli/yummain.py", line 94, in mainresult, resultmsgs = base.doCommands()File "/usr/share/yum-cli/cli.py", line 381, in doCommandsreturn self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)File "/usr/share/yum-cli/yumcommands.py", line 317, in doCommandypl = base.returnPkgLists(extcmds)File "/usr/share/yum-cli/cli.py", line 895, in returnPkgListsypl = self.doPackageLists(pkgnarrow=pkgnarrow)File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 994, in doPackageListsself.doRepoSetup()File "/usr/share/yum-cli/cli.py", line 109, in doRepoSetupself.doSackSetup(thisrepo=thisrepo)File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 338, in doSackSetupself.repos.populateSack(which=repos)File "/usr/lib/python2.4/site-packages/yum/repos.py", line 200, in populateSacksack.populate(repo, with, callback, cacheonly)File "/usr/lib/python2.4/site-packages/yum/yumRepo.py", line 91, in populatedobj = repo.cacheHandler.getPrimary(xml, csum)File "/usr/lib64/python2.4/site-packages/sqlitecachec.py", line 40, in getPrimary self.repoid))TypeError: Parsing primary.xml error: Start tag expected, '<' not foundThis took me way longer than it should have to figure out, but I determined from running 'createrpo', that the error was actually in a shared library.# createrepoTraceback (most recent call last):File "/usr/share/createrepo/genpkgmetadata.py", line 27, in ?import libxml2File "/usr/lib64/python2.4/site-packages/libxml2.py", line 1, in ?import libxml2modImportError: /usr/lib64/python2.4/site-packages/libxml2mod.so: undefined symbol: xmlXPathContextSetCache# ldd /usr/lib64/python2.4/site-packages/libxml2mod.solibxml2.so.2 => /usr/local/lib/libxml2.so.2 (0x00002b61705e9000)libc.so.6 => /lib64/libc.so.6 (0x00002b6170921000)libdl.so.2 => /lib64/libdl.so.2 (0x00002b6170c6f000)libm.so.6 => /lib64/libm.so.6 (0x00002b6170e74000)/lib64/ld-linux-x86-64.so.2 (0x0000555555554000)Notice /usr/local/lib in the above section.So, I then discovered the problem.# env|grep -i libLD_LIBRARY_PATH=/usr/local/libSomewhere along the way, someone set LD_LIBRARY_PATH in .bash_profile.Once the LD_LIBRARY_PATH environment variable was removed, the issue went away!