Michael, On Wednesday June 18, 2003 11:25, [EMAIL PROTECTED] wrote: > hi all, > > after doing a number of rpm updates to my system, updatedb appears to have > broken. i have posted this problem now twice to this list without any > response whatsoever, but lets see if my latest discovery helps spur some > answers on! > > i have finally discovered what is breaking it, but don't know what to do > about it. > i went into /var/lib/slocate and deleted everything there - so basically a > clean slate. > i ran updatedb > it thought for a long time > then got the broken pipe > and ls /var/lib/slocate showed that it had successfully created > /var/lib/slocate.db.tmp > i did a mv slocate.db.tmp slocate.db > and i could locate things perfectly. > > so it appears that the broken pipe occurs when slocate is trying to move > slocate.db.tmp -> slocate.db. and this even happens when > /var/lib/slocate.db doesn't exist. > > so, for the final time - any suggestions?
Most likely you are out of drive space (somewhere). Do a "df -h" and see if there is a plenty of space left in all of your partitions. The partition where /tmp is must have more space than the size of your DB because that's where it does it's sort operation. The partition where /var is should have twice the free space of the DB. These are not necessarily _exact_ figures, so make sure you have some float in there as well. If you used an "update tool" (such as up2date, apt-get or red carpet) it likely stored a bunch of extra stuff in /var somewhere and is the cause of the post update failure. -- Brian Ashe CTO Dee-Web Software Services, LLC. [EMAIL PROTECTED] http://www.dee-web.com/ -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
