That didn't worked for me, i removed all roster and pep lines in sm.xml config
file but i've the same error.
- Mail original -
De: "Sander Grendelman" .
À: spacewalk-list@redhat.com
Envoyé: Lundi 28 Février 2011 13:11:59
Objet: Re: [Spacewalk-list] osa-dispatcher and
On Mon, Feb 28, 2011 at 01:05:27PM +0100, Sander Grendelman wrote:
> service osa-dispatcher stop
> service jabberd stop
> ### remove all "roster" lines from /etc/jabberd/sm.xml> ###
> service jabberd start
> ### Check if sm is running
> service osa-dispatcher start
Oh, and don't forget to remove t
On Mon, Feb 28, 2011 at 11:14:04AM +0100, Baptiste AGASSE wrote:
> I've applied the patch attached at
> https://bugzilla.redhat.com/show_bug.cgi?id=662593, but now, sm don't start
> (sm dead but subsys locked)
I had the same problem ( I'm guessing that you applied the patch to
sm.xml ?).
What w
28 spacewalk jabberd/s2s[12619]: ready for connections
any suggestion ?
Regards.
- Mail original -
De: "Greg Wojtak"
À: spacewalk-list@redhat.com
Envoyé: Vendredi 25 Février 2011 15:56:50
Objet: Re: [Spacewalk-list] osa-dispatcher and osad
In my case, I also had to re-regi
In my case, I also had to re-register my osad clients and upgrade
yum-rhn-plugin on the clients to what's in the 1.3 repo.
On 2011-02-25 6:48 AM, "Sander Grendelman" wrote:
>On Fri, Feb 25, 2011 at 11:55:26AM +0100, Baptiste AGASSE wrote:
>>
>> after that, all the log file are touched and if i
On Fri, Feb 25, 2011 at 11:55:26AM +0100, Baptiste AGASSE wrote:
>
> after that, all the log file are touched and if i add an action to this
> client (remote script execution) this action is only picked up when
> rhnsd on the client execute rhn_check.
>
Hi Baptiste,
You're probably hitting a (k
Hi all,
I have a little problem with osa-dispatcher and osad
I have a spacewalk server in test env with 18 servers configured as
client on it.
This spacewalk server was installed with spacewalk 1.2 and updated in 1.3
I started to play with osad few days ago with one client but it seems
not work.
