CentOS5 update problem solved

Share on TwitterSubmit to StumbleUponDigg This
Running transaction check ---> Package libxml2.i386 0:2.6.26-2.1.2.8 set to be updated ---> Package xulrunner.i386 0:1.9.0.12-1.el5 set to be updated ---> Package libxml2-python.i386 0:2.6.26-2.1.2.8 set to be updated ---> Package libtiff.i386 0:3.8.2-7.el5_3.4 set to be updated ---> Package apr.i386 0:1.2.7-11.el5_3.1 set to be updated ---> Package bind-utils.i386 30:9.3.4-10.P1.el5_3.3 set to be updated ---> Package kernel.i686 0:2.6.18-128.4.1.el5 set to be installed ---> Package nss.i386 0:3.12.3.99.3-1.el5.centos.2 set to be updated ---> Package apr-util.i386 0:1.2.7-7.el5_3.2 set to be updated ---> Package tomcat5-servlet-2.4-api.i386 0:5.5.23-0jpp.7.el5_3.2 set to be updated ---> Package bind-libs.i386 30:9.3.4-10.P1.el5_3.3 set to be updated ---> Package tomcat5-jsp-2.0-api.i386 0:5.5.23-0jpp.7.el5_3.2 set to be updated ---> Package python.i386 0:2.4.3-24.el5_3.6 set to be updated ---> Package nss-tools.i386 0:3.12.3.99.3-1.el5.centos.2 set to be updated ---> Package kernel-headers.i386 0:2.6.18-128.4.1.el5 set to be updated ---> Package nspr.i386 0:4.7.4-1.el5_3.1 set to be updated ---> Package firefox.i386 0:3.0.12-1.el5.centos set to be updated Traceback (most recent call last): File "/usr/bin/yum", line 29, in ? yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 229, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 145, in main (result, resultmsgs) = base.buildTransaction() File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 647, in buildTransaction (rescode, restring) = self.resolveDeps() File "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 704, in resolveDeps for po, dep in self._checkFileRequires(): File "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 939, in _checkFileRequires if not self.tsInfo.getOldProvides(filename) and not self.tsInfo.getNewProvides(filename): File "/usr/lib/python2.4/site-packages/yum/transactioninfo.py", line 414, in getNewProvides for pkg, hits in self.pkgSack.getProvides(name, flag, version).iteritems(): File "/usr/lib/python2.4/site-packages/yum/packageSack.py", line 300, in getProvides return self._computeAggregateDictResult("getProvides", name, flags, version) File "/usr/lib/python2.4/site-packages/yum/packageSack.py", line 470, in _computeAggregateDictResult sackResult = apply(method, args) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 861, in getProvides return self._search("provides", name, flags, version) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 43, in newFunc return func(*args, **kwargs) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 837, in _search for pkg in self.searchFiles(name, strict=True): File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 43, in newFunc return func(*args, **kwargs) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 586, in searchFiles self._sql_pkgKey2po(rep, cur, pkgs) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 470, in _sql_pkgKey2po pkg = self._packageByKey(repo, ob['pkgKey']) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 413, in _packageByKey po = self.pc(repo, cur.fetchone()) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 68, in __init__ self._read_db_obj(db_obj) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 94, in _read_db_obj setattr(self, item, _share_data(db_obj[item])) TypeError: unsubscriptable object After some searching and checking several suggestions, I found the cause and solution to be very simple. The yum cache had become corrupted. The solution: cd /var/cache/yum rm -rf * yum makecache See below Sponsored Links

That cured it.

yum update then worked perfectly. Many thanks to http://just-another.net.
Share on TwitterSubmit to StumbleUponDigg This
In: linuxAuthor: EditorComments (0)

Email server software

Share on TwitterSubmit to StumbleUponDigg This
Zimbra Collaboration Suite (ZCS) Open Source Edition. When I first attempted to install it, things got sticky. The main issue for me was that it needs a DNS server present which needs to point to itself (internal IP address) for all domains you add to your Zimbra system. When I eventually figured out how to install and configure BIND on my email server, everything started to flow. Zimbra does complain here and there but, after your third or fourth install attempt you will find it works with very little extra effort. Go ahead and try it. Once you figure out the requirements, I promise you'll be impressed.
Share on TwitterSubmit to StumbleUponDigg This