Will McDonald wrote:
On 31/08/06, Julio E. Gonzalez P. jegp@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?
On 31/08/06, Bowie Bailey Bowie_Bailey@buc.com wrote:
Will McDonald wrote:
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?
Not that I could find unfortunaltey. I've just done...
[root@willspc ~]# for package in `rpm -qa --qf "%{NAME}.%{arch}\n" | sort | uniq -d | grep -v kernel`; do rpm -q $package; done
Which lists all base duplicated packages (though at least kernel and gpg-pubkey are this way by design I believe). Then manually removed the older packages. You could THORETICALLY do...
# for duppackage in `rpm -qa --qf "%{NAME}.%{arch}\n" | sort | uniq -d | grep -Ev '(kernel)|(gpg-pubkey)'`; do for olderpackage in `rpm -q $duppackage | head -1` do rpm -e $olderpackage; done done
WARNING: ^^^^ That's entirely untested and reliant on the ordering from rpm output, which looks consistent but I couldn't *swear* to it. So be careful! :)
Will.
On Thu, 2006-08-31 at 16:43 +0100, Will McDonald wrote:
On 31/08/06, Bowie Bailey Bowie_Bailey@buc.com wrote:
Will McDonald wrote:
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?
Not that I could find unfortunaltey. I've just done...
[root@willspc ~]# for package in `rpm -qa --qf "%{NAME}.%{arch}\n" | sort | uniq -d | grep -v kernel`; do rpm -q $package; done
Which lists all base duplicated packages (though at least kernel and gpg-pubkey are this way by design I believe). Then manually removed the older packages. You could THORETICALLY do...
# for duppackage in `rpm -qa --qf "%{NAME}.%{arch}\n" | sort | uniq -d | grep -Ev '(kernel)|(gpg-pubkey)'`; do for olderpackage in `rpm -q $duppackage | head -1` do rpm -e $olderpackage; done done
WARNING: ^^^^ That's entirely untested and reliant on the ordering from rpm output, which looks consistent but I couldn't *swear* to it. So be careful! :)
Will. _______________________________________________
personally, I would remove the new package and re-update in case something in cleanup is required for proper operations.
what does everyone think.
Not trying to jinx myself, but I have never had this problem using centos on hundreds of servers.
Thanks, Johnny Hughes
Johnny Hughes wrote:
On Thu, 2006-08-31 at 16:43 +0100, Will McDonald wrote:
On 31/08/06, Bowie Bailey Bowie_Bailey@buc.com wrote:
Will McDonald wrote:
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?
Not that I could find unfortunaltey. I've just done...
[root@willspc ~]# for package in `rpm -qa --qf "%{NAME}.%{arch}\n" | sort | uniq -d | grep -v kernel`; do rpm -q $package; done
Which lists all base duplicated packages (though at least kernel and gpg-pubkey are this way by design I believe). Then manually removed the older packages. You could THORETICALLY do...
# for duppackage in `rpm -qa --qf "%{NAME}.%{arch}\n" | sort | uniq -d | grep -Ev '(kernel)|(gpg-pubkey)'`; do for olderpackage in `rpm -q $duppackage | head -1` do rpm -e $olderpackage; done done
WARNING: ^^^^ That's entirely untested and reliant on the ordering from rpm output, which looks consistent but I couldn't *swear* to it. So be careful! :)
Will. _______________________________________________
personally, I would remove the new package and re-update in case something in cleanup is required for proper operations.
what does everyone think.
Not trying to jinx myself, but I have never had this problem using centos on hundreds of servers.
I've never had this type of problem either, but paranoia is setting in since I've got a couple of key machines that happen to be in difficult to reach locations if something should wedge the machine. To date, I've just thrown caution to the wind and remotely updated everything since I've always had a remote helper at the various datacenters to pick up the pieces if anything blew up (which has never happened to date).
Cheers,
chrism@imntv.com wrote:
I've never had this type of problem either, but paranoia is setting in since I've got a couple of key machines that happen to be in difficult to reach locations if something should wedge the machine. To date, I've just thrown caution to the wind and remotely updated everything since I've always had a remote helper at the various datacenters to pick up the pieces if anything blew up (which has never happened to date).
Same here, I've never had this issue before. All my machines are local to me though, so if something gets botched, I have physical access so I'm better off than say you.
Max
On 31/08/06, Johnny Hughes mailing-lists@hughesjr.com wrote:
personally, I would remove the new package and re-update in case something in cleanup is required for proper operations.
what does everyone think.
That's a fair point, I was going to rpm verify the whole system once this is all settled.
Johnny Hughes wrote:
personally, I would remove the new package and re-update in case something in cleanup is required for proper operations.
what does everyone think.
Not trying to jinx myself, but I have never had this problem using centos on hundreds of servers.
I don't know either. Again, I've never had this happen so this is all new to me. Apparently removing the doubles manually in the past hasn't caused anyone that has mentioned doing it this way, any trouble. If my approach doesn't work and screws my lappy up...oh well, I need to re-partition my system anyways. :)
This time around, I was going to take that approach and see what happens. For the future though, I might start doing what everyone is saying and get a list and then run them manually.
Anyone else have an opinion? I'm thinking removing the duplicates by hand is the best, since you know you won't hose any config files...or perhaps I'm wrong.
Max
Bowie Bailey wrote:
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/49That website is no longer working. Is there still a copy of this script floating around?
I ran that script as well just a few minutes ago and it got rid of all my dups. Everything seems to be good now, but I'll have to keep this all in mind for the next time around.
The script is just this in case you still can't get to it:
for file in `rpm -qa --queryformat="%{NAME} %{ARCH}\n" | sort | uniq -c | grep -v " 1 " | cut -c 9- | cut -d" " -f1`; do rpm -q --last $file | tail -1 | cut -d" " -f1; done | grep -v gpg-pubkey | xargs rpm -e --justdb --nodeps 2> /tmp/dupes
Max
-
Bowie Bailey -
chrism＠imntv.com -
Johnny Hughes -
Max H. -
Will McDonald