[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Spacewalk-list] osa-dispatcher and jabber



Thanks, I think this confirms that it's not doing anything to start sm or c2s:

Aug 15 07:14:15 c4t-space01 jabberd/router[24722]: shutting down
Aug 15 07:14:15 c4t-space01 kernel: router[24722] general protection rip:415909 rsp:7fff4aa14450 error:0
Aug 15 07:14:15 c4t-space01 jabberd/s2s[24743]: connection to router closed
Aug 15 07:14:15 c4t-space01 jabberd/s2s[24743]: attempting reconnect (3 left)
Aug 15 07:14:17 c4t-space01 jabberd/s2s[24743]: attempting connection to router at ::1, port=5347
Aug 15 07:14:17 c4t-space01 jabberd/s2s[24743]: [6] [router] write error: Connection refused (111)
Aug 15 07:14:17 c4t-space01 jabberd/s2s[24743]: connection to router closed
Aug 15 07:14:17 c4t-space01 jabberd/s2s[24743]: attempting reconnect (2 left)
Aug 15 07:14:18 c4t-space01 jabberd/s2s[24743]: attempting connection to router at ::1, port=5347
Aug 15 07:14:18 c4t-space01 jabberd/s2s[24743]: shutting down
Aug 15 07:14:18 c4t-space01 jabberd/s2s[24743]: connection to router closed
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: starting up
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: process id is 2549, written to /var/lib/jabberd/pid/router.pid
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: loaded user table (1 users)
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: loaded filters (0 rules)
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: [::, port=5347] listening for incoming connections
Aug 15 07:14:19 c4t-space01 jabberd/s2s[2570]: starting up (interval=3, queue=60, keepalive=0, idle=86400)
Aug 15 07:14:19 c4t-space01 jabberd/s2s[2570]: process id is 2570, written to /var/lib/jabberd/pid/s2s.pid
Aug 15 07:14:19 c4t-space01 jabberd/s2s[2570]: attempting connection to router at ::1, port=5347
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: [::1, port=51244] connect
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: [::1, port=51244] authenticated as jabberd jabberd-router
Aug 15 07:14:19 c4t-space01 jabberd/s2s[2570]: connection to router established
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: [s2s] set as default route
Aug 15 07:14:19 c4t-space01 jabberd/router[2549]: [s2s] online (bound to ::1, port 51244)
Aug 15 07:14:19 c4t-space01 jabberd/s2s[2570]: [::, port=5269] listening for connections
Aug 15 07:14:19 c4t-space01 jabberd/s2s[2570]: ready for connections


-----Original Message-----
From: spacewalk-list-bounces redhat com [mailto:spacewalk-list-bounces redhat com] On Behalf Of Milan Zazrivec
Sent: 14 August 2012 20:52
To: spacewalk-list redhat com
Subject: Re: [Spacewalk-list] osa-dispatcher and jabber

On Tuesday 14 August 2012 17:46:18 Anton Pritchard-Meaker wrote:
> Hi All,
> 
> Sorry for sending this out, but I've run into a problem I can't get around.
> I've had Spacewalk up and running and can update systems (initiated 
> from the client via yum), but I can't get osad-dispatcher going.
> 
> Selinux is disabled as is the firewall.
> 
> Here's the error I get:
> 
> [root c4t-space01 pid]# /etc/init.d/jabberd restart Terminating 
> jabberd processes ...
> Stopping router:                                           [  OK  ]
> Stopping sm:                                               [FAILED]
> Stopping c2s:                                              [FAILED]
> Stopping s2s:                                              [  OK  ]
> Initializing jabberd processes ...
> Starting router:                                           [  OK  ]
> Starting sm:                                               [  OK  ]
> Starting c2s:                                              [  OK  ]
> Starting s2s:                                              [  OK  ]
> [root c4t-space01 pid]# ls
> router.pid  s2s.pid
> 
> [root c4t-space01 pid]# /etc/init.d/osa-dispatcher restart
> Shutting down osa-dispatcher:                              [  OK  ]
> Starting osa-dispatcher: RHN 19797 2012/08/14 15:13:18 +01: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.4/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',) [  OK  ] [root c4t-space01 pid]#
> 
> All the jabber configs are set to the FQDN of the server, but it would 
> seem sm and c2s aren't starting.
> 
> Hostname is set:
> 
> [root c4t-space01 jabberd]# hostname
> c4t-space01.test.channel4.com
> 
> Reverse DNS is set:
> 
> [root c4t-space01 db]# nslookup 192.168.11.171
> Server:         192.168.8.181
> Address:        192.168.8.181#53
> 
> 171.11.168.192.in-addr.arpa     name = c4t-space01.test.xxxxxxx.com.
> 
> 
> Hosts entry in place:
> 
> [root c4t-space01 db]# cat /etc/hosts
> # Do not remove the following line, or various programs # that require 
> network functionality will fail.
> 127.0.0.1               localhost
> 
> 192.168.11.171          c4t-space01.test.xxxxxxx.com
> 
> 
> Contents of the server.pem:
> 
> [root c4t-space01 rhn]# cd /etc/pki/spacewalk/jabberd/
> [root c4t-space01 jabberd]#
> [root c4t-space01 jabberd]# head server.pem
> Certificate:
>     Data:
>         Version: 3 (0x2)
>         Serial Number:
>             d9:4b:9e:23:41:31:a0:44
>         Signature Algorithm: sha1WithRSAEncryption
>         Issuer: C=GB, ST=N.Yorks, L=York, O=Kit Digital, 
> OU=c4t-space01.test.xxxxxxx.com, CN=c4t-space01.test.xxxxxxx.com Validity
>             Not Before: Aug  7 13:32:00 2012 GMT
>             Not After : Aug  8 13:32:01 2036 GMT
> [root c4t-space01 jabberd]#
> 
> The FQDN for jabber and osa-dispatcher are also set in /etc/rhn/rhn.conf.
> 
> I noticed the server.pem under /etc/jabberd contained no conent for 
> some reason, so I have copied this from /etc/pki/spacewalk/jabberd/
> 
> Is there some debug logging I can enable for Jabber? Any assistance on 
> this would be great, as this is basically the last obstacle between me 
> having a very nice Spacewalk set up.

As root:

# tail -f /var/log/messages

And while the above is running:

# service jabberd restart

Do you see any errors / anything suspicious in the above log?

-MZ

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list redhat com
https://www.redhat.com/mailman/listinfo/spacewalk-list


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]