Packagekit complaint: "database disk image is malformed"
Packagekit is whining at me, and complaining that there's a "Problem connecting to a software source". "More details" gives a very helpful "database disk image is malformed". Meanwhile "yum update" shows me the pending updates just fine, and is ready to install them. Then, if I run "yum clean all", that smacks packagekit into action, and it obediently shows me the pending updates. This has happened several times already. What's up with that? pgpXLt1pju9Us.pgp Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Database disk image is malformed
On Sun, Jan 24, 2010 at 11:38:45PM -0600, James Antill wrote: > On Fri, 2010-01-22 at 23:06 -0600, Matt Domsch wrote: > > I ran into this once recently, when I hit Ctrl-C at an inopportune > > moment while yum was running on that window. Like you, thought it was > > the RPM database that was corrupt, and like you did the same thing to > > no effect. > > > > # yum clean all > > > > had no effect either. > > > > To resolve, I deleted all the contents of /var/lib/yum/. It's kind of > > heavyweight, but it resolved it. You may try simply deleting > > /var/lib/yum/history/* first, and see if that's sufficient (assuming > > you don't need to be able to have yum roll back completed transactions > > to some previous state). If not, try deleting yumdb/ there. > > > > There may be a better way to handle this, but I'll let the yum experts > > chime in then. > > I've seen one other case of this, and indeed it was the yum history DB. > We can certainly give a better message (running: yum history new, will > give you a new history DB). But it's annoying that it happens, as AFAIK > we are using sqlite transactions everywhere. > Matt/Jim ... was there anything weird like /var/lib/yum being on NFS or > anything like that? For me, /var/lib/yum is on local storage. I'm sure I did hit Ctrl-C at some point to try to break out of it while it was downloading packages. -- Matt Domsch Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Database disk image is malformed
On Fri, 2010-01-22 at 21:35 -0500, Jim wrote: > FC12-x86_64/KDE > > #yum install > > Error: Database disk image is malformed > > I removed /var/lib/rpm/__db.** files > And then I did a ; > #rpm --rebuilddb * I may be confused but I am not aware that : rpm --rebuilddb has another argument, so what is the * doing on the command. > > But that still doesn't help when running yum. > What am I not doing right? -- === Many Myths are based on truth -- Spock, "The Way to Eden", stardate 5832.3 === Aaron Konstam telephone: (210) 656-0355 e-mail: akons...@sbcglobal.net -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Database disk image is malformed
On 01/23/2010 12:06 AM, Matt Domsch wrote: On Fri, Jan 22, 2010 at 09:35:49PM -0500, Jim wrote: FC12-x86_64/KDE #yum install Error: Database disk image is malformed I removed /var/lib/rpm/__db.** files And then I did a ; #rpm --rebuilddb * But that still doesn't help when running yum. What am I not doing right? I ran into this once recently, when I hit Ctrl-C at an inopportune moment while yum was running on that window. Like you, thought it was the RPM database that was corrupt, and like you did the same thing to no effect. # yum clean all had no effect either. To resolve, I deleted all the contents of /var/lib/yum/. It's kind of heavyweight, but it resolved it. You may try simply deleting /var/lib/yum/history/* first, and see if that's sufficient (assuming you don't need to be able to have yum roll back completed transactions to some previous state). If not, try deleting yumdb/ there. There may be a better way to handle this, but I'll let the yum experts chime in then. Thanks, Matt Remove contents from /var/lib/yum/history/* did the trick. THANKS MUCH MATT -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Database disk image is malformed
On Fri, Jan 22, 2010 at 09:35:49PM -0500, Jim wrote: > FC12-x86_64/KDE > > #yum install > > Error: Database disk image is malformed > > I removed /var/lib/rpm/__db.** files > And then I did a ; > #rpm --rebuilddb * > > But that still doesn't help when running yum. > What am I not doing right? I ran into this once recently, when I hit Ctrl-C at an inopportune moment while yum was running on that window. Like you, thought it was the RPM database that was corrupt, and like you did the same thing to no effect. # yum clean all had no effect either. To resolve, I deleted all the contents of /var/lib/yum/. It's kind of heavyweight, but it resolved it. You may try simply deleting /var/lib/yum/history/* first, and see if that's sufficient (assuming you don't need to be able to have yum roll back completed transactions to some previous state). If not, try deleting yumdb/ there. There may be a better way to handle this, but I'll let the yum experts chime in then. Thanks, Matt -- Matt Domsch Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Database disk image is malformed
On 01/22/2010 09:35 PM, Jim wrote: > FC12-x86_64/KDE > > #yum install > > Error: Database disk image is malformed > > I removed /var/lib/rpm/__db.** files > And then I did a ; > #rpm --rebuilddb * > > But that still doesn't help when running yum. > What am I not doing right? If I run Yumex from command line I get this; $ yumex running Current Settings autorefresh: True branding_title: 'Yum Extender NextGen' color_install: 'darkgreen' color_normal: 'black' color_obsolete: 'blue' color_update: 'red' debug: False disable_repo_page: False plugins: True proxy: '' recentdays: 14 repo_exclude: ['debug', 'source'] win_height: 850 win_sep: 300 win_width: 1600 yumdebuglevel: 2 /usr/lib/python2.6/site-packages/guihelpers/__init__.py:199: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead self.add_from_file(filename) eth0 (forcedeth) is connected /usr/lib/python2.6/site-packages/yumexgui/gui.py:179: DeprecationWarning: Use the new widget gtk.Tooltip self.tooltip = gtk.Tooltips() /usr/lib/python2.6/site-packages/yumexgui/gui.py:206: DeprecationWarning: Use the new widget gtk.Tooltip self.tooltip.set_tip(button, tooltip) eth0 (forcedeth) is connected Connected to an network eth0 (forcedeth) is connected Starting yum child process YUM: Loaded plugins: presto ERROR: Error in repository setup ERROR: database disk image is malformed You can try starting 'yumex -n' from a command line and deseleting the repositories causing problems and try again. Stopping yum child process Program Terminated What repositories would i deselect ? -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Database disk image is malformed
FC12-x86_64/KDE #yum install Error: Database disk image is malformed I removed /var/lib/rpm/__db.** files And then I did a ; #rpm --rebuilddb * But that still doesn't help when running yum. What am I not doing right? -- users mailing list users@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
