Pacman unable to connect to mirrors.

Wesman26 · 2012-02-17 10:33:13

Okay, so I had this problem more recently as did some other fellows, you can see the original thread here. The ultimate solution seemed to be to disable ipv6, so I did it through /etc/modprobe.d/modprobe.conf.

More recently the problem returned and so I checked the wiki, and follwed the new instructions for disabling ipv6. I'm assuming the first part about the bootloader configuration meant that I was supposed to add

ipv6.disable_ipv6=1

to the kernel line in my /boot/grub/menu.lst; if this is my mistake please correct me. I then took the /etc/sysctl.conf precautions also outlined.

I still have the same problem; the error essentially reads:

error: failed retrieving file 'core.db' from lug.mtu.edu : Connection time-out

Except it says that for all 10 mirrors I have set as options and all the databases. If you insist on seeing my pacman.conf I can post it, but the only thing I've changed is adding the archlinuxfr server so I could install yaourt.

Does anyone see something going on here that I don't?

Update
So I haven't changed anything, but I did notice while trying to update the system multiple times hoping that I'll randomly succeed, that occasionally pacman will connect with a mirror, and from that point out it downloads whatever databases remain without problems. The weird part is that this is haphazard at best; it has yet to initiate this behavior on the same server twice, and it does it very rarely. I know it's not my internet connection, as I'm using the same computer to post this, and I can ping google (as well as the mirrors) just fine.

Last edited by Wesman26 (2012-02-17 10:44:24)

Juszi · 2012-02-17 11:04:56

Just wanted to report the same problem. Did everything according to the Wiki and still I'm facing timeouts. Help? Anyone?

Update:
Changed my DNS addresses to OpenDNS, works now. Had my router address set as nameserver in resolv.conf, after the change everything is fine; just switch the bloody thing to something else.

Last edited by Juszi (2012-02-17 11:25:10)

Avant-texte · 2012-02-17 12:17:33

@Wesman26, https://wiki.archlinux.org/index.php/Pa … tall_it.3F

Last edited by Avant-texte (2012-02-17 12:18:32)

falconindy · 2012-02-17 13:18:30

Avant-texte wrote:

@Wesman26, https://wiki.archlinux.org/index.php/Pa … tall_it.3F

How is that even remotely relevant?

.:B:. · 2012-02-17 13:29:34

Don't sweat it falconindy. After all that's what you do when Windows breaks as well .

mpnordland · 2012-02-17 19:42:41

I'm suffering from this too

micah@micah-dell|~|$:sudo pacman -Syu
Password: 
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from ftp.gtlib.gatech.edu : Connection time-out
error: failed retrieving file 'core.db' from mirrors.kernel.org : Connection time-out
error: failed retrieving file 'core.db' from cake.lib.fit.edu : Connection time-out
error: failed retrieving file 'core.db' from cake.lib.fit.edu : Connection time-out
error: failed retrieving file 'core.db' from www.gtlib.gatech.edu : Connection time-out
error: failed to update core (download library error)
error: failed retrieving file 'extra.db' from ftp.gtlib.gatech.edu : Connection time-out
error: failed retrieving file 'extra.db' from mirrors.kernel.org : Connection time-out
error: failed retrieving file 'extra.db' from cake.lib.fit.edu : Connection time-out
error: failed retrieving file 'extra.db' from cake.lib.fit.edu : Connection time-out
error: failed retrieving file 'extra.db' from www.gtlib.gatech.edu : Connection time-out
error: failed to update extra (download library error)
error: failed retrieving file 'community.db' from ftp.gtlib.gatech.edu : Connection time-out
error: failed retrieving file 'community.db' from mirrors.kernel.org : Connection time-out
error: failed retrieving file 'community.db' from cake.lib.fit.edu : Connection time-out
error: failed retrieving file 'community.db' from cake.lib.fit.edu : Connection time-out
error: failed retrieving file 'community.db' from www.gtlib.gatech.edu : Connection time-out
error: failed to update community (download library error)
error: failed retrieving file 'multilib.db' from ftp.gtlib.gatech.edu : Connection time-out
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (4): gtkspell-2.0.16-2  libart-lgpl-2.3.21-2  libpng-1.5.8-2
             librsync-0.9.7-6

Total Download Size:    0.34 MiB
Total Installed Size:   2.16 MiB
Net Upgrade Size:       -0.05 MiB

Proceed with installation? [Y/n] y
:: Retrieving packages from extra...
error: failed retrieving file 'gtkspell-2.0.16-2-x86_64.pkg.tar.xz' from ftp.gtlib.gatech.edu : Connection time-out
error: failed retrieving file 'gtkspell-2.0.16-2-x86_64.pkg.tar.xz' from mirrors.kernel.org : Connection time-out
error: failed retrieving file 'gtkspell-2.0.16-2-x86_64.pkg.tar.xz' from cake.lib.fit.edu : Connection time-out
error: failed retrieving file 'gtkspell-2.0.16-2-x86_64.pkg.tar.xz' from cake.lib.fit.edu : Connection time-out
error: failed retrieving file 'gtkspell-2.0.16-2-x86_64.pkg.tar.xz' from www.gtlib.gatech.edu : Connection time-out
warning: failed to retrieve some files from extra
error: failed retrieving file 'libart-lgpl-2.3.21-2-x86_64.pkg.tar.xz' from ftp.gtlib.gatech.edu : Connection time-out
error: failed retrieving file 'libart-lgpl-2.3.21-2-x86_64.pkg.tar.xz' from mirrors.kernel.org : Connection time-out
error: failed retrieving file 'libart-lgpl-2.3.21-2-x86_64.pkg.tar.xz' from cake.lib.fit.edu : Connection time-out
 libart-lgpl-2.3.21-...    68.1 KiB   294K/s 00:00 [######################] 100%
 libpng-1.5.8-2-x86_64    210.4 KiB   262K/s 00:01 [######################] 100%
:: Retrieving packages from community...
 librsync-0.9.7-6-x86_64   40.1 KiB  56.8K/s 00:01 [######################] 100%
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

karol · 2012-02-17 19:58:56

Wesman26, have you checked if ipv6 *is* getting blacklisted?
I have 'alias net-pf-10 off' in my /etc/modprobe.d/modprobe.conf and it does the job.

Wesman26 · 2012-02-17 20:26:48

I had my modprobe.conf taking care of the job before, but once I updated to the new kernel and I started looking around I realized that it probably isn't blacklisting ipv6 as it should. Or at least that's what the wiki made me think.

I didn't think to check whether or not ipv6 is actually being blacklisted since the last time I experienced this problem I found ipv6 to be the culprit, however

 lsmod | grep ipv6

returned no output, so the module must be blacklisted.

I now have no clue what could be causing this problem.

Update
So I removed the lines to disable ipv6 from the /etc/sysctl.conf and from my /boot/grub/menu.lst and after rerunning lsmod I still see no mention of an ipv6 module. Should I be using a different command to see if it's blacklisted? Since ipv6 is now built into the kernel would lsmod not show it?

Last edited by Wesman26 (2012-02-17 20:44:50)

azuiden · 2012-02-17 21:03:19

I am having the same issue. Since I narrowed it down to the kernel, I downgraded the kernel in hopes of finding a fix soon and continuing to work. Downgrading it did fix the pacman not resolving issue.

Last edited by azuiden (2012-02-17 21:04:03)

mpnordland · 2012-02-17 21:30:39

I should note that out of date systems are not, per se, the Right way to do things on Arch, but your post does tell us one thing: the builting ipv6 support in the kernel is causing this. Probably should file a bug. I'll do it in a while if it's not already done.

azuiden · 2012-02-17 21:35:59

mpnordland wrote:

I should note that out of date systems are not, per se, the Right way to do things on Arch, but your post does tell us one thing: the builting ipv6 support in the kernel is causing this. Probably should file a bug. I'll do it in a while if it's not already done.

Absolutely, and I don't like to downgrade a package any longer than I have too. However I have used up all my options to try and fix it and hit a roadblock with my knowledge so I did what have to get back to a working system. As soon as a fix is found I will get back up there.

But here's what I know. ipv6 with pacman hasn't ever played nice with me.
blacklisting the module has worked 100% of the time in the past to fix it
I am using google's dns and have used opendns to same result
using the blacklisting procedures to turn off ipv6 in sysctl in the current kernel causes pacman to not resolve
I fixed the issue by downgrading the kernel with the problem going away immiedately

I have tried updating my mirrors, using only ipv6 mirrors and different mirrors on the current kernel and nothing fixed it except downgrading.

Last edited by azuiden (2012-02-17 21:37:29)

mpnordland · 2012-02-17 21:37:31

I am using google's dns and have used opendns to same result

What result?

azuiden · 2012-02-17 21:38:40

mpnordland wrote:

I am using google's dns and have used opendns to same result
What result?

They worked. I ran into an issue awhile that my ISPs DNS weren't playing nice so I switched them over a long time ago.

mpnordland · 2012-02-17 21:40:39

Okay, then I'm going to use them as a work around

karol · 2012-02-17 21:43:03

Have you read https://bugs.archlinux.org/task/27988 ? Maybe you can prove some details so the devs can figure out if it's pacman, the kernel or something else's fault.

falconindy · 2012-02-17 22:40:36

The problem is in part that ipv6 is no longer a module. Its a built-in. That's why you don't see it in lsmod. The only way to disable ipv6 now is to append to your kernel cmdline.

karol · 2012-02-17 22:46:30

My mistake, I forgot to check which linux version is in [core].
Thanks falconindy for clarification.

mpnordland · 2012-02-17 23:03:19

The problem is, I did that, and the problem persists

Wesman26 · 2012-02-19 23:09:13

So, In the past couple days I hadn't really thought anything strange of it, but I'm not connecting to the internet on boot up. I'm using netcfg with wpa_supplicant as described in the wiki for wpa_supplicant. It was working fine up until the kernel update. I can still connect manually after using

 ip link set wlan0 up
wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
dhcpcd wlan0

but I've noticed now, after running dhcpcd that there are multiple instances of trying to communicate with an IPv6 router that doesn't exist. After a bit of waiting it does eventually connect. This tells me that the method described in the wiki on how to disable IPv6 is not working for me, because it's still apparently being used.

Update
Okay, so I looked at the bug report and I've ran some of the commands.
ip -6 r returns nothing

ip a returns

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:24:8c:46:46:09 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1492 qdisc mq state UP qlen 1000
    link/ether 00:22:43:77:49:76 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.3/24 brd 192.168.2.255 scope global wlan0

Here's my resolv.conf

# Generated by dhcpcd from wlan0
# /etc/resolv.conf.head can replace this line
domain Dynex
nameserver 192.168.2.1
nameserver 75.75.76.76
nameserver 75.75.75.75
# /etc/resolv.conf.tail can replace this line

I'm not clear on what pacman.strace or curl.strace are. They're not commands as far as my machine is concerned and if they're files I'm not sure where they are. I'll keep looking.

Last edited by Wesman26 (2012-02-19 23:41:43)

skunktrader · 2012-02-20 00:07:54

Wesman26 wrote:

but I've noticed now, after running dhcpcd that there are multiple instances of trying to communicate with an IPv6 router that doesn't exist. After a bit of waiting it does eventually connect. This tells me that the method described in the wiki on how to disable IPv6 is not working for me, because it's still apparently being used.

You didn't mention which method you were using to disable IPv6. Due to a build change, the method to disable IPv6 changed following the release of kernel 3.2.6-2. The wiki has been updated in the last couple of days.

karol · 2012-02-20 00:09:27

skunktrader wrote:

You didn't mention which method you were using to disable IPv6.

I think he did - in the first post.

skunktrader · 2012-02-20 00:20:26

karol wrote:

skunktrader wrote:
You didn't mention which method you were using to disable IPv6.
I think he did - in the first post.

Oops sorry. Please ignore my noise

jo-shva · 2012-02-20 15:43:43

Having the same problem here. I tried the new recomendations in the wiki for blacklisting ipv6 with /etc/sysctl.conf and grub.
Changing my DNS nameserver to either OpenDNS or GoogleDNS solves the problem.

Last edited by jo-shva (2012-02-20 16:50:29)

Wesman26 · 2012-02-21 05:25:29

Yeah, changing to OpenDNS appeared to work for me, but I still don't like it; I get extremely slow download times with pacman compared to what I used to get. It actually seems to effect most all operations; loading web pages in chromium takes quite a bit of time, and multiple packages I try to update in pacman get an error involving the operation being too slow (downloading less than 1024 bytes/sec over the last 10 seconds). It's actually so bad that the system fails to update because several packages can't be obtained. So OpenDNS apparently doesn't fix my problem...

Thank you all for being so helpful, but is there anything else to be done? I'm not willing to downgrade, and I kind of hate not having an updated system.

Update
So it looks like my /etc/resolv.conf keeps getting changed back to what it was before I edited it. I'm not sure how this keeps happening.

Even More Update
So with everything being as slow as it was I checked out the wiki for disabling ipv6 again. I noticed that they changed the kernel cmdline argument from

 ipv6.disable_ipv6=1

to

 ipv6.disable=1

but once I changed that I started getting errors during boot about the line in /etc/sysctl.conf not being an appropriate argument.

I've now commented out that line on /etc/sysctl.conf and my kernel cmdline is now appropriate. My resolv.conf is the same as it was before I changed it to OpenDNS because apparently adding those lines somehow makes it change back? I have no idea why still.

The good news is that I can now update things with pacman, though much more slowly than before the kernel update. I was used to getting download rates in excess of 500K/s, and in many cases more than 1M/s. Now my rates are generally less than 100K/s. Loading webpages and other internet activity seems to be a little slower now as well. What is going on?

Hopefully Final Update
Nevermind it looks like I've gotten most if not all my speed back. This was a weird bug; I'm not sure how it got fixed, but I'm glad it did...

Thank you all for all your help!!

Last edited by Wesman26 (2012-02-21 07:01:39)

demoneyes905 · 2012-06-04 21:20:55

I don't know what might have happened in the time between the last post here and now but I got the same error recently. I had decided to update my Arch Linux box which hadn't been upgraded in a few months and ran into the same problem.

For some reason flushing the cache and manually downloading pacman seemed to solve my problem. I didn't have to disable IPv6 at all. Maybe a fix to pacman was applied?

Steps:
sudo pacman -Scc
sudo pacman -S pacman
sudo pacman -Syu

Arch Linux

#1 2012-02-17 10:33:13

Pacman unable to connect to mirrors.

#2 2012-02-17 11:04:56

Re: Pacman unable to connect to mirrors.

#3 2012-02-17 12:17:33

Re: Pacman unable to connect to mirrors.

#4 2012-02-17 13:18:30

Re: Pacman unable to connect to mirrors.

#5 2012-02-17 13:29:34

Re: Pacman unable to connect to mirrors.

#6 2012-02-17 19:42:41

Re: Pacman unable to connect to mirrors.

#7 2012-02-17 19:58:56

Re: Pacman unable to connect to mirrors.

#8 2012-02-17 20:26:48

Re: Pacman unable to connect to mirrors.

#9 2012-02-17 21:03:19

Re: Pacman unable to connect to mirrors.

#10 2012-02-17 21:30:39

Re: Pacman unable to connect to mirrors.

#11 2012-02-17 21:35:59

Re: Pacman unable to connect to mirrors.

#12 2012-02-17 21:37:31

Re: Pacman unable to connect to mirrors.

#13 2012-02-17 21:38:40

Re: Pacman unable to connect to mirrors.

#14 2012-02-17 21:40:39

Re: Pacman unable to connect to mirrors.

#15 2012-02-17 21:43:03

Re: Pacman unable to connect to mirrors.

#16 2012-02-17 22:40:36

Re: Pacman unable to connect to mirrors.

#17 2012-02-17 22:46:30

Re: Pacman unable to connect to mirrors.

#18 2012-02-17 23:03:19

Re: Pacman unable to connect to mirrors.

#19 2012-02-19 23:09:13

Re: Pacman unable to connect to mirrors.

#20 2012-02-20 00:07:54

Re: Pacman unable to connect to mirrors.

#21 2012-02-20 00:09:27

Re: Pacman unable to connect to mirrors.

#22 2012-02-20 00:20:26

Re: Pacman unable to connect to mirrors.

#23 2012-02-20 15:43:43

Re: Pacman unable to connect to mirrors.

#24 2012-02-21 05:25:29

Re: Pacman unable to connect to mirrors.

#25 2012-06-04 21:20:55

Re: Pacman unable to connect to mirrors.

Board footer