Greetings,
I just ran "yum update" on a remote 4.2 Centos install. Then I typed "yum search some package" and got this error message repeating continuously:
sem_post: Invalid argument
A search for this message revealed only these links:
http://www.linode.com/forums/archive/o_t/t_1898/centos4_installations_rpm_da...
http://bugs.centos.org/view.php?id=1202
If I run the command to look for duplicated RPMs described in those pages I get:
-bash-3.00# rpm -qa | sed 's/([A-Za-z0-9])-[0-9].*$/\1/' | sort | uniq -d kernel
As a matter of fact, I also get:
-bash-3.00# rpm -q kernel kernel-2.6.9-11.EL kernel-2.6.9-22.0.1.EL kernel-2.6.9-34.EL
My question is, what is the best, safest way to fix the system?
The hack described in those pages doesn't seem (to me) to apply directly to my case. Being the kernel involved, instead of normal packages, I'm hesitant to try something that, as far as I know, may bring this remote server in an unusable state.
Any help is appreciated.
Marco
M. Fioretti wrote:
As a matter of fact, I also get:
-bash-3.00# rpm -q kernel kernel-2.6.9-11.EL kernel-2.6.9-22.0.1.EL kernel-2.6.9-34.EL
there is nothing wrong with this - kernels are added / installed rather than upgraded - since lots of people have custom kernel modules and other kernel specific stuff.
On Wed, May 24, 2006 01:54:12 AM +0100, Karanbir Singh (mail-lists@karan.org) wrote:
As a matter of fact, I also get:
-bash-3.00# rpm -q kernel kernel-2.6.9-11.EL kernel-2.6.9-22.0.1.EL kernel-2.6.9-34.EL
there is nothing wrong with this - kernels are added / installed
So can I remove the first 2, or all 3 versions must remain?
TIA, Marco
On Wed, 2006-05-24 at 07:01 +0200, M. Fioretti wrote:
On Wed, May 24, 2006 01:54:12 AM +0100, Karanbir Singh (mail-lists@karan.org) wrote:
As a matter of fact, I also get:
-bash-3.00# rpm -q kernel kernel-2.6.9-11.EL kernel-2.6.9-22.0.1.EL kernel-2.6.9-34.EL
there is nothing wrong with this - kernels are added / installed
So can I remove the first 2, or all 3 versions must remain?
you can remove any kernels that you don't boot from ... the reason it doesn't automatically remove them is so you can reboot with the old kernel if the new one is broken on your install. This is the default yum behavior.
the only time I have ever seen the problem you describe is when an upgrade from CentOS-3 to CentOS-4 is done (which we highly discourage).
It would stand to reason that other upgrades of python could also cause the error.
You should reboot your machine ...
But ... you have no duplicate packages that are an issue.
Does rebooting solve your problem?
On Wed, May 24, 2006 05:27:13 AM -0500, Johnny Hughes (mailing-lists@hughesjr.com) wrote:
On Wed, 2006-05-24 at 07:01 +0200, M. Fioretti wrote:
On Wed, May 24, 2006 01:54:12 AM +0100, Karanbir Singh
there is nothing wrong with this - kernels are added / installed
So can I remove the first 2, or all 3 versions must remain?
you can remove any kernels that you don't boot from ...
[...]
Does rebooting solve your problem?
Yes, it seems so. Thanks, everybody,
Marco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, May 26, 2006 at 05:46:03PM +0200, M. Fioretti wrote:
On Wed, May 24, 2006 05:27:13 AM -0500, Johnny Hughes (mailing-lists@hughesjr.com) wrote:
On Wed, 2006-05-24 at 07:01 +0200, M. Fioretti wrote:
On Wed, May 24, 2006 01:54:12 AM +0100, Karanbir Singh
there is nothing wrong with this - kernels are added / installed
So can I remove the first 2, or all 3 versions must remain?
you can remove any kernels that you don't boot from ...
[...]
Does rebooting solve your problem?
Yes, it seems so. Thanks, everybody,
I have noticed, in one of my machines, the rpmq daily cronjob hanging indefinitively. That will cause headaches and lockups on yum.
Killing the stray rpmq process solves the problem.
- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-
Johnny Hughes -
Karanbir Singh -
M. Fioretti -
Rodrigo Barbosa