Bug 22262

Summary: A window opens with the message "... Could not find a mirror from mirrorlist $MIRRORLIST"
Product: Mageia Reporter: Christian C <bugzzzz>
Component: RPM PackagesAssignee: Mageia tools maintainers <mageiatools>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: choucroot, marja11
Version: 6Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: mgaonline-3.24.1-1.mga6 CVE:
Status comment:
Attachments: my /etc/urpmi/urpmi.cfg
my /etc/urpmi/urpmi.cfg
my update.txt

Description Christian C 2017-12-24 17:46:01 CET
Description of problem:
Every time when mgaapplet checks the update availability, a series of windows are displayed with the message "Une erreur fatale est survenue : impossible de trouver un miroir dans la liste $MIRRORLIST" that I could translate by something like "A fatal error has happened : Could not find a mirror from mirrorlist $MIRRORLIST".

ksysguard says that it is mgaapplet-update-checker which run this window.
The message displayed comes from mirrors.pm.

But I think I have mirrors configured because I can, when running MCC, do an update without problem.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. let the computer running and wait for magaapplet to start
2.
3.
Comment 1 Marja Van Waes 2017-12-25 17:02:18 CET
http://mirrors.mageia.org/api/mageia.5.x86_64.list?reason=update seems ok.

I'm wondering whether urpmi rejects broken mirrors, there are quite some that are broken now, even for Mageia 5 http://mirrors.mageia.org/status

Christian, can you please attach (don't paste) your /etc/urpmi/urpmi.cfg ?

and please do also attach update.txt that is the result of running in a konsole/terminal, as root:

   urpmi --auto-update --debug 2>&1 | tee update.txt


Thanks :-)

CC: (none) => marja11
Keywords: (none) => NEEDINFO
Assignee: bugsquad => mageiatools

Comment 2 Christian C 2017-12-25 21:21:59 CET
Created attachment 9855 [details]
my /etc/urpmi/urpmi.cfg
Comment 3 Christian C 2018-05-14 10:12:49 CEST
Created attachment 10152 [details]
my /etc/urpmi/urpmi.cfg

Attachment 9855 is obsolete: 0 => 1

Comment 4 Christian C 2018-05-14 10:15:48 CEST
Created attachment 10153 [details]
my update.txt

result of urpmi --auto-update --debug 2>&1 | tee update.txt
Comment 5 Christian C 2018-05-14 10:28:28 CEST
As I am now under mga 6 (and I hope I will stay with it), I re-activate this bug.

What is surprising is that I only get this error on my main desktop, installed from scratch (contrary to the above report where mga 5 was upgraded from mga 4, upgraded itself from mga 3, with the distribution on the DVD and sometimes errors during the upgrade).

I have 2 laptops and 2 desktop (1 x86_64, 1 i586) under mga 6 that have no problem.

Version: 5 => 6
Source RPM: mgaonline-3.15-1.mga5 => mgaonline-3.24.1-1.mga6

Alain Choucroot 2018-05-26 17:07:50 CEST

CC: (none) => choucroot

Comment 6 Alain Choucroot 2018-05-26 17:18:30 CEST
I have also encountered this bug. I applied the following workaround (== changing the distrib link): 
1) urpmi.removemedia -a
2) urpmi.addmedia --distrib http://ftp.free.fr/mirrors/mageia.org/distrib/6/x86_64
3) urpmi --auto-update

Now updates work fine, but mgaapplet is still lost. After rebooting my machine, if i wait 5 minutes so that mgaapplet automatically launches a check, the $MIRRORLIST error notification has disappeared, but a new one as "no update media configured". Yet "urpmi --auto-update" works fine.

And what's weird is that in logs, it tries to update unselected media, for example all the backports.
Comment 7 Christian C 2018-06-09 16:56:21 CEST
Yes, it works.
I replaced 6 by 5 because I still can't upgrade (see https://bugs.mageia.org/show_bug.cgi?id=23026#c13) and get the same result.

In addition, the "no update media configured" notification is an old story coming from 2013-03-14 for my part (https://bugs.mageia.org/show_bug.cgi?id=9386) and that has probably been lost in twists and turns of bugzilla.

Maybe Mageia team lacks maintainers to resolve this problem.
Comment 8 Marja Van Waes 2020-04-29 15:41:30 CEST
(In reply to Christian CHEVALIER from comment #7)

> 
> Maybe Mageia team lacks maintainers to resolve this problem.

We always need more hands on deck, like (afaik) every software project. If you know of anyone who'd be interested in helping, please let her or him have a look at https://wiki.mageia.org/en/Contributing.

Anyway, is this issue still valid for Mageia 7?
If so, please change "Version:" in the upper left of this report to "7"
If not, then please close this report as OLD (since support for Mga6 ended in 2019)

Thanks :-)
Comment 9 Marja Van Waes 2020-07-31 12:55:01 CEST
No reply, so closing as OLD

Resolution: (none) => OLD
Status: NEW => RESOLVED