[Spacewalk-list] osa-dispatcher "service requested for unknown domain" ??

[Joshua Roys]

On 12/10/2009 09:20 AM, Michael Masseo wrote:
> 2009/12/10 09:12:27 -04:00 10232 0.0.0.0:
> osad/jabber_lib.connect('ERROR', 'Got:',<error><host-unknown xmlns =
> 'urn:ietf:params:xml:ns:xmpp-streams'  /><text xmlns =
> 'urn:ietf:params:xml:ns:xmpp-streams'>service requested for unknown
> domain</text></error>)
> 2009/12/10 09:12:27 -04:00 10232 0.0.0.0:
> osad/jabber_lib.print_message('SSLError',)
> 2009/12/10 09:12:27 -04:00 10232 0.0.0.0:
> osad/jabber_lib.print_message('Could not connect to jabber server',
> 'spacewalk.myhost.com')
> 2009/12/10 09:12:27 -04:00 10232 0.0.0.0:
> osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
> 2009/12/10 09:12:27 -04:00 10232 0.0.0.0: osad/jabber_lib.main('Unable
> to connect to jabber servers, sleeping 10 seconds',)
>
> I have looked at all of the SSL settings, and it appears that the .pem
> file correctly exists. I have also verified that the FQDN is in the
> jabberd config files, and is reachable.
> Im not sure what else to do, does anyone have insight?
>

The next thing to check is the jabberd output.  (what version of 
jabberd/spacewalk do you have?)  If you didn't set it to go anywhere 
else, it will do to /var/log/messages .  If you don't see anything out 
of the norm, then here's what you can do:

# service jabberd stop
...
(open 4 terminals, or 4 `screen's)
t1# router -D

t2# sm -D

t3# c2s -D

t4# s2s -D

And first look for errors on startup.  None of them should detach from 
the terminal or otherwise end.  Then try osa-dispatcher again and see 
what you get.

Hope to help,

Josh

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2719 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20091210/228db34d/attachment.p7s>