-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Dear,
Recently I have noticed that on all my CentOS machines the CentOS-Base.repo file seems to have been modified resulting in all baseurl= lines being commented out.
Did I miss something that was planned or is this a bug?
Best regards,
- -- Tim Semeijn Babylon Network pgp 0x5B8A4DDF
Am 24.05.2015 um 13:45 schrieb Tim Semeijn:
Dear,
Recently I have noticed that on all my CentOS machines the CentOS-Base.repo file seems to have been modified resulting in all baseurl= lines being commented out.
That is the case for a very long time, even if it hasn't be the case all the time. Instead of baseurl the default is mirrorlist.
Did I miss something that was planned or is this a bug?
Best regards,
Tim Semeijn
Alexander
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Weird, as all CentOS machines under my control are suddenly giving the baseurl of Base repo not found error since this morning. Could be that mirrorlist is leading but all other options I found online to debug the error message seem to indicate that (un)commenting should fix it.
On 24-5-2015 14:10, Alexander Dalloz wrote:
Am 24.05.2015 um 13:45 schrieb Tim Semeijn:
Dear,
Recently I have noticed that on all my CentOS machines the CentOS-Base.repo file seems to have been modified resulting in all baseurl= lines being commented out.
That is the case for a very long time, even if it hasn't be the case all the time. Instead of baseurl the default is mirrorlist.
Did I miss something that was planned or is this a bug?
Best regards,
- -- Tim Semeijn
Alexander
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
- -- Tim Semeijn Babylon Network pgp 0x5B8A4DDF
On 05/24/2015 07:48 AM, Tim Semeijn wrote:
Weird, as all CentOS machines under my control are suddenly giving the baseurl of Base repo not found error since this morning. Could be that mirrorlist is leading but all other options I found online to debug the error message seem to indicate that (un)commenting should fix it.
For the Base (or os) section of the CentOS-Base.repo file, the default is:
=========================================
[base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep... #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
=========================================
(note: the mirrorlist line wrapped)
So mirrorlist returns a list of 10 geoip (by country) based servers where you can get updates ... here is a way to test:
http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os
(that lists the os update mirrors for your location based on your IP)
If you have issues doing updates, I would first do "yum clean all" as root and try again. If that does not work make sure the server can get a list of mirrors from mirrorlist. If your machine does not have a browser, you can print the list in a terminal with:
curl "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os"
If you can get a mirrorlist and you are getting errors still, then the issue has something to do with you yum connection to the mirrorlist servers. It could be proxy related, if you have a proxy . more info would be needed.
You CAN uncommnet the baseurl, but that is just one host, while mirrorlist gives you ten.
On 24-5-2015 14:10, Alexander Dalloz wrote:
Am 24.05.2015 um 13:45 schrieb Tim Semeijn:
Dear,
Recently I have noticed that on all my CentOS machines the CentOS-Base.repo file seems to have been modified resulting in all baseurl= lines being commented out.
That is the case for a very long time, even if it hasn't be the case all the time. Instead of baseurl the default is mirrorlist.
Did I miss something that was planned or is this a bug?
Best regards,
- -- Tim Semeijn
Alexander
Am 24.05.2015 um 16:11 schrieb Johnny Hughes:
On 05/24/2015 07:48 AM, Tim Semeijn wrote:
Weird, as all CentOS machines under my control are suddenly giving the baseurl of Base repo not found error since this morning. Could be that mirrorlist is leading but all other options I found online to debug the error message seem to indicate that (un)commenting should fix it.
[ ... ]
If you have issues doing updates, I would first do "yum clean all" as root and try again. If that does not work make sure the server can get a list of mirrors from mirrorlist. If your machine does not have a browser, you can print the list in a terminal with:
curl "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os"
Empty result.
If you can get a mirrorlist and you are getting errors still, then the issue has something to do with you yum connection to the mirrorlist servers. It could be proxy related, if you have a proxy . more info would be needed.
Hi Johnny,
I am getting the same problem with mirrorlist:
# LANG=C yum -d10 makecache Loading "fastestmirror" plugin Config time: 0.015 Running "init" handler for "fastestmirror" plugin Yum Version: 3.2.29 COMMAND: yum -d10 makecache Installroot: / Running "postreposetup" handler for "fastestmirror" plugin Loading mirror speeds from cached hostfile Error: Cannot find a valid baseurl for repo: base
Did run a "yum clean all" before.
]# LANG=C yum -d10 update Loading "fastestmirror" plugin Config time: 0.013 Running "init" handler for "fastestmirror" plugin Yum Version: 3.2.29 COMMAND: yum -d10 update Installroot: / Reading Local RPMDB rpmdb time: 0.001 Setting up Update Process Updating Everything Building updates object Setting up Package Sacks Running "postreposetup" handler for "fastestmirror" plugin Loading mirror speeds from cached hostfile Error: Cannot find a valid baseurl for repo: base
You CAN uncommnet the baseurl, but that is just one host, while mirrorlist gives you ten.
Something is screwed on the remote end.
Alexander
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Thanks for your replies.
curl "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os"
Same empty result here. Opening the link on my computer shows 10 mirrors as expected, but server side nothing.
- -- Tim Semeijn Babylon Network pgp 0x5B8A4DDF
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It looks like the culprit is IPv6 according to a post on the CentOS Mirrors mailing list (http://lists.centos.org/pipermail/centos-mirror/2015-May/008847.html):
Hello,
mirrorlist.centos.org currently doesn't correctly answer on IPv6 - The request succeeds superficially (200 OK), but the answer is empty:
~ $ curl -6 "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os" ~ $ curl -4 "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os" http://mirror.ibcp.fr/pub/Centos/6.6/os/x86_64/ http://distrib-coffee.ipsl.jussieu.fr/pub/linux/centos/6.6/os/x86_64/
http://mirror1.babylon.network/centos/6.6/os/x86_64/
ftp://ftp.free.fr/mirrors/ftp.centos.org/6.6/os/x86_64/ http://centos.quelquesmots.fr/6.6/os/x86_64/ http://ftp.rezopole.net/centos/6.6/os/x86_64/ http://fr2.rpmfind.net/linux/centos/6.6/os/x86_64/ http://mirror.in2p3.fr/linux/CentOS/6.6/os/x86_64/ http://mirrors.ircam.fr/pub/CentOS/6.6/os/x86_64/ http://mirrors.atosworldline.com/public/centos/6.6/os/x86_64/ ~ $ curl -I -6 "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os" HTTP/1.1 200 OK Server: nginx/1.0.15 Date: Sun, 24 May 2015 14:38:37 GMT Content-Type: text/plain Connection: keep-alive Content-Length: 0
~ $
Thanks for looking into it!
(Also, I wonder why the results don't contain centos.mirrors.ovh.net which should be closest - but that's another question for another time.)
Best regards, Felix Krohn
- -- Tim Semeijn Babylon Network pgp 0x5B8A4DDF
Am 24.05.2015 um 16:54 schrieb Tim Semeijn:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It looks like the culprit is IPv6 according to a post on the CentOS Mirrors mailing list (http://lists.centos.org/pipermail/centos-mirror/2015-May/008847.html):
Bingo.
[root@msg ~]# curl -6 "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os"; echo $? 0 [root@msg ~]# curl -4 "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os"; echo $? http://ftp.wrz.de/pub/CentOS/6.6/os/x86_64/ ftp://mirror.fraunhofer.de/centos.org/6.6/os/x86_64/ http://mirror.eu.oneandone.net/linux/distributions/centos/6.6/os/x86_64/ http://centos.datente.com/media/6.6/os/x86_64/ http://mirror.skylink-datacenter.de/centos/6.6/os/x86_64/ http://mirror.softaculous.com/centos/6.6/os/x86_64/ http://mirror.netcologne.de/centos/6.6/os/x86_64/ http://ftp.fau.de/centos/6.6/os/x86_64/ http://mirror.23media.de/centos/6.6/os/x86_64/ http://mirror.jgotteswinter.com/centos/6.6/os/x86_64/ 0
Alexander
On 05/24/2015 10:00 AM, Alexander Dalloz wrote:
Am 24.05.2015 um 16:54 schrieb Tim Semeijn:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It looks like the culprit is IPv6 according to a post on the CentOS Mirrors mailing list (http://lists.centos.org/pipermail/centos-mirror/2015-May/008847.html):
Bingo.
[root@msg ~]# curl -6 "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os"; echo $? 0 [root@msg ~]# curl -4 "http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os"; echo $? http://ftp.wrz.de/pub/CentOS/6.6/os/x86_64/ ftp://mirror.fraunhofer.de/centos.org/6.6/os/x86_64/ http://mirror.eu.oneandone.net/linux/distributions/centos/6.6/os/x86_64/ http://centos.datente.com/media/6.6/os/x86_64/ http://mirror.skylink-datacenter.de/centos/6.6/os/x86_64/ http://mirror.softaculous.com/centos/6.6/os/x86_64/ http://mirror.netcologne.de/centos/6.6/os/x86_64/ http://ftp.fau.de/centos/6.6/os/x86_64/ http://mirror.23media.de/centos/6.6/os/x86_64/ http://mirror.jgotteswinter.com/centos/6.6/os/x86_64/ 0
IPv6 support is not always solid everywhere for us (as our mirrors are all donated) , we will troubleshoot as soon as we can.