CentOS 4.3 (SMP, x86_64, Athlon64 X2) with all pre-4.4 release updates applied. Since I ran into the Yum issue at the previous upgrade, I first did yum upgrade to get the list of packages (6 to install, 206 to update). I then did yum upgrade yum (which passed without issues) yum upgrade sqlite (which passed without isseus). Fairly certain that yum now works correctly, I wanted to just do another small upgrade before doing the rest, and did yum upgrade samba [root at naboens ~]# yum upgrade samba Setting up Upgrade Process Setting up repositories Reading repository metadata in from local files <no progress> This seemed to hang, and a look at top showed yum consuming more and more memory, the system starting to swap and bog down and then become unresponsive (all swap exhausted, I was not quick enough to kill yum). I was able to reproduce this on a different machine (also x86_64, SMP and Athlon64 X2), so it seems to be an actual problem. As I can play around a bit more on this machine, I tried doing a yum upgrade (without specifying samba) and it behaves the same (ie yum consuming increasing amounts of memory while "Reading repository metadata (etc)". Has anyone else experienced and been able to resolve this? -S -- Simen Thoresen, Dolphin ICS Systems Administration and Wulfkit Support
Simen Thoresen wrote:> CentOS 4.3 (SMP, x86_64, Athlon64 X2) with all pre-4.4 release updates > applied. > > Since I ran into the Yum issue at the previous upgrade, I first did > yum upgrade to get the list of packages (6 to install, 206 to update). > I then did > yum upgrade yum (which passed without issues) > yum upgrade sqlite (which passed without isseus). >yum clean metadata; yum list updates -- Karanbir Singh : http://www.karan.org/ : 2522219 at icq
I have the same problem here... Anyone has something to say about this? Thanks. Julio. Simen Thoresen wrote:> CentOS 4.3 (SMP, x86_64, Athlon64 X2) with all pre-4.4 release updates > applied. > > Since I ran into the Yum issue at the previous upgrade, I first did > yum upgrade to get the list of packages (6 to install, 206 to update). > I then did > yum upgrade yum (which passed without issues) > yum upgrade sqlite (which passed without isseus). > > Fairly certain that yum now works correctly, I wanted to just do > another small upgrade before doing the rest, and did > yum upgrade samba > > [root at naboens ~]# yum upgrade samba > Setting up Upgrade Process > Setting up repositories > Reading repository metadata in from local files > <no progress> > > This seemed to hang, and a look at top showed yum consuming more and > more memory, the system starting to swap and bog down and then become > unresponsive (all swap exhausted, I was not quick enough to kill yum). > > I was able to reproduce this on a different machine (also x86_64, SMP > and Athlon64 X2), so it seems to be an actual problem. As I can play > around a bit more on this machine, I tried doing a yum upgrade > (without specifying samba) and it behaves the same (ie yum consuming > increasing amounts of memory while "Reading repository metadata (etc)". > > Has anyone else experienced and been able to resolve this? > > -S
Will McDonald wrote:> On 31/08/06, Julio E. Gonzalez P. <jegp at netvision.com.py> wrote: > > I have the same problem here... > > Anyone has something to say about this? > > Thanks. > > Julio. > > Try strace-ing the process ID of the yum process to see if it's stuck > at the "futex" call/stage. I tried blithely "yum update"-ing my test > system earlier and it hung on this. > > http://www.google.co.uk/search?hl=en&q=strace+futex&meta> > Now the system's in a little bit of a state consistency-wise. > Fortunately, we've covered this ground before. :) > > *cuts* > *pastes* > > Check the list archives for : > > "futex.. How to remove lots of duplicate packages" > > http://lists.centos.org/pipermail/centos/2006-March/thread.html#62319 > > "yum update killed on cleanup stage - anything to worry about?" > > http://lists.centos.org/pipermail/centos/2006-March/thread.html#62568>From your second link:Yes, I did get lots of duplicate packages but I've already fixed that. Basically, what I did was to run Adam Stoke's script to remove duplcate packages. It can be located at http://astokes.org/?q=node/49 That website is no longer working. Is there still a copy of this script floating around? -- Bowie