Upgraded pacman, now cannot reach any servers.

eyolf · 2012-01-19 02:09:24

So does that mean that the blacklist way is the safest, then? I'm having problems right now, after disabling ipv6, with samba (smbnetfs) and mpd...

Edit: the mpd problem was solved by following the wiki and hard-coding bind_to_address "127.0.0.1", and the smbnetfs seems to have been a temporary problem -- at least restarting the daemon worked well. All my slooooow network connection issues now seem to be ironed out.

Last edited by eyolf (2012-01-19 03:35:42)

tigrmesh · 2012-01-19 02:28:22

aChipmunk wrote:

I removed /etc/pacman.d/mirrorlist.pacnew maked sure /etc/pacman.conf pointed to /etc/pacman.d/mirrorlist (not mirrorlist.pacnew) and maked sure the mirrors i wanted to use are uncomented in /etc/pacman.d/mirrorlist but pacman still gives the same errors. . .

Forgive the thread hijack, but it's extremely important to merge the contents of a .pacnew or .pacsave file with the original file, instead of just deleting the new one.

Config files have changes. For example, not too long ago the URL for my favorite mirror changed. If I had deleted the mirrorlist.pacnew, I would have had errors every day when I ran pacman. Another thing is that Arch devs are continually making improvements. Config file changes are a natural result of that activity.

I use diffpac from the AUR to locate all .pacnew and .pacsave files. It has an option to call vimdiff with both the original config and the .pacnew. It works very well.

There's more information about .pacnew and .pacave files in the pacman man page. This wiki page also has information and ideas on how to manage them http://wiki.archlinux.org/index.php/Pac … save_Files

aChipmunk · 2012-01-19 03:27:20

tigrmesh wrote:

Config files have changes. For example, not too long ago the URL for my favorite mirror changed. If I had deleted the mirrorlist.pacnew, I would have had errors every day when I ran pacman. Another thing is that Arch devs are continually making improvements. Config file changes are a natural result of that activity.
I use diffpac from the AUR to locate all .pacnew and .pacsave files. It has an option to call vimdiff with both the original config and the .pacnew. It works very well.

I tried this and a full system upgrade using old pacman and i still cannot connect to any servers. I am also having some issues with grafics drivers and other things so I think I will just re-install arch. it's long ovedue.

Last edited by aChipmunk (2012-01-19 06:01:50)

ltorres · 2012-01-19 06:39:33

I'm still having the same problem, and am also considering a re-install.

I was wondering, how often does this happen? When someone does an update, all of a sudden things can get shifted out of place? I installed Arch maybe 2 weeks ago for my laptop that I use for school work. I'm currently studying software engineering and more or less don't have much time to tweak the system after every update. I'm actually considering going back to Fedora at this point

eyolf · 2012-01-19 10:00:07

Not very often, I would say, but it is wise to be attentive when you do a pacman -Syu, and not just automatically answer "yes" to everything. I'd say that whenever pacman asks "do you want to replace package x with package y?", it's a good idea to go to the web page and check for a notification (perhaps also to the forum and check for "Upgrade broke my system" posts...). In general, review the list of programs to be updated. Anything kernel related, and also pacman itself, check one extra time.
This is not to say that you can expect trouble. I've been using arch for seven years now, and in that time, I've only had one serious problem after an upgrade (something about a special partition table which wasn't caught in the testing period, resulting in a kernel panic during booting), and some minor glitches, but nothing that hasn't been fixed quite quickly. Which is quite good, considering that Arch is a bleeding-edge, rolling release distro, I'd say.

aChipmunk · 2012-01-20 04:53:14

I am headed to southern california linux expo tomorrow, I can pick up and install disk there! Anybody else coming?

mpnordland · 2012-01-20 20:45:52

I've added a bug in flyspray for this, it's really bugging me (pun not intended). I am available to run tests and give output.

falconindy · 2012-01-21 00:50:42

mpnordland wrote:

I've added a bug in flyspray for this, it's really bugging me (pun not intended). I am available to run tests and give output.

Not that I see... unless it was closed as a dupe of mine: https://bugs.archlinux.org/task/27988

Feel free to post output of the things mentioned in the ticket.

karol · 2012-01-21 00:58:04

Yup, closed as a duplicate: https://bugs.archlinux.org/task/28019

sweetthdevil · 2012-02-08 23:55:50

I too have the issue while trying to update the system tonight.

However After reading few post on the forum and wiki, I am not sure what is the best course of action, disabling IPV6? if so how, because the file mentioned in the wiki => /etc/modprobe.d/modprobe.conf isn't there or created (on my system at least) and the addition on the rc.conf on the module section is not there neither.

P.S. I always merge those *.pcanew file.

Many thanks for your assistance,

marogi · 2012-02-23 12:33:24

Any other workaround for connect() timeout errors? I've already disabled ipv6 in kernel, but I'm still getting "connect() timed out!" errors with pacman -Syu. Mirrors are ok - I can get to them from web browser and with wget and curl from command line.

OpenDNS DNS in resolv.conf also did not help.

elpres · 2012-02-24 13:39:44

I've got a similar problem, but the error I'm getting is not a timeout but "could not connect to host". I've started a thread about it yesterday here, and with generous help we've localized the problem to curl not using the proxy correctly. Setting "XferCommand" in /etc/pacman.conf to the one using wget solved the issue. Neither the default way of downloading worked (pacman --debug reported a curl error), nor the other "XferCommand", which is also curl-based. Downloading files with curl from the command line works though.

Sorry if I should have started a new thread; the name of this one sounded close enough.

letster · 2012-02-25 19:03:46

Hi. I solved this problem few weeks ago by disabling ipv6 in modprobe.conf. But now I have this issue again. After system update in 2012-02-19 I have installed amule and yesterday saw "failed retrieving file" message.
My pacman.log file:

[2012-02-19 12:36] Running 'pacman -Syu'
[2012-02-19 12:36] synchronizing package lists
[2012-02-19 12:36] starting full system upgrade
[2012-02-19 13:06] upgraded gsm (1.0.13-6 -> 1.0.13-7)
[2012-02-19 13:06] upgraded hawknl (1.68-2 -> 1.68-3)
[2012-02-19 13:06] upgraded id3v2 (0.1.12-1 -> 0.1.12-2)
[2012-02-19 13:06] upgraded libdiscid (0.2.2-1 -> 0.2.2-2)
[2012-02-19 13:06] upgraded libid3tag (0.15.1b-6 -> 0.15.1b-7)
[2012-02-19 13:06] upgraded libieee1284 (0.2.11-3 -> 0.2.11-4)
[2012-02-19 13:06] upgraded libirman (0.4.5-2 -> 0.4.5-3)
[2012-02-19 13:06] upgraded libmodplug (0.8.8.3-1 -> 0.8.8.4-1)
[2012-02-19 13:06] upgraded libofa (0.9.3-3 -> 0.9.3-4)
[2012-02-19 13:06] upgraded libzip (0.10-1 -> 0.10-2)
[2012-02-19 13:06] upgraded naev-data (0.5.0-1 -> 0.5.0-2)
[2012-02-19 13:06] upgraded neon (0.29.6-2 -> 0.29.6-3)
[2012-02-19 13:06] upgraded openlierox (0.58_rc3-3 -> 0.58_rc3-4)
[2012-02-19 13:06] upgraded openttd-opensfx (0.2.3-3 -> 0.2.3-4)
[2012-02-19 13:06] upgraded p11-kit (0.9-1 -> 0.11-1)
[2012-02-19 13:06] upgraded perl-error (0.17016-2 -> 0.17017-1)
[2012-02-19 13:06] upgraded speech-dispatcher (0.7.1-5 -> 0.7.1-6)
[2012-02-19 13:06] upgraded sudo (1.8.3.p2-2 -> 1.8.4-1)
[2012-02-19 13:07] upgraded vlc (1.1.13-6 -> 2.0.0-1)
[2012-02-20 14:18] Running 'pacman -S amule'
[2012-02-20 14:19] installed geoip (1.4.8-1)
[2012-02-20 14:19] installed crypto++ (5.6.1-3)
[2012-02-20 14:19] installed amule (10759-1)
[2012-02-24 20:20] Running 'pacman -Syu'
[2012-02-24 20:20] synchronizing package lists
[2012-02-24 22:42] Running 'pacman -S pacman'
[2012-02-24 22:43] upgraded pacman (4.0.2-1 -> 4.0.2-1)
[2012-02-24 22:43] Running 'pacman -Syu'
[2012-02-24 22:43] synchronizing package lists
[2012-02-24 22:46] Running 'pacman -Syu'
[2012-02-24 22:46] synchronizing package lists
[2012-02-24 23:31] Running 'pacman -Syu'
[2012-02-24 23:31] synchronizing package lists
[2012-02-24 23:36] Running 'pacman -Syu'
[2012-02-24 23:36] synchronizing package lists
[2012-02-25 12:12] Running 'pacman -Syu'
[2012-02-25 12:12] synchronizing package lists
[2012-02-25 13:23] Running 'pacman -Syy'
[2012-02-25 13:23] synchronizing package lists
[2012-02-25 18:18] Running 'pacman -Syu'
[2012-02-25 18:18] synchronizing package lists
[2012-02-25 20:49] Running 'pacman -S dwarffortress'
[2012-02-25 20:50] Running 'pacman -S pingus'

letster · 2012-02-27 08:37:48

Ok. On russian support forum I got solution that works for me.
Adding ipv6.disable=1 in /boot/grub/menu.lst file to the kernel line solves the problem.
Disabling ipv6 in /etc/modprobe.d/modprobe.conf don't work. Adding net.ipv6.conf.all.disable_ipv6 = 1 in /etc/sysctl.conf brings an error on system booting.

Gcool · 2012-02-27 09:23:48

Recently (since 3.2.6-2 iirc) ipv6 support has been integrated in the kernel itself. So there's no longer an ipv6 kernel module to disable/blacklist.

So either adding "ipv6.disable=1" to your bootloader config or "net.ipv6.conf.all.disable_ipv6 = 1" to /etc/sysctl.conf is the way to go from now on.

karol · 2012-02-27 09:31:28

Gcool wrote:

Recently (since 3.2.6-2 iirc) ipv6 support has been integrated in the kernel itself. So there's no longer an ipv6 kernel module to disable/blacklist.
So either adding "ipv6.disable=1" to your bootloader config or "net.ipv6.conf.all.disable_ipv6 = 1" to /etc/sysctl.conf is the way to go from now on.

https://wiki.archlinux.org/index.php/Disabling_IPv6

He shouldn't get an error when using /etc/sysctl.conf. He's not the first one to say that /etc/sysctl.conf didn't work for him https://bbs.archlinux.org/viewtopic.php … 9#p1059909
Please read https://bbs.archlinux.org/viewtopic.php … 0#p1061070 to see if we can easily fix this or is it some mysterious bug.

Last edited by karol (2012-02-27 09:32:55)

letster · 2012-02-27 09:34:31

Thank you, now I understand what was wrong. But with net.ipv6.conf.all.disable_ipv6 = 1 I receive an error:

error: "net.ipv6.conf.all.disable_ipv6" is an unknown key

Only grub disabling works for me.

hokasch · 2012-02-27 11:54:39

From your other post, sysctl seems to disable ipv6 (otherwise you would see a inet6 address).

Just to be sure - are you running the stock arch kernel (uname -a)?

[2012-02-20 14:18] Running 'pacman -S amule'
[2012-02-20 14:19] installed geoip (1.4.8-1)
[2012-02-20 14:19] installed crypto++ (5.6.1-3)
[2012-02-20 14:19] installed amule (10759-1)
[2012-02-24 20:20] Running 'pacman -Syu'
[2012-02-24 20:20] synchronizing package lists
<broken from here>

The last pacman action that worked was installing amule, crypto++ and geoip. There was no kernel update involved, likely you were already running the kernel with ipv6 build in so your modprobe ipv6 blacklist did not have any effect but pacman worked either way.
I have no idea why that would make trouble, but could you try removing amule, crypto++ and geoip, reboot and see if it has any effect?

letster · 2012-02-27 12:37:19

About an

error: "net.ipv6.conf.all.disable_ipv6" is an unknown key

, this is my fault. I added

ipv6.disable=1

to grub loader menu and left

net.ipv6.conf.all.disable_ipv6=1

in /etc/sysctl.conf in same time. When there is no ipv6.disable=1 in grub loader menu I don't receive this error.
Kernel is common:

[lolik@lolikpc ~]$ uname -a
Linux lolikpc 3.2.7-1-ARCH #1 SMP PREEMPT Tue Feb 21 09:51:29 CET 2012 x86_64 Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz GenuineIntel GNU/Linux

looks like I didn't done reboot after previous kernel update till I installed amule. After reboot, when I tried to update the system I saw the problem.

I tried this:
1. removed ipv6.disable=1 from menu.lst
2. net.ipv6.conf.all.disable_ipv6=1 option is in sysctl.conf
3. removed amule, crypto++, geoip
4. reboot system
After that pacman can't reach servers.

With ipv6.disable=1 in menu.lst pacman works fine.

Oh, and thank you to all ))

Last edited by letster (2012-02-27 12:39:01)

hokasch · 2012-02-27 12:50:27

looks like I didn't done reboot after previous kernel update till I installed amule.

ah crap - didn't think of that, sorry

wangyixiang · 2012-04-12 15:19:34

I'm meeting the same problem, and yes, it's proved, it should be bug of pacman 4.0 on ipv6 enabled but don't really have ipv6 kind system.
https://bugs.archlinux.org/task/28019
Thanks.

urza9814 · 2012-09-15 00:02:26

edit: Removed my comment, because I was in fact doing something stupid. Turns out my network was blocking pacman -- even though I could access the mirrors fine through regular ftp and http connections.

Last edited by urza9814 (2012-09-15 18:34:32)

noodles · 2012-09-16 12:13:04

Newb here trying to do an install off USB, and also seem to be stuck with this problem.
I get connection timeout when trying to fetch files.
My ISP seems to be vague about whether they have changed to IPV6 or not.

http://test-ipv6.com/ tells me:

 Your IPv4 address on the public Internet appears to be xx.xxx.xx.xxx
	     No IPv6 address detected [more info]
	    The World IPv6 Launch day is June 6th, 2012. Good news! Your current browser, on this computer and at this location, are expected to keep working after the Launch. [more info]
	    When a publisher offers both IPv4 and IPv6, your browser appears to be happy to take the IPv4 site without delay.
	    Connections to IPv6-only sites are timing out. Any web site that is IPv6 only, will appear to be down to you.
	    Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. 
            This may in the future restrict your ability to reach IPv6-only sites. [more info]

mirrorlist generated for IPV4:

 
## Arch Linux repository mirrorlist
## Generated on 2012-09-16
##

## Canada
Server = ftp://archlinux.mirror.rafal.ca/pub/archlinux/$repo/os/$arch
Server = http://archlinux.mirror.rafal.ca/$repo/os/$arch
Server = ftp://mirror.csclub.uwaterloo.ca/archlinux/$repo/os/$arch
Server = http://mirror.csclub.uwaterloo.ca/archlinux/$repo/os/$arch
Server = ftp://mirror.its.dal.ca/archlinux/$repo/os/$arch
Server = http://mirror.its.dal.ca/archlinux/$repo/os/$arch

I get connection timeout when trying to fetch files.

Is there a way to change USB files so that my connection does not try to use IPV6?
Thanks
Jim

Arch Linux

#26 2012-01-19 02:09:24

Re: Upgraded pacman, now cannot reach any servers.

#27 2012-01-19 02:28:22

Re: Upgraded pacman, now cannot reach any servers.

#28 2012-01-19 03:27:20

Re: Upgraded pacman, now cannot reach any servers.

#29 2012-01-19 06:39:33

Re: Upgraded pacman, now cannot reach any servers.

#30 2012-01-19 10:00:07

Re: Upgraded pacman, now cannot reach any servers.

#31 2012-01-20 04:53:14

Re: Upgraded pacman, now cannot reach any servers.

#32 2012-01-20 20:45:52

Re: Upgraded pacman, now cannot reach any servers.

#33 2012-01-21 00:50:42

Re: Upgraded pacman, now cannot reach any servers.

#34 2012-01-21 00:58:04

Re: Upgraded pacman, now cannot reach any servers.

#35 2012-02-08 23:55:50

Re: Upgraded pacman, now cannot reach any servers.

#36 2012-02-23 12:33:24

Re: Upgraded pacman, now cannot reach any servers.

#37 2012-02-24 13:39:44

Re: Upgraded pacman, now cannot reach any servers.

#38 2012-02-25 19:03:46

Re: Upgraded pacman, now cannot reach any servers.

#39 2012-02-27 08:37:48

Re: Upgraded pacman, now cannot reach any servers.

#40 2012-02-27 09:23:48

Re: Upgraded pacman, now cannot reach any servers.

#41 2012-02-27 09:31:28

Re: Upgraded pacman, now cannot reach any servers.

#42 2012-02-27 09:34:31

Re: Upgraded pacman, now cannot reach any servers.

#43 2012-02-27 11:54:39

Re: Upgraded pacman, now cannot reach any servers.

#44 2012-02-27 12:37:19

Re: Upgraded pacman, now cannot reach any servers.

#45 2012-02-27 12:50:27

Re: Upgraded pacman, now cannot reach any servers.

#46 2012-04-12 15:19:34

Re: Upgraded pacman, now cannot reach any servers.

#47 2012-09-15 00:02:26

Re: Upgraded pacman, now cannot reach any servers.

#48 2012-09-16 12:13:04

Re: Upgraded pacman, now cannot reach any servers.

Board footer