On 25 May 2010 14:23, DEMARQUAY, Mathieu <[email protected]> wrote: > I reinstalled from scratch spacewalk 1.0 on a new RHEL 5.3 machine and I am > facing the same problem as before with jabber. This time I watched log files > but nothing seems to go wrong during the spacewalk install: > > > > - /var/log/rhn/rhn-installation.log is ok (except that > osa-dispatcher doesn’t start properly) > > - If I execute manually « /usr/bin/spacewalk-setup-jabberd --macros > hostname:swmgt_vip.exp.localdomain », it works fine. > > - If I re-execute /usr/bin/spacewalk-setup, same result. > > > > Like the last previous installation I had to do: > > chmod 644 /etc/jabberd/* > > mkdir -p /var/jabberd/db > > chown jabberd:jabberd /var/jabberd/db > > > > Now, in /var/log/message I have the following message repeated constantly: > > « > > May 25 17:03:34 dev1vmsmgt1 jabberd/c2s[25958]: [6] [10.67.149.61, > port=56731] connect > > May 25 17:03:34 dev1vmsmgt1 jabberd/c2s[25958]: [6] packet sent before > session start, closing stream > > May 25 17:03:34 dev1vmsmgt1 jabberd/c2s[25958]: [6] [10.67.149.61, > port=56731] disconnect > > » > > > > And when osad starts: > > Starting osa-dispatcher: RHN 23937 2010/05/25 16:24:53 +02:00: ('Server does > not support TLS - <starttls /> not in <features /> stanza',) > > RHN 23937 2010/05/25 16:24:53 +02:00: ('Traceback (most recent call > last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 254, in > setup_connection\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',) > > > > As I am trying to put spacewalk in a cluster (Red Hat Cluster suite), before > configuring spacewalk I change manually the hostname of my machine to the > hostname of a Virtual IP address. I am wondering if this trick is not > interfering with the spacewalk installation and causing my problem… > > > > Could you help me to troubleshoot? Can someone who made a typical > spacewalk/jabber install send me its jabber configuration files in > /etc/jabberd/ just to see what it should looks like? > > > > I attached my own jabber configuration files to this post. > > > > Best regards, > > Mathieu > > > > ________________________________ > > De : [email protected] > [mailto:[email protected]] De la part de James Hogarth > Envoyé : jeudi 29 avril 2010 20:22 > À : [email protected] > Objet : Re: [Spacewalk-list] problem configuring jabber / osa-dispatcher > with spacewalk 0.8 > > > > 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. > > On Apr 29, 2010 7:05 PM, "DEMARQUAY, Mathieu" > <[email protected]> wrote: > > 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: > [email protected]/superclient > > Apr 29 17:50:59 mvdiff2 jabberd/sm[13601]: user not found, can't start > session: [email protected]/superclient > > > > 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 > > > > > > > > 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. > > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > > > > > > 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. > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
Same as your first email at this point - the pem file is commented out and TLS isn't being presented which osa-dispatcher looks for... Out of curiosity why RHEL5.3? RHEL is now several patches down from the 5.5 baseline... James _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
