Josh,
Thank You for the help!
I set jabber to put its log files to /var/log/rhn/ for ease of viewing.
The problem turned out to be that the fqdn "spacewalk.mydomain.com" ,
was not consisitent in the sm.xml c2s.xml files, I corrected this, then
found out in the osa-dispatcher.log file, that my SSL CN was mismatched.
This Mismatch was caused by the the PTR record in my dns resolving to an
alternate FQDN, during my intial setup.
Instead of reconfiguring everything, I just told the osa-dispatcher to
not check for the mismatch, by commenting out the following:
# if common_name != hdot:
# raise SSLVerifyError("Mismatch: peer name: %s; common name:
%s" %
# (self._host, common_name))
in:
/usr/share/rhn/osad/jabber_lib.py
After that was changed, I started osa_dispatcher, and there was an issue
with the username and password it was using for jabberd. I found out
which username and password the osa-dispatcher was attempting to use, by
adding this in the
/usr/share/rhn/osad/jabber_lib.py file
# Need to register the user if possible
log_error("Invalid password", password)
log_error("User:", username)
I took a look in the jabber database to see if this password was right:
1 - cd /var/lib/jabberd/db
2 - strings * |grep rhn-dispatcher- |grep -v com |grep -v sat
(the password from the osa log did not match (perhaps due to me
re-installing jabberd and running through the setup again)
Either way, I now have the right password and put it in /etc/rhn/rhn.conf
I started osa-dispatcher, and it worked!
Thanks for pointing me in the right direction.
Mike
On 12/10/2009 09:33 AM, Joshua Roys wrote:
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
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
