On 02/08/2010 09:47 AM, Stefan Bluhm wrote:
This is what the logs state after a /usr/sbin/rhn-satellite stop (this is when I got the error "Stopping s2s: [FAILED]"):Feb 8 14:35:23 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524] connect Feb 8 14:35:25 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524] error: XML parse error (not well-formed (invalid token)) Feb 8 14:35:25 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524] disconnect
Hmm, that XML error is strange. I wonder if that's from the config files? Can you check the following:
# xmllint --noout /etc/jabberd/*.xml
Now heading straight for a /usr/sbin/rhn-satellite start:
...
So I can't really see any indications of an error in the logs. Note that
I can now do a "telnet 127.0.0.1 5347" and connect successfully. So i am
not sure why the connection is refused on shut down. Do I need a FQDN or
should it all work on the 127.0.0.1 IP?
Now same thing for the log at /var/log/rhn/osa-dispatcher
Whilst stopping:
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.main('Unable
to connect to jabber servers, sleeping 10 seconds',)
The port osa-dispatcher will try to connect to is 5222, which is run by c2s. See what programs are listening:
# netstat -ptnl Let's check for a common problem: # cd /var/lib/jabberd/db/ (you may need to install db4-utils for the next step) # db_verify authreg.db sm.db ; echo $? 0 -- Josh
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
