diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-March/013093.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-March/013093.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-March/013093.html | 181 |
1 files changed, 181 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-March/013093.html b/zarb-ml/mageia-dev/2012-March/013093.html new file mode 100644 index 000000000..0f1000de0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/013093.html @@ -0,0 +1,181 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Fatal errors with rpm + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Fatal%20errors%20with%20rpm&In-Reply-To=%3C1331745833.27321.1.camel%40foxbase%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="013092.html"> + <LINK REL="Next" HREF="013094.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Fatal errors with rpm</H1> + <B>Robert Fox</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Fatal%20errors%20with%20rpm&In-Reply-To=%3C1331745833.27321.1.camel%40foxbase%3E" + TITLE="[Mageia-dev] Fatal errors with rpm">list at foxconsult.net + </A><BR> + <I>Wed Mar 14 18:23:53 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="013092.html">[Mageia-dev] Fatal errors with rpm +</A></li> + <LI>Next message: <A HREF="013094.html">[Mageia-dev] Fatal errors with rpm +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#13093">[ date ]</a> + <a href="thread.html#13093">[ thread ]</a> + <a href="subject.html#13093">[ subject ]</a> + <a href="author.html#13093">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, 2012-03-14 at 18:19 +0100, Wolfgang Bornath wrote: +><i> 2012/3/14 Wolfgang Bornath <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>>: +</I>><i> > 2012/3/14 Wolfgang Bornath <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>>: +</I>><i> >> 2012/3/14 Wolfgang Bornath <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>>: +</I>><i> >>> 2012/3/14 Wolfgang Bornath <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>>: +</I>><i> >>>> 2012/3/14 Robert Fox <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">list at foxconsult.net</A>>: +</I>><i> >>>>> On Wed, 2012-03-14 at 16:10 +0100, Olav Vitters wrote: +</I>><i> >>>>>> On Wed, Mar 14, 2012 at 04:01:03PM +0100, Robert Fox wrote: +</I>><i> >>>>>> > Since the last few updates, I am experiencing erratic RPM db errors (on +</I>><i> >>>>>> > more than one machine): +</I>><i> >>>>>> +</I>><i> >>>>>> This should already be fixed. Maybe your mirror lags behind a bit. +</I>><i> >>>>>> +</I>><i> >>>>> +</I>><i> >>>>> I have the latest updates and it just happened - I will rebuild the db +</I>><i> >>>>> and report back if it happens again. +</I>><i> >>>> +</I>><i> >>>> Just did updates (including rpm-4.9.1.2-22.mga2) on 2 cauldron +</I>><i> >>>> installations. Last mirror sync with tier1 was 1:20 hours ago. +</I>><i> >>>> No problems with rpm db +</I>><i> >>> +</I>><i> >>> Now I did some more package management: +</I>><i> >>> - I opened a konsole window, did another check with 'urpmi +</I>><i> >>> --auto-update' which turned up no updates. After that rpm database was +</I>><i> >>> unlocked. Good. +</I>><i> >>> - I opened rpmdrake from the konsole and marked all KDE handbooks for +</I>><i> >>> uninstall. I clicked on OK and watched the output in the konsole +</I>><i> >>> window. +</I>><i> >>> - after the second handbook urpmi crashed with a segmentation fault +</I>><i> >>> and rpmdrake showed a message box with the same error (segfault). +</I>><i> >>> +</I>><i> >>> Then I rebooted the system and starting rpmdrake on the konsole returned: +</I>><i> >>> * getting lock on urpmi +</I>><i> >>> * [reading all synthesis files, ok] +</I>><i> >>> * Error: rpmdb: Thread/process 2794/1397..... failed: Thread died in +</I>><i> >>> Berkeley DB library +</I>><i> >>> * Error: db4 error from dbenv->failchk: DB_RUNRECOVERY: Fatal error, +</I>><i> >>> run database recovery +</I>><i> >>> * Error: Unable to open packages index, using db4 +</I>><i> >>> * Error: Unable to open package database in /var/lib/rpm +</I>><i> >>> * unlocking urpmi database +</I>><i> >>> +</I>><i> >>> Mind that this happened with latest updates as written in my previous mail. +</I>><i> >> +</I>><i> >> Adding info: erasing and rebuilding the db does not work. After +</I>><i> >> removing the _db* I run # rpm --rebuilddb which returns +</I>><i> >> : +</I>><i> >> * Error: rpmdb: Thread/process 2794/1397..... failed: Thread died in +</I>><i> >> Berkeley DB library +</I>><i> >> * Error: db4 error from dbenv->failchk: DB_RUNRECOVERY: Fatal error, +</I>><i> >> run database recovery +</I>><i> >> * Error: Unable to open packages index, using db4 +</I>><i> >> +</I>><i> >> Result: system is unusable now. +</I>><i> > +</I>><i> > Solution: I had to manually erase the lock file /var/lib/rpm/.RPMLOCK +</I>><i> > After that rebuilding the database worked and urpmi is usable again. +</I>><i> +</I>><i> Ok, here we go again: +</I>><i> I did the same as described earlier: +</I>><i> Updates, then opening rpmdrake and marking all handbook packages for +</I>><i> uninstall. After uninstalling one or two packages rpmdrake segfaults. +</I>><i> Opening it again shows the known errors about the rpm database. +</I>><i> +</I>><i> Unfortunately rpmdrake gives no other error message than "Segmentation +</I>><i> fault" - that's it. So I don't know whether the error messages about +</I>><i> the rpm database are just a result of the segfault or the cause of the +</I>><i> segfault. +</I>><i> +</I>><i> -- +</I>><i> wobo +</I> +Hello Wolfgang - + +Try the rebuild again: +rm -f /var/lib/rpm/__db* +rpm --rebuilddb + +and then simple do: +urpmi --auto-update -v + +That worked for me. When I tried rpmdrake, I also got the corruption +again. + +Cheers, +R.Fox + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="013092.html">[Mageia-dev] Fatal errors with rpm +</A></li> + <LI>Next message: <A HREF="013094.html">[Mageia-dev] Fatal errors with rpm +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#13093">[ date ]</a> + <a href="thread.html#13093">[ thread ]</a> + <a href="subject.html#13093">[ subject ]</a> + <a href="author.html#13093">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |