Description of problem: I am trying an update from Mageia 2 to Mageia 3 with the update icon appearing in the icon bar. When it comes to update media sources, it goes on for a while, but then it ends with a Windows error: ------------------------------------------- Impossible d'ajouter le média, erreurs rapportées : ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Backports » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Backports Debug » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted 32bit Backports » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Backports Testing » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Backports Testing Debug » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted 32bit Backports Testing » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Release » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Release Debug » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted 32bit Release » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Updates » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Updates Debug » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted 32bit Updates » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Updates Testing » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted Updates Testing Debug » ... échec de la récupération : rsync a échoué : sortie avec 23 pas de métadonnées trouvées pour le média « Tainted 32bit Updates Testing » -------------------------------------------------- Sorry it's French, but basically it seems it failed to update all the Tainted media sources. I guess it tried to update using a server which has no Tainted repository (I previously already encountered such servers and I was told it was up to the mirror servers to decide whether they want to provide these sources or not). But then when this happens, and I click ok, then nothing would happen for a while (no other window appearing for maybe 5 or 10 min, not sure if something was processing in background or something), and at some point another error window appears saying just: --------- Ãchec de l'installation Ãchec lors de l'ajout du média ----------- Then I would just click "ok" again, the blue Mageia update icon would turn to this orange circled-arrow icon when it's checking for updates, and finally disappear, leaving me no chance to try and update Mageia again until I reboot again (or find what binary I would be supposed to run to restart this update program). Version-Release number of selected component: Mageia 2. Steps to Reproduce: 1. Start the Mageia 2 to 3 update process; 2. Make it fail media updating (maybe unplug the connection while it is updating would simulate the issue?); 3. See Mageia update failed. I would expect that when this happens, it proposes us: 1/ to try again by selecting a specific media source by hand, just like when you set sources by hand in the GUI. That may be annoying for common users, but at least is a workaround for advanced users; 2/ to display a warning and propose to skip the failed step and continue anyway when only optional media update fails. In particular as I understand that tainted media are often absent on many mirrors, and this is still considered normal, then Mageia 3 update should continue even without these media (then up to the user to update these media later from another source in the usual GUI if needed). Reproducible: Steps to Reproduce:
seems a mirrors issue, you can still reproduce ? what does show urpmq --sources rpm ?
Just tested again. Well it happened again (failed Tainted media failure). But this time, after closing the error window, there was a new icon in the task bar, telling me that I should add a media source. So I clicked it, I let the GUI add a full set of sources, it updated once again, and once again at the end the Tainted media failed. But when I closed this, the icon saying there are package updates appeared! And all the packages were ".mga3". So look like it "somehow" worked though that was definitely not a clean distribution update and I am still wondering what happened. I will want to check all went well at my next reboot. Also just in case, I ran: ----------------------------- $ jehan@DarkMarmot ~/prog $ urpmq --sources rpm http://mageia.r0b0t.fr/linux/Mageia/distrib/2/x86_64/media/core/updates/rpm-4.9.1.3-2.1.mga2.x86_64.rpm rsync://ftp.tsukuba.wide.ad.jp/mageia/distrib/3/x86_64/media/core/release/rpm-4.11.0.1-1.mga3.x86_64.rpm ----------------------------- Is it normal that the release sources are marked 3, but the updates are still 2?
Hmm... ok so today I rebooted my computer and now I can't update my packages. There is the red icon telling me there are updates. I click it, insert my password, then a popup error tells me "Une erreur fatale est survenue: Couldn't open RPM DB () at /usr/lib/perl5/vendor_perl/5.16.3/Rpmdrake/open_db.pm line 74. ." Then when I click ok, the list of packages to update is empty. Well I have so many issues with this Mageia 3 update, I believe I'll do soon a new installation from scratch over it instead. :-/
>$ jehan@DarkMarmot ~/prog $ urpmq --sources rpm >http://mageia.r0b0t.fr/linux/Mageia/distrib/2/x86_64/media/core/updates/rpm-4.9.1.3-2.1.mga2.x86_64.rpm >rsync://ftp.tsukuba.wide.ad.jp/mageia/distrib/3/x86_64/media/core/release/rpm-4.11.0.1-1.mga3.x86_64.rpm ----------------------------- >Is it normal that the release sources are marked 3, but the updates are still 2? no it's not. maybe you can do urpmi.removemedia -a ; rm /var/cache/urpmi/mirrors.cache then add manually a mirrors with urpmi.addmedia --distrib $mirror with $mirror one from here http://mirrors.mageia.org/distrib?version=3&arch=x86_64 or with the mirrorlist api: urpmi.addmedia --distrib --mirrorlist and then check the updates: urpmi --auto-update
CC: sysadmin-bugs => thierry.vignaudComponent: Release (media or process) => RPM PackagesSource RPM: (none) => urpmi
$ LC_ALL=C urpmi.addmedia --distrib rsync://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/3/x86_64 error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch error: cannot open Packages index using db5 - (-30969) error: cannot open Packages database in /var/lib/rpm unable to open rpmdb ------------------------- It seems I can't add anymore any media source. :-/ Seems to be the same kind of error I had earlier with the GUI about the RPM DB which could not be opened.
maybe you can rebuild the database but I'm not sure this will work rm -f /var/lib/rpm/__db* rpm --rebuilddb beside that I have no ideas, sorry
Seemed like it worked, even though there were some version error/warning displayed: ------------------------------ root@DarkMarmot(1) /home/jehan # rm -f /var/lib/rpm/__db* root@DarkMarmot(1) /home/jehan # rpm --rebuilddb rpm: /lib64/liblzma.so.5: no version information available (required by /lib64/librpmio.so.3) /usr/bin/rpmdb: /lib64/liblzma.so.5: no version information available (required by /lib64/librpmio.so.3) ------------------------------- After this I had been able to urpmi.addmedia. Now I am in the process of "urpmi --auto-update". It is downloading packages but in the initial stage where I choose between packages, it already told me that some packages won't be installed because of some incompatible packages. Will wait until it is finished to check this all. Yet I think I may want to reinstall over my current system in the end anyway. After having so many problems, warning and such, I would feel better with a clean system to prevent more problems in the future.
Well, just to say that with all these commands, I managed to have a working Mageia 3. I will not make a new installation because I had no other problem, so I'll let it as is for now. I don't expect the issue being fixed for this release (unless this problem happens for many users), but if you ever understood what was the original issue, that would be awesome to have this kind of problem (failing media update) considered for when the Mageia 3 to 4 updater will be made. :-) Thanks!
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD