yum always hangs

[shwick]

I just did a clean install of rawhide, and i can't use yum at all. When i run update this is what i get:

[root@onyx ~]# yum -v update
Not loading "blacklist" plugin, as it is disabled
Loading "refresh-packagekit" plugin
Not loading "whiteout" plugin, as it is disabled
Config time: 0.063
Yum Version: 3.2.22
Setting up Package Sacks

And that's where it hangs. After this i have to close the terminal, and then kill the hanged process.
It doesnt seem to work at all, when i tried to use software repositories during installation, the installer hanged as well.

[sideways]

try 'yum --noplugins update'

if that works then perhaps remove the problem yum-plugin-* packages

[shwick]

I tried it, but it's still the same.
I've edited urls in /etc/yum.repos.d/fedora-rawhide.repo to http instead of https, because i read somewhere that this problem can be caused by this, but if you are using a proxy. I tried anyway, although i'm not using a proxy(i'm behind a router though), but still no use

[sideways]

try cleaning up

yum clean all

and finally, if that still doesn't work try

rm /var/lib/__db*
rpm --rebuilddb

[shwick]

Already tried it all, but still nothing...
clean all and rebuilddb doesn't hang, but yum update still does afterwards

[sideways]

can you see the internet through firefox?

if so, post it as a bug against rawhide.

and expect lots more issues from a rawhide install.

[Hlingler]

Hello shwick:

And welcome to the forum.

This thread has been moved to "Rawhide" because: that's where it belongs.

FedoraForum.org Guidelines

V

[typerlc]

Do you have network connectivity? Is it through a proxy? Does netstat -an show anything unusual? Does yum -d9 update show anything of interest. Does strace yum update show anything of interest?

[shwick]

Network connectivity is fine (i'm writing this from fedora). Netstat seems fine, yum -d9 update hangs on "Setting up package sacks" as well, strace churns a bunch of system calls, but stops with read(5,

[typerlc]

So you aren't using a proxy?

What is the 10-20 lines around the read? Also look for an open() or socket() system call that has = 5 at the end. What does that say?

The point of the netstat -an was to see if there were any problems connecting. Do you see any SYN SENT messages in that output?

[shwick]

No, i'm not using a proxy.

Here's the output of strace near the end(this time the last line is "read(6,")

socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 6
connect(6, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("152.46.7.222")}, 16) = 0
getsockname(6, {sa_family=AF_INET, sin_port=htons(50182), sin_addr=inet_addr("192.168.2.136")}, [16]) = 0
connect(6, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...}, 16) = 0
connect(6, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("66.35.62.166")}, 16) = 0
getsockname(6, {sa_family=AF_INET, sin_port=htons(33914), sin_addr=inet_addr("192.168.2.136")}, [16]) = 0
connect(6, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...}, 16) = 0
connect(6, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("80.239.156.215")}, 16) = 0
getsockname(6, {sa_family=AF_INET, sin_port=htons(36648), sin_addr=inet_addr("192.168.2.136")}, [16]) = 0
connect(6, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...}, 16) = 0
connect(6, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("209.132.176.120")}, 16) = 0
getsockname(6, {sa_family=AF_INET, sin_port=htons(37240), sin_addr=inet_addr("192.168.2.136")}, [16]) = 0
close(6)                                = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 6
connect(6, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("152.46.7.222")}, 16) = 0
getpeername(6, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("152.46.7.222")}, [16]) = 0
fcntl64(6, F_GETFL)                     = 0x2 (flags O_RDWR)
fcntl64(6, F_SETFL, O_RDWR)             = 0
time(NULL)                              = 1247045059
time(NULL)                              = 1247045059
write(6, "\200\177\1\3\1\0f\0\0\0\20\0\0009\0\0008\0\0005\0\0\210\0\0\207\0\0\204\0\0\26\0"..., 129) = 129
read(6, "\26\3\1\0*\2\0"..., 7)         = 7
time(NULL)                              = 1247045059
time(NULL)                              = 1247045059
read(6, "\0&\3\1JTI\243&\256\303\214\223WM\23L%\227\32@\340\253~\325fU\367\242\224e\r\320"..., 40) = 40
read(6, "\26\3\1\3\34"..., 5)           = 5
read(6, "\v\0\3\30\0\3\25\0\3\0220\202\3\0160\202\2w\240\3\2\1\2\2\3\t\225\3760\r\6\t*"..., 796) = 796
read(6, "\26\3\1\0\4"..., 5)            = 5
read(6, "\16\0\0\0"..., 4)              = 4
write(6, "\26\3\1\0\206\20\0\0\202\0\2002\217\304\202\25\36\317\344\264,5\n\276\307P\337F~\353\326\377W"..., 198) = 198
read(6, "\24\3\1\0\1"..., 5)            = 5
read(6, "\1"..., 1)                     = 1
read(6, "\26\3\1\0000"..., 5)           = 5
read(6, "\20\0\200\22\2\32\33\0\315yJ4q\1X6\363\373n\345\250\270\22!M\243\n\30Ye|\17w"..., 48) = 48
fcntl64(6, F_GETFL)                     = 0x2 (flags O_RDWR)
fcntl64(6, F_SETFL, O_RDWR)             = 0
write(6, "\27\3\1\0\260\24\200/\35q\332P4\267q\227\304\227\317\203\324\345=(ZnL'\10\207e\361\216"..., 181) = 181
read(6,

There aren't any SYN_SENT messages in netstat, but here's the a part of the output:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State      
tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN      
tcp        0      0 0.0.0.0:56691               0.0.0.0:*                   LISTEN      
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      
tcp        0      0 127.0.0.1:631               0.0.0.0:*                   LISTEN      
tcp        0      0 127.0.0.1:25                0.0.0.0:*                   LISTEN      
tcp        0      0 192.168.2.136:36701         209.151.236.22:80           ESTABLISHED 
tcp        0      0 192.168.2.136:46162         74.125.39.19:80             TIME_WAIT   
tcp        0    181 192.168.2.136:54272         80.239.156.215:443          ESTABLISHED 
tcp        0      0 192.168.2.136:36700         209.151.236.22:80           ESTABLISHED 
tcp        0      0 192.168.2.136:44927         74.125.39.17:80             ESTABLISHED 
tcp        0    182 192.168.2.136:42099         209.132.176.120:443         FIN_WAIT1   
tcp        0      0 :::111                      :::*                        LISTEN      
tcp        0      0 :::22                       :::*                        LISTEN      
tcp        0      0 ::1:631                     :::*                        LISTEN      
udp        0      0 0.0.0.0:721                 0.0.0.0:*                               
udp        0      0 0.0.0.0:5353                0.0.0.0:*                               
udp        0      0 0.0.0.0:111                 0.0.0.0:*                               
udp        0      0 0.0.0.0:631                 0.0.0.0:*                               
udp        0      0 0.0.0.0:55444               0.0.0.0:*                               
udp        0      0 0.0.0.0:46518               0.0.0.0:*                               
udp        0      0 0.0.0.0:707                 0.0.0.0:*                               
udp        0      0 :::111                      :::*                                    
udp        0      0 :::707                      :::*

what i can see, one of the addresses that's been called with connect() is in FIN_WAIT1 state, but this doesn't tell me much

[typerlc]

Not much to go on unfortunately. But what I really needed from the netstat output was the line containing the ip address last connected to in the tcp output (in this case, 152.46.7.222)

It is possible that there is a server down somewhere, and that this will just fix itself sometime soon. Or try changing the yum repo files to point at a mirror list or directly to a particular machine (switch between baseurl and mirrorlist).

[Tigernuts]

This is exactly the problem I was having today, at exactly the same point.

For some reason my https:// connections get disallowed from the F11 box. I've only ever noticed it before when I can no longer access my email, now I see it has affected yum too.

I have absolutely NFI why it happens repeatedly for a week or so, then I have no problems for some months.

Power cycling my router and rebooting Fedora does the trick, until it barfs again.

If anyone has any leads on this, I'd be very grateful.

Cheers
Charlie

[CiaW]

The rawhide repo's are being swtiched to Fedora 13 this weekend, according to this thread (read the first message) Those with current F12 installs already have the fedora and update repo's enabled and the rawhide repo's disabled.

That might have some bearing on your issue... otherwise I don't know. The other messages in this thread were from July.