Something definitely went wrong in install. Looks like jabber didn't get configured. I saw something similar previously in my proxy install which I reported and got fixed. You aren't far off getting it configured so a reinstall is pretty pointless. You need to enable auto registration in jabber. Osa will then register itself if not already in the sigh fb. <blockquote type="cite">On Apr 29, 2010 7:05 PM, "DEMARQUAY, Mathieu" <<a href="mailto:mathieu.demarquay@capgemini.com">mathieu.demarquay@capgemini.com</a>> wrote: <div lang="FR" link="blue" vlink="purple"> <div> Hi, I installed spacewalk 0.8 on a RHEL 5.3 x86_64 and spacewalk is working fine except for jabber and osa-dispatcher. At the beginning, jabberd was not starting at all; it resulted in a connection failure for osa-dispatcher. After some investigation, I corrected two problems: - c2s.xml was not readable for the jabber user, so i did a : « chmod 644 /etc/jabberd/* » - /var/jabberd/db was not created, so I did : o mkdir -p /var/jabberd/db o chown jabberd:jabberd /var/jabberd/db At this point, jabber started but osa-dispatcher was not able to establish a secure connection: # date ; /usr/sbin/rhn-satellite start jeu avr 29 16:36:02 CEST 2010 Starting rhn-satellite... Starting Jabber services [ OK ] Starting Oracle Net Listener. Starting Oracle Database 10g Express Edition Instance. Starting osa-dispatcher: RHN 22852 2010/04/29 16:36:09 +02:00: ('Server does not support TLS - <starttls /> not in <features /> stanza',) RHN 22852 2010/04/29 16:36:09 +02:00: ('Traceback (most recent call last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 254, in setup_co nnection\n c = self._get_jabber_client(js)\n File "/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client\n c.connect()\n File "/usr/share/rhn/osad/jabber_lib.py", line 601, in connect\n raise SSLDisabledError\nSSLDisabledError\n',) [ OK ] Starting tomcat5: [ OK ] Démarrage de httpd : [ OK ] Starting Monitoring ... [ OK ] Starting MonitoringScout ... [ OK ] Starting rhn-search... Starting cobbler daemon: [ OK ] Starting RHN Taskomatic... SERVING! Done. I found that the line “<pemfile>/etc/jabberd/server.pem</pemfile>” in c2s.xml was commented. I corrected this and copied the certificate from /etc/pki/spacewalk/jabberd/server.pem in /etc/jabberd/. Now osa-dispatcher starts fine, but I obtain following errors in syslogs: Apr 29 17:50:59 mvdiff2 jabberd/c2s[13603]: [12] auth succeeded: username=rhn-dispatcher-sat, resource=superclient Apr 29 17:50:59 mvdiff2 jabberd/c2s[13603]: [12] requesting session: jid=<a href="http://rhn-dispatcher-sat@my.fqdn.obfuscated.org/superclient" target="_blank">rhn-dispatcher-sat@my.fqdn.obfuscated.org/superclient</a> Apr 29 17:50:59 mvdiff2 jabberd/sm[13601]: user not found, can't start session: jid=<a href="http://rhn-dispatcher-sat@my.fqdn.obfuscated.org/superclient" target="_blank">rhn-dispatcher-sat@my.fqdn.obfuscated.org/superclient</a> I suppose that I missed something in the setup process, those errors are too big for not having been corrected: but I did not found any documentation about that. Do you have any idea how to correct this “user not found” problem? Did I forget something in the configuration process that could have avoided theses problems? Best, Mathieu <div> </div> </div> <pre></pre>This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. <pre> </pre></div> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </blockquote>