Kill all processes using rpm database (fuser /var/lib/rpm/* should reveal such processes) then run 'rm /var/lib/rpm/__db* '. Consider rebuilding rpm database after that ('rpm --rebuilddb'). This should unlock the database.
> -----Original Message----- > From: Brian Curtis [mailto:[EMAIL PROTECTED]] > Sent: Tue, January 21, 2003 6:30 PM > To: [EMAIL PROTECTED] > Subject: RPM stops responding > > > Hello, > > I just tried to rpm -e my MySQL 3.x rpms in preparation for MySQL 4 > when I ran into a bit of trouble. > > After trying to # rpm -e mysqlclient9-3.23.22-6 I ended up having to > kill -9 the process after 15 minutes since it seemed to stop > responding. > > Now every time I try any rpm query/update/delete, the process > goes into > sleep mode and has to be terminated with a kill -9. The output of ps > does not show any "rpm" commands running, and lsof shows the following > rpm-related files in use when rpm isn't stuck in sleep mode: > > /usr/lib/python2.2/site-packages/rpm404module.so > /usr/lib/librpm-4.0.4.so > /usr/lib/librpmdb-4.0.4.so > /usr/lib/librpmio-4.0.4.so > > Any ides how I can get rpm responding once more? I'd like to avoid a > reboot, if at all possible. > > -- > Best regards, > Brian Curtis > > > > -- > Psyche-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/psyche-list > -- Psyche-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list