[Spacewalk-list] Problems With Jabberd on Fresh Install
Glennie, Jonathan - 0443 - MITLL
jrglenni at ll.mit.edu
Mon Mar 26 14:10:27 UTC 2012
Hello-
We've recently setup a fresh install of Spacewalk 1.6 on CentOS 6 using
Postgres. Install went fine, set up some repos and started adding clients
but I realize osa-dispatcher wasn't working properly. I get the following
when trying to start it:
Starting osa-dispatcher: RHN 4716 2012/03/26 09:59:09 -04: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 also see the following in the logs when trying to restart jabberd:
Mar 26 09:53:13 walkin jabberd/router[3742]: shutting down
Mar 26 09:53:13 walkin jabberd/s2s[3763]: connection to router closed
Mar 26 09:53:13 walkin jabberd/router[3742]: [::1, port=35373] disconnect
Mar 26 09:53:13 walkin jabberd/router[3742]: [s2s] default route offline
Mar 26 09:53:13 walkin jabberd/router[3742]: [s2s] offline
Mar 26 09:53:13 walkin jabberd/s2s[3763]: attempting reconnect (3 left)
Mar 26 09:53:15 walkin jabberd/s2s[3763]: attempting connection to router at
::1, port=5347
Mar 26 09:53:15 walkin jabberd/s2s[3763]: [6] [router] write error:
Connection refused (111)
Mar 26 09:53:15 walkin jabberd/s2s[3763]: connection to router closed
Mar 26 09:53:15 walkin jabberd/s2s[3763]: attempting reconnect (2 left)
Mar 26 09:53:17 walkin jabberd/s2s[3763]: attempting connection to router at
::1, port=5347
Mar 26 09:53:17 walkin jabberd/s2s[3763]: [6] [router] write error:
Connection refused (111)
Mar 26 09:53:17 walkin jabberd/s2s[3763]: connection to router closed
Mar 26 09:53:17 walkin jabberd/s2s[3763]: attempting reconnect (1 left)
Mar 26 09:53:19 walkin jabberd/s2s[3763]: attempting connection to router at
::1, port=5347
Mar 26 09:53:19 walkin jabberd/s2s[3763]: [6] [router] write error:
Connection refused (111)
Mar 26 09:53:19 walkin jabberd/s2s[3763]: connection to router closed
Mar 26 09:53:19 walkin jabberd/s2s[3763]: shutting down
Mar 26 09:53:26 walkin jabberd/router[4566]: starting up
Mar 26 09:53:26 walkin jabberd/router[4566]: process id is 4566, written to
/var/lib/jabberd/pid/router.pid
Mar 26 09:53:26 walkin jabberd/router[4566]: loaded user table (1 users)
Mar 26 09:53:26 walkin jabberd/router[4566]: loaded filters (0 rules)
Mar 26 09:53:26 walkin jabberd/router[4566]: [::, port=5347] listening for
incoming connections
Mar 26 09:53:26 walkin jabberd/sm[4573]: starting up
Mar 26 09:53:26 walkin jabberd/sm[4573]: process id is 4573, written to
/var/lib/jabberd/pid/sm.pid
Mar 26 09:53:26 walkin jabberd/sm[4573]: loading 'db' storage module
Mar 26 09:53:26 walkin jabberd/c2s[4580]: starting up
Mar 26 09:53:26 walkin jabberd/c2s[4580]: process id is 4580, written to
/var/lib/jabberd/pid/c2s.pid
Mar 26 09:53:26 walkin jabberd/c2s[4580]: modules search path:
/usr/lib64/jabberd
Mar 26 09:53:26 walkin jabberd/c2s[4580]: loading 'db' authreg module
Mar 26 09:53:26 walkin jabberd/s2s[4587]: starting up (interval=3, queue=60,
keepalive=0, idle=86400)
Mar 26 09:53:26 walkin jabberd/s2s[4587]: process id is 4587, written to
/var/lib/jabberd/pid/s2s.pid
Mar 26 09:53:26 walkin jabberd/s2s[4587]: attempting connection to router at
::1, port=5347
Mar 26 09:53:26 walkin jabberd/router[4566]: [::1, port=35495] connect
Mar 26 09:53:26 walkin jabberd/router[4566]: [::1, port=35495] authenticated
as jabberd at jabberd-router
Mar 26 09:53:26 walkin jabberd/s2s[4587]: connection to router established
Mar 26 09:53:26 walkin jabberd/router[4566]: [s2s] set as default route
Mar 26 09:53:26 walkin jabberd/router[4566]: [s2s] online (bound to ::1,
port 35495)
Mar 26 09:53:26 walkin jabberd/s2s[4587]: [::, port=5269] listening for
connections
Mar 26 09:53:26 walkin jabberd/s2s[4587]: ready for connections
I've tried switching the router, s2s, c2s and sm xml files to all use IP v4
instead of IP v6 but it doesn't seem to make a difference, I still get the
same issues. I've edited my hosts file in both cases to look like below:
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
x.x.x.x walkin.x.x.x.x walkin
I checked the names in the XML files as well as the name in the cert and the
CN is not my fqdn, even though I specified the fqdn during the spacewalk
setup. I even re-ran the setup thinking that I must not have the first time
and let it regenerate the SSL Cert and it still is only showing the hostname
and not the FQDN. I'm at a loss as to why this is happening, so any
insight would be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120326/16fec2b9/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5410 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120326/16fec2b9/attachment.bin>
More information about the Spacewalk-list
mailing list