Hi,
yes, backing-up my rpm-db and rebuilding it was the solution. now all packages updated as expected. seems that there is a bug or something like that in rpm so that the db got corrupted.
mfg ;-) Christoph Illnar
GlobalAce.net Internetservice GmbH * WorldStore eCommerce www.globalace.net www.worldstore.at www.schatzmail.com
-----Ursprungliche Nachricht----- Von: David Huecking [mailto:david@huecking.net] Gesendet: Freitag, 02. August 2002 09:47 An: Christoph Illnar Cc: suse-security@suse.com Betreff: Re: [suse-security] SuSE Security Announcement: mod_ssl, mm (SuSE-SA:2002:028)
I saw this thing happen two times before. I did an update of many RPM-packages and the hell knows why when processing rpm seemed to stop working and took around 100% system load. I killed rpm after waiting some minutes and tried to process explicitly this one package, but rpm showed just the same behaviour... As a solution I made a backup of my rpm-database (/var/lib/rpm) and regenerated it with rpm --rebuilddb. After that the update ran as expected.
-- Eat, sleep and go running!
David Huecking.
On Thu, 1 Aug 2002, Christoph Illnar wrote:
Hello,
I installed the recommended updated packages on my suse 7.3. Everything worked fine when passed on as a list (command "rpm
-Fhv apache*
mod_ssl*"). mod_php4 worked fine too except mod_php4 that hangs after the
progress bar
is complete. after 30min of high cpu usage of rpm (~90%) I killed it...
any ideas what the problem could be?
On Fri 02 Aug 2002 21:19:38 NZST +1200, Christoph Illnar wrote:
Hi,
yes, backing-up my rpm-db and rebuilding it was the solution. now all packages updated as expected. seems that there is a bug or something like that in rpm so that the db got corrupted.
SuSE has fiddled with rpm in some way to make rpm understand the hacked .patch.rpm packages. rpm is buggy. With rpm-3.0.6-278 (shipped with SuSE 8.0), rpm -UvhF ....patch.rpm ....rpm will corrupt the rpm data base as well as make rpm terminate with error. The rpm-3.0.6-294 just installed will not fix the database up with --rebuilddb, a downgrade to -278 and --rebuilddb is required.
When not touching these .patch.rpm at all, all is fine.
IMHO these .patch.rpm are more trouble than they're worth. One even needs to download both .rpm and .patch.rpm, as -UvhF will only work with .rpm and YOU only with .patch.rpm. This, as far as I am concerned, is a waste of approx 90% (the patch ones are a little smaller, but not much) bandwidth and disk space.
All this is not directly security-related though.
Volker
[bcc feedback@suse.de]
On Sunday 04 August 2002 12:45 am, V K wrote:
SuSE has fiddled with rpm in some way to make rpm understand the hacked .patch.rpm packages. rpm is buggy. With rpm-3.0.6-278 (shipped with SuSE 8.0), rpm -UvhF ....patch.rpm ....rpm will corrupt the rpm data base as well as make rpm terminate with error.
All this is not directly security-related though.
Volker
Scuze me??? Your distro publisher's tools corrupts your database and its not a security issue for you???
I'd like to be your Banker.!!
-
Christoph Illnar -
John Andersen -
V K