I just installed a fresh 3.3 system (because those are the ISO's I had on hand). Upon running yum update, it starts to download headers and then stalls. I hit Ctl-C and it continues to download about 4-5 more headers and stalls. I hit Ctl-C again and it pulls a few more headers. Anyone seen this and/or know how to fix it? TIA Mike
Have you tried manually editing them mirror(s) in the config from default ? On Fri, 25 Feb 2005 20:42:12 -0600, Mike Kercher <mike at camaross.net> wrote:> I just installed a fresh 3.3 system (because those are the ISO's I had on > hand). Upon running yum update, it starts to download headers and then > stalls. I hit Ctl-C and it continues to download about 4-5 more headers and > stalls. I hit Ctl-C again and it pulls a few more headers. Anyone seen > this and/or know how to fix it? > > TIA > > Mike > > _______________________________________________ > CentOS mailing list > CentOS at caosity.org > http://lists.caosity.org/mailman/listinfo/centos >-- Beau Henderson http://www.iminteractive.net
You can strace the rpm command and find out where its stalling, You may find some __db files left over in /var/lib/rpm kill all the rpm processes, delete these files and try again, it may then continue... P. Francesco F wrote:> At 02.35 27/02/05, you wrote: > >> Nope...this was a plain Jane clean install...same as I''ve done >> hundreds of >> times. Initially, I had an Intel gigabit NIC in there and thought there >> might be a problem with it. I replaced it with a Broadcom gigabit >> NIC...same problem. Went down to an Intel 10/100 and the problems >> persists. >> I suppose I can deal with it. I''ve seen this before on an FC3 box >> leased at >> a datacenter; just wasn''t ever able to solve it. >> >> Mike > > > Hi, can you try to use rpm command, p.e rpm -qa? I installed yum on > RH9 (with problem on rpm database) and, when i run yum, it stalled: > the problem was rpm database. You can debug this option, run rpm -qa > -v (for verbose). If this is your problem, you can rebuild rpm > database with rpm --rebuilddb -v (for verbose) > > Francesco > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos
Matt Bottrell wrote:> It''s not a problem with name resolution or anything like that. > I was watching a netstat -tc in another window and when yum > froze, the connection to the mirror would show a SYN_SENT > status. After I hit Ctl-C, the yum process doesn''t > terminate...it continues to download more headers/rpms.I have a similar problem. yum is almost always stalling whether it''s a clean install (just did two clean installs of 3.4 on Friday) or an existing box (have eight 3.3 boxes that have been running for about 2 months now). However, if I hit ctrl-c, it just kills the process, it doesn''t continue it, so I was surprised to read your comments above. I end up always doing one of two things (or a combination of them): a) since I figured it was related to which mirror it might be hitting (never investigated, just assumed), I always just ctrl-c to end the process and then run yum again, thinking I might get a faster/closer mirror -- repeat this until it seems to be going at a decent pace b) alternatively, or after doing (a) a few times, I just walk away from it, and eventually (sometimes half an hour or more), it *will* complete, stalling all along the way at various points johnn
Johnn Tan wrote:> Matt Bottrell wrote: >> It''s not a problem with name resolution or anything like that. >> I was watching a netstat -tc in another window and when yum froze, >> the connection to the mirror would show a SYN_SENT status. After I >> hit Ctl-C, the yum process doesn''t terminate...it continues to >> download more headers/rpms. > > I have a similar problem. yum is almost always stalling whether it''s > a clean install (just did two clean installs of 3.4 on Friday) or an > existing box (have eight 3.3 boxes that have been running for about 2 > months now). > > However, if I hit ctrl-c, it just kills the process, it doesn''t > continue it, so I was surprised to read your comments above. > > I end up always doing one of two things (or a combination of them): > > a) since I figured it was related to which mirror it might be hitting > (never investigated, just assumed), I always just ctrl-c to end the > process and then run yum again, thinking I might get a faster/closer > mirror -- repeat this until it seems to be going at a decent pace > > b) alternatively, or after doing (a) a few times, I just walk away > from it, and eventually (sometimes half an hour or more), it *will* > complete, stalling all along the way at various points > > johnn > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centosMine will kill the process if it is somewhere between: Gathering header information file(s) from server(s) Server: CentOS-3 - Addons Server: CentOS-3 - Base Server: CentOS-3 - Extras Server: CentOS-3 - Updates Finding updated packages Downloading needed headers After it starts downloading headers and/or package and stalls, Ctl-C will allow the downloads to continue for a moment. Mike
> I have a similar problem. yum is almost always stalling whether it''s a > clean install (just did two clean installs of 3.4 on Friday) or an > existing box (have eight 3.3 boxes that have been running for about 2 > months now). > > However, if I hit ctrl-c, it just kills the process, it doesn''t continue > it, so I was surprised to read your comments above. > > I end up always doing one of two things (or a combination of them): > > a) since I figured it was related to which mirror it might be hitting > (never investigated, just assumed), I always just ctrl-c to end the > process and then run yum again, thinking I might get a faster/closer > mirror -- repeat this until it seems to be going at a decent pace > > b) alternatively, or after doing (a) a few times, I just walk away from > it, and eventually (sometimes half an hour or more), it *will* complete, > stalling all along the way at various points >Ditto.... Seems to have just started when I did an update this last weekend. Took about 1/2 hour just to download header info, previous to last weekend never had this problem.
Ken Godee wrote:>> I have a similar problem. yum is almost always stalling whether it''s >> a clean install (just did two clean installs of 3.4 on Friday) or an >> existing box (have eight 3.3 boxes that have been running for about >> 2 months now). >> >> However, if I hit ctrl-c, it just kills the process, it doesn''t >> continue it, so I was surprised to read your comments above. >> >> I end up always doing one of two things (or a combination of them): >> >> a) since I figured it was related to which mirror it might be hitting >> (never investigated, just assumed), I always just ctrl-c to end the >> process and then run yum again, thinking I might get a faster/closer >> mirror -- repeat this until it seems to be going at a decent pace >> >> b) alternatively, or after doing (a) a few times, I just walk away >> from it, and eventually (sometimes half an hour or more), it *will* >> complete, stalling all along the way at various points >> > > Ditto.... > > Seems to have just started when I did an update this last weekend. > Took about 1/2 hour just to download header info, previous to last > weekend never had this problem. >Thank god...I''m not crazy!!! :) Mike
Ken Godee wrote:> Ditto.... > > Seems to have just started when I did an update this > last weekend. Took about 1/2 hour just to download > header info, previous to last weekend never had this problem.I''ve always had the problem, I''ve almost come to just accept it as a yum thing. It happened to me all the time on FC2, too. Though it is true that this past weekend seems to have been particularly bad. johnn
<snip>>> >>Seems to have just started when I did an update this last weekend. >>Took about 1/2 hour just to download header info, previous to last >>weekend never had this problem. >> >> >> > >Thank god...I''m not crazy!!! :) > >Mike > >No, I noticed it too last night when I was updating a new production server. I kept having to CRTL-C it, and 1/2 of the time it would die and I would have to restart. The weird thing is that it was happening to the core RPM sites, as well as (for me) Dag RPM Repository, which really threw me for a loop. Was it something I said? ;-) Jonathan
On Mon, 2005-02-28 at 10:35 -0800, Johnn Tan wrote:>Ken Godee wrote: >> Ditto.... >> >> Seems to have just started when I did an update this >> last weekend. Took about 1/2 hour just to download >> header info, previous to last weekend never had this problem. > >I''ve always had the problem, I''ve almost come to just accept it as a yum >thing. It happened to me all the time on FC2, too. > >Though it is true that this past weekend seems to have been particularly >bad.It''s not ''just a yum thing''. There are lots and lots of users of yum out there w/o any problem like this. I know, I''ve heard from them. However, the problem of stalling on downloads is most often related to transparent proxies. -sv
I did an install of CentOS 2.1 this past weekend and ran into the same thing. While strace''ing the yum process I noticed it was hanging trying to talk to the same ip address each time. After it would timeout it would download a few more until it hit trying to talk to that same ip address again. nslookup of server configured in yum.conf returned several ip''s, one of which was not responding. My fix was to set it specifically to one of the ip addresses. Sorry I don''t have the specifics of which server it was that wasn''t responding, but I don''t have access to that box at the moment. Jamie On Mon, 28 Feb 2005, Mike Kercher wrote:> Ken Godee wrote: > >> I have a similar problem. yum is almost always stalling whether it''s > >> a clean install (just did two clean installs of 3.4 on Friday) or an > >> existing box (have eight 3.3 boxes that have been running for about > >> 2 months now). > >> > >> However, if I hit ctrl-c, it just kills the process, it doesn''t > >> continue it, so I was surprised to read your comments above. > >> > >> I end up always doing one of two things (or a combination of them): > >> > >> a) since I figured it was related to which mirror it might be hitting > >> (never investigated, just assumed), I always just ctrl-c to end the > >> process and then run yum again, thinking I might get a faster/closer > >> mirror -- repeat this until it seems to be going at a decent pace > >> > >> b) alternatively, or after doing (a) a few times, I just walk away > >> from it, and eventually (sometimes half an hour or more), it *will* > >> complete, stalling all along the way at various points > >> > > > > Ditto.... > > > > Seems to have just started when I did an update this last weekend. > > Took about 1/2 hour just to download header info, previous to last > > weekend never had this problem. > > > > Thank god...I''m not crazy!!! :) > > Mike > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
I''ve see this too... I just left it go for a while and did other things. -----Original Message----- From: centos-bounces@caosity.org [mailto:centos-bounces@caosity.org]On Behalf Of Mike Kercher Sent: Monday, February 28, 2005 1:10 PM To: ''CentOS discussion and information list'' Subject: RE: [Centos] yum stalls <?> Ken Godee wrote:>> I have a similar problem. yum is almost always stalling whether it''s >> a clean install (just did two clean installs of 3.4 on Friday) or an >> existing box (have eight 3.3 boxes that have been running for about >> 2 months now). >> >> However, if I hit ctrl-c, it just kills the process, it doesn''t >> continue it, so I was surprised to read your comments above. >> >> I end up always doing one of two things (or a combination of them): >> >> a) since I figured it was related to which mirror it might be hitting >> (never investigated, just assumed), I always just ctrl-c to end the >> process and then run yum again, thinking I might get a faster/closer >> mirror -- repeat this until it seems to be going at a decent pace >> >> b) alternatively, or after doing (a) a few times, I just walk away >> from it, and eventually (sometimes half an hour or more), it *will* >> complete, stalling all along the way at various points >> > > Ditto.... > > Seems to have just started when I did an update this last weekend. > Took about 1/2 hour just to download header info, previous to last > weekend never had this problem. >Thank god...I''m not crazy!!! :) Mike _______________________________________________ CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
On Mon, 28 Feb 2005, Jamie McKnight wrote:> > I did an install of CentOS 2.1 this past weekend and ran into the > same thing. While strace''ing the yum process I noticed it was hanging > trying to talk to the same ip address each time. After it would timeout > it would download a few more until it hit trying to talk to that same ip > address again. > > nslookup of server configured in yum.conf returned several ip''s, > one of which was not responding. My fix was to set it specifically to one > of the ip addresses. Sorry I don''t have the specifics of which server it > was that wasn''t responding, but I don''t have access to that box at the > moment.sounds like one of the mirror servers may be having problems. I also saw the issue last night updating a server and put it down to excess traffic caused by C4 syncing. If you can let us know which ip then I can investigate - otherwise will try to deduce later. Lance> > Jamie > > On Mon, 28 Feb 2005, Mike Kercher wrote: > > > Ken Godee wrote: > > >> I have a similar problem. yum is almost always stalling whether it''s > > >> a clean install (just did two clean installs of 3.4 on Friday) or an > > >> existing box (have eight 3.3 boxes that have been running for about > > >> 2 months now). > > >> > > >> However, if I hit ctrl-c, it just kills the process, it doesn''t > > >> continue it, so I was surprised to read your comments above. > > >> > > >> I end up always doing one of two things (or a combination of them): > > >> > > >> a) since I figured it was related to which mirror it might be hitting > > >> (never investigated, just assumed), I always just ctrl-c to end the > > >> process and then run yum again, thinking I might get a faster/closer > > >> mirror -- repeat this until it seems to be going at a decent pace > > >> > > >> b) alternatively, or after doing (a) a few times, I just walk away > > >> from it, and eventually (sometimes half an hour or more), it *will* > > >> complete, stalling all along the way at various points > > >> > > > > > > Ditto.... > > > > > > Seems to have just started when I did an update this last weekend. > > > Took about 1/2 hour just to download header info, previous to last > > > weekend never had this problem. > > > > > > > Thank god...I''m not crazy!!! :) > > > > Mike > > > > _______________________________________________ > > CentOS mailing list > > CentOS@caosity.org > > http://lists.caosity.org/mailman/listinfo/centos > > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >-- uklinux.net - The ISP of choice for the discerning Linux user.
seth vidal wrote:>>>Seems to have just started when I did an update this >>>last weekend. Took about 1/2 hour just to download >>>header info, previous to last weekend never had this problem. >> >>I''ve always had the problem, I''ve almost come to just accept it as a yum >>thing. It happened to me all the time on FC2, too. >> >>Though it is true that this past weekend seems to have been particularly >>bad. > > > It''s not ''just a yum thing''. There are lots and lots of users of yum out > there w/o any problem like this. I know, I''ve heard from them. > > However, the problem of stalling on downloads is most often related to > transparent proxies.I don''t deny there are probably lots of folks without the problem (though I don''t actually know). It may be related to transparent proxies, but there must be other causes too. Because I''ve done the yum thing on very diverse networks (UCLA, UCLA Medical, CalPOP, Verizon DSL, Adelphia Cable, etc.) and I''ve seen the behavior on all of them, and I''d be surprised if they were *all* using transparent proxies -- though *some* probably are. Not really offering a solution or any definitive statements, just sharing my experience (as I believe Matt Bottrell had asked folks to do). johnn
It would appear the one I have trouble talking to is 69.67.240.122. Seems I can get to all the other ip''s that make up mirror.centos.org. Jamie On Mon, 28 Feb 2005, Lance Davis wrote:> On Mon, 28 Feb 2005, Jamie McKnight wrote: > > > > > I did an install of CentOS 2.1 this past weekend and ran into the > > same thing. While strace''ing the yum process I noticed it was hanging > > trying to talk to the same ip address each time. After it would timeout > > it would download a few more until it hit trying to talk to that same ip > > address again. > > > > nslookup of server configured in yum.conf returned several ip''s, > > one of which was not responding. My fix was to set it specifically to one > > of the ip addresses. Sorry I don''t have the specifics of which server it > > was that wasn''t responding, but I don''t have access to that box at the > > moment. > > sounds like one of the mirror servers may be having problems. > > I also saw the issue last night updating a server and put it down to > excess traffic caused by C4 syncing. > > If you can let us know which ip then I can investigate - otherwise will > try to deduce later. > > Lance > > > > > Jamie > > > > On Mon, 28 Feb 2005, Mike Kercher wrote: > > > > > Ken Godee wrote: > > > >> I have a similar problem. yum is almost always stalling whether it''s > > > >> a clean install (just did two clean installs of 3.4 on Friday) or an > > > >> existing box (have eight 3.3 boxes that have been running for about > > > >> 2 months now). > > > >> > > > >> However, if I hit ctrl-c, it just kills the process, it doesn''t > > > >> continue it, so I was surprised to read your comments above. > > > >> > > > >> I end up always doing one of two things (or a combination of them): > > > >> > > > >> a) since I figured it was related to which mirror it might be hitting > > > >> (never investigated, just assumed), I always just ctrl-c to end the > > > >> process and then run yum again, thinking I might get a faster/closer > > > >> mirror -- repeat this until it seems to be going at a decent pace > > > >> > > > >> b) alternatively, or after doing (a) a few times, I just walk away > > > >> from it, and eventually (sometimes half an hour or more), it *will* > > > >> complete, stalling all along the way at various points > > > >> > > > > > > > > Ditto.... > > > > > > > > Seems to have just started when I did an update this last weekend. > > > > Took about 1/2 hour just to download header info, previous to last > > > > weekend never had this problem. > > > > > > > > > > Thank god...I''m not crazy!!! :) > > > > > > Mike > > > > > > _______________________________________________ > > > CentOS mailing list > > > CentOS@caosity.org > > > http://lists.caosity.org/mailman/listinfo/centos > > > > > _______________________________________________ > > CentOS mailing list > > CentOS@caosity.org > > http://lists.caosity.org/mailman/listinfo/centos > > > > -- > uklinux.net - > The ISP of choice for the discerning Linux user. > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
doesn''t respond for me either... ping/trace stops, no ping replies, etc. On Mon, 28 Feb 2005, Jamie McKnight wrote:> > It would appear the one I have trouble talking to is > 69.67.240.122. > > Seems I can get to all the other ip''s that make up > mirror.centos.org. > > Jamie > > > > On Mon, 28 Feb 2005, Lance Davis wrote: > > > On Mon, 28 Feb 2005, Jamie McKnight wrote: > > > > > > > > I did an install of CentOS 2.1 this past weekend and ran into the > > > same thing. While strace''ing the yum process I noticed it was hanging > > > trying to talk to the same ip address each time. After it would timeout > > > it would download a few more until it hit trying to talk to that same ip > > > address again. > > > > > > nslookup of server configured in yum.conf returned several ip''s, > > > one of which was not responding. My fix was to set it specifically to one > > > of the ip addresses. Sorry I don''t have the specifics of which server it > > > was that wasn''t responding, but I don''t have access to that box at the > > > moment. > > > > sounds like one of the mirror servers may be having problems. > > > > I also saw the issue last night updating a server and put it down to > > excess traffic caused by C4 syncing. > > > > If you can let us know which ip then I can investigate - otherwise will > > try to deduce later. > > > > Lance > > > > > > > > Jamie > > > > > > On Mon, 28 Feb 2005, Mike Kercher wrote: > > > > > > > Ken Godee wrote: > > > > >> I have a similar problem. yum is almost always stalling whether it''s > > > > >> a clean install (just did two clean installs of 3.4 on Friday) or an > > > > >> existing box (have eight 3.3 boxes that have been running for about > > > > >> 2 months now). > > > > >> > > > > >> However, if I hit ctrl-c, it just kills the process, it doesn''t > > > > >> continue it, so I was surprised to read your comments above. > > > > >> > > > > >> I end up always doing one of two things (or a combination of them): > > > > >> > > > > >> a) since I figured it was related to which mirror it might be hitting > > > > >> (never investigated, just assumed), I always just ctrl-c to end the > > > > >> process and then run yum again, thinking I might get a faster/closer > > > > >> mirror -- repeat this until it seems to be going at a decent pace > > > > >> > > > > >> b) alternatively, or after doing (a) a few times, I just walk away > > > > >> from it, and eventually (sometimes half an hour or more), it *will* > > > > >> complete, stalling all along the way at various points > > > > >> > > > > > > > > > > Ditto.... > > > > > > > > > > Seems to have just started when I did an update this last weekend. > > > > > Took about 1/2 hour just to download header info, previous to last > > > > > weekend never had this problem. > > > > > > > > > > > > > Thank god...I''m not crazy!!! :) > > > > > > > > Mike > > > > > > > > _______________________________________________ > > > > CentOS mailing list > > > > CentOS@caosity.org > > > > http://lists.caosity.org/mailman/listinfo/centos > > > > > > > _______________________________________________ > > > CentOS mailing list > > > CentOS@caosity.org > > > http://lists.caosity.org/mailman/listinfo/centos > > > > > > > -- > > uklinux.net - > > The ISP of choice for the discerning Linux user. > > > > _______________________________________________ > > CentOS mailing list > > CentOS@caosity.org > > http://lists.caosity.org/mailman/listinfo/centos > > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >
On Mon, 28 Feb 2005, Jamie McKnight wrote:> > It would appear the one I have trouble talking to is > 69.67.240.122. > > Seems I can get to all the other ip''s that make up > mirror.centos.org.Thanks - that fixes it - should be 69.56.240.122 :( Regards Lance> > Jamie > > > > On Mon, 28 Feb 2005, Lance Davis wrote: > > > On Mon, 28 Feb 2005, Jamie McKnight wrote: > > > > > > > > I did an install of CentOS 2.1 this past weekend and ran into the > > > same thing. While strace''ing the yum process I noticed it was hanging > > > trying to talk to the same ip address each time. After it would timeout > > > it would download a few more until it hit trying to talk to that same ip > > > address again. > > > > > > nslookup of server configured in yum.conf returned several ip''s, > > > one of which was not responding. My fix was to set it specifically to one > > > of the ip addresses. Sorry I don''t have the specifics of which server it > > > was that wasn''t responding, but I don''t have access to that box at the > > > moment. > > > > sounds like one of the mirror servers may be having problems. > > > > I also saw the issue last night updating a server and put it down to > > excess traffic caused by C4 syncing. > > > > If you can let us know which ip then I can investigate - otherwise will > > try to deduce later. > > > > Lance > > > > > > > > Jamie > > > > > > On Mon, 28 Feb 2005, Mike Kercher wrote: > > > > > > > Ken Godee wrote: > > > > >> I have a similar problem. yum is almost always stalling whether it''s > > > > >> a clean install (just did two clean installs of 3.4 on Friday) or an > > > > >> existing box (have eight 3.3 boxes that have been running for about > > > > >> 2 months now). > > > > >> > > > > >> However, if I hit ctrl-c, it just kills the process, it doesn''t > > > > >> continue it, so I was surprised to read your comments above. > > > > >> > > > > >> I end up always doing one of two things (or a combination of them): > > > > >> > > > > >> a) since I figured it was related to which mirror it might be hitting > > > > >> (never investigated, just assumed), I always just ctrl-c to end the > > > > >> process and then run yum again, thinking I might get a faster/closer > > > > >> mirror -- repeat this until it seems to be going at a decent pace > > > > >> > > > > >> b) alternatively, or after doing (a) a few times, I just walk away > > > > >> from it, and eventually (sometimes half an hour or more), it *will* > > > > >> complete, stalling all along the way at various points > > > > >> > > > > > > > > > > Ditto.... > > > > > > > > > > Seems to have just started when I did an update this last weekend. > > > > > Took about 1/2 hour just to download header info, previous to last > > > > > weekend never had this problem. > > > > > > > > > > > > > Thank god...I''m not crazy!!! :) > > > > > > > > Mike > > > > > > > > _______________________________________________ > > > > CentOS mailing list > > > > CentOS@caosity.org > > > > http://lists.caosity.org/mailman/listinfo/centos > > > > > > > _______________________________________________ > > > CentOS mailing list > > > CentOS@caosity.org > > > http://lists.caosity.org/mailman/listinfo/centos > > > > > > > -- > > uklinux.net - > > The ISP of choice for the discerning Linux user. > > > > _______________________________________________ > > CentOS mailing list > > CentOS@caosity.org > > http://lists.caosity.org/mailman/listinfo/centos > > > _______________________________________________ > CentOS mailing list > CentOS@caosity.org > http://lists.caosity.org/mailman/listinfo/centos >-- uklinux.net - The ISP of choice for the discerning Linux user.