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)
there is no logs in /var/log/message from sm when start jabberd : Feb 28 11:01:28 spacewalk jabberd/router[12531]: starting up Feb 28 11:01:28 spacewalk jabberd/router[12531]: process id is 12531, written to /var/lib/jabberd/pid/router.pid Feb 28 11:01:28 spacewalk jabberd/router[12531]: loaded user table (1 users) Feb 28 11:01:28 spacewalk jabberd/router[12531]: loaded filters (0 rules) Feb 28 11:01:28 spacewalk jabberd/router[12531]: [0.0.0.0, port=5347] listening for incoming connections Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: starting up Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: process id is 12589, written to /var/lib/jabberd/pid/c2s.pid Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: modules search path: /usr/lib64/jabberd Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: loading 'db' authreg module Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: initialized auth module 'db' Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: [spacewalk.lyra-network.com] configured; realm=, registration enabled Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: attempting connection to router at 127.0.0.1, port=5347 Feb 28 11:01:28 spacewalk jabberd/router[12531]: [127.0.0.1, port=35642] connect Feb 28 11:01:28 spacewalk jabberd/router[12531]: [127.0.0.1, port=35642] authenticated as jabberd@jabberd-router Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: connection to router established Feb 28 11:01:28 spacewalk jabberd/router[12531]: [c2s] online (bound to 127.0.0.1, port 35642) Feb 28 11:01:28 spacewalk jabberd/s2s[12619]: starting up (interval=3, queue=60, keepalive=0, idle=86400) Feb 28 11:01:28 spacewalk jabberd/s2s[12619]: process id is 12619, written to /var/lib/jabberd/pid/s2s.pid Feb 28 11:01:28 spacewalk jabberd/s2s[12619]: attempting connection to router at 127.0.0.1, port=5347 Feb 28 11:01:28 spacewalk jabberd/router[12531]: [127.0.0.1, port=35644] connect Feb 28 11:01:28 spacewalk jabberd/router[12531]: [127.0.0.1, port=35644] authenticated as jabberd@jabberd-router Feb 28 11:01:28 spacewalk jabberd/s2s[12619]: connection to router established Feb 28 11:01:28 spacewalk jabberd/router[12531]: [s2s] set as default route Feb 28 11:01:28 spacewalk jabberd/router[12531]: [s2s] online (bound to 127.0.0.1, port 35644) Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: [0.0.0.0, port=5222] listening for connections Feb 28 11:01:28 spacewalk jabberd/c2s[12589]: ready for connections Feb 28 11:01:28 spacewalk jabberd/s2s[12619]: [0.0.0.0, port=5269] listening for connections Feb 28 11:01:28 spacewalk jabberd/s2s[12619]: ready for connections any suggestion ? Regards. ----- Mail original ----- De: "Greg Wojtak" <[email protected]> À: [email protected] 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-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" <[email protected]> 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 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 (known) bug with osa-dispatcher and jabberd. >Please take a look at https://bugzilla.redhat.com/show_bug.cgi?id=662593 > >Commenting out the "roster" parts in sm.xml fixed the issue for me. > >With kind regards, > >Sander Grendelman. > >_______________________________________________ >Spacewalk-list mailing list >[email protected] >https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
