Hi Patrick,
That does the trick!
Thanks.
The strange thing is that when I want to upgrade to the CentOS 5.4 repo
it complains about a missing GPG key (which I found strange because the
client already got the PGP key when I installed Centos right?)
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 7203f491
Public key for yum-3.2.22-20.el5.centos.noarch.rpm is not installed
Kind regards,
Michiel
Flaherty, Patrick wrote:
Yep, I wget'd the files from the redhat spacewalk repo, scp'd them in a
directory on a few client machines and ran "rpm -Uvh ./*.rpm" from that
directory.
I have not been brave enough to add them to my spacewalk channels and
have been doing the process manually on machines I've needed to patch.
Patrick
-----Original Message-----
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Michiel van Es
Sent: Saturday, October 31, 2009 7:56 AM
To: spacewalk-list@redhat.com
Subject: RE: CentOS 5.3 to CentOS 5.4 upgrade and
yum_rhn_plugin ==>WAS:Re:[Spacewalk-list] osa-dispatcher not
running or not connecting
Hi Patrick,
That is ok mate ;)
But how did you do the upgrade on your centos 5.3 clients?
Did you do an rpm -UVH from these packages?
I really hope that stahma will update it's packages so an yum
update would supply the new yum version :)
Kind regards,
Michiel
________________________________________
From: spacewalk-list-boun...@redhat.com
[spacewalk-list-boun...@redhat.com] On Behalf Of Flaherty,
Patrick [pflahe...@wsi.com]
Sent: Friday, October 30, 2009 7:51 PM
To: spacewalk-list@redhat.com
Subject: RE: CentOS 5.3 to CentOS 5.4 upgrade and
yum_rhn_plugin ==> WAS:Re:[Spacewalk-list] osa-dispatcher
not running or not connecting
Hey Michel,
I re-read my original message, I probably should have been
less curt (sorry!). The work around seems to be use the
packages out the .6 repo (
http://article.gmane.org/gmane.linux.redhat.spacewalk.user/300
9 ). It also appears that the "offical" repos will be updated
when the packages are ported.
The packages I needed were:
rhn-check-0.6.4-1.el5.noarch.rpm
rhnlib-2.5.13-1.el5.noarch.rpm
yum-rhn-plugin-0.6.2-1.el5.noarch.rpm
rhn-client-tools-0.6.4-1.el5.noarch.rpm
rhn-setup-0.6.4-1.el5.noarch.rpm
Patrick
-----Original Message-----
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of
Michiel van Es
Sent: Friday, October 30, 2009 11:28 AM
To: spacewalk-list@redhat.com
Subject: Re: CentOS 5.3 to CentOS 5.4 upgrade and
yum_rhn_plugin ==>
WAS:Re:[Spacewalk-list] osa-dispatcher not running or not connecting
Hi PAtrick,
yes I know, that is my own thread but there is not a
solution for all
my CentOS 5.3 machines wanting to upgrade to CentOS
5.4 and how I can upgrade my yum_rhn_plugin packages...
Or am I missing a post?
Michiel
Flaherty, Patrick wrote:
Please see the thread "[Spacewalk-list] CentOS 5.4 64 bit and
spacewalk client tools", where this has been discussed for a fix.
http://article.gmane.org/gmane.linux.redhat.spacewalk.user/2988
Patrick
-----Original Message-----
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of
Michiel van
Es
Sent: Friday, October 30, 2009 10:36 AM
To: Joshua Roys
Cc: spacewalk-list@redhat.com
Subject: CentOS 5.3 to CentOS 5.4 upgrade and
yum_rhn_plugin ==> WAS:
Re:[Spacewalk-list] osa-dispatcher not running or not connecting
Yes :)
The next problem I got is to install the correct yum_rhn_plugin
working with CentOS 5.4 ;) The problem is that a lot of CentoS 5
machines are now upgrading to CenOS 5.4 with a new yum
version not
compatible with the yum_rhn_plugin installed by wget -q
http://stahnma.fedorapeople.org/spacewalk-tools/spacewalk-clie
nt-tools-0.0-1.noarch.rpm
The question is now: how can I upgrae my centos 5.3 to
5.4 without
the dependency problems (yum_rhn_plugin being to old?)
Kind regards,
Michiel
Joshua Roys wrote:
On 10/30/2009 10:11 AM, Michiel van Es wrote:
FIXED IT!
changed the max open files from 1024 to 2024 in the .xml
files and
moved /var/lib/jabberd/db to
/var/lib/jabberd/old-jammer&& mkdir
/var/lib/jabberd/db&& chown jabber:jabber
/var/lib/jabberd/db&&
chmod
777 /var/lib/jabberd/db
and restarted jabberd and now I see all connection
established :)
Works like a charm! :D
Michiel van Es wrote:
Nice! Glad you finally got it.
Josh
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list