[SOLVED] Spacewalk 1.9 Centos Jabber problems connecting on startup?

gdizzle · 03-15-2013, 08:58 PM

Hi All,
Just installed the latest Spacewalk 1.9 on Centos 6.4 64bit and when I start the service I get this error when starting Spacewalk:

Code:

Starting osa-dispatcher: RHN 3837 2013/03/16 11:48:07 +11:00: ('Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 252, in setup_connection\n    c = self._get_jabber_client(js)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 309, in _get_jabber_client\n    c.connect()\n  File "/usr/share/rhn/osad/jabber_lib.py", line 567, in connect\n    jabber.Client.connect(self)\n  File "/usr/lib/python2.6/site-packages/jabber/xmlstream.py", line 488, in connect\n    raise socket.error("Unable to connect to the host and port specified")\nerror: Unable to connect to the host and port specified\n',)

I have googled around it's jabber related:

Here are my troubleshooting steps so far:

* Iptables/iptables disabled and Flushed
* SElinux disabled
* stopped spacewalk ,cleared the jabber db rm -rf /var/lib/jabberd/db and restarted spacewalk
* followed this guide: https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD ,
however I am confused about point 4 "Within /etc/jabberd/server.pem, verify that the same FQDN is present here" because my server.pem does not have the FQDN in there and I am not sure how it should look??

In Spacewalk the only Failed services according to the Task Schedule Status are:

* Cobbler Sync
* Kickstart Sync

everything else has started and is working fine....

Any ideas?

Thanks

gdizzle · 03-15-2013, 10:34 PM

Ok I ran this command: strace -fe trace=network osa-dispatcher -N

I get this output, it's connecting to the wrong IP, should be trying to connect to 192.168.122.30

connect(5, {sa_family=AF_INET, sin_port=htons(5222), sin_addr=inet_addr("192.168.122.192")}, 16) = -1 EHOSTUNREACH (No route to host)

[root@centostemplate ~]# ping centostemplate
PING centostemplate.rap.local (192.168.122.192) 56(84) bytes of data.
From 192.168.122.30 icmp_seq=1 Destination Host Unreachable

Found a bad entries in /etc/hosts that caused this:

Epic fail on my part!