-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Joshua,
- -------- Original Message -------- Subject: [Spacewalk-list] error jabber after upgrade 0.5 => 0.6 From: Joshua Roys <[email protected]> To: [email protected] <[email protected]> Date: 9/10/2009 6:51 PM > On 09/10/2009 12:40 PM, Michiel van Es wrote: > Hi I upgraded, spacewalk 0.5 to 0.6 but jabberd is giving errors to osad: > > ==> /var/log/rhn/osa-dispatcher.log<== > 2009/09/10 18:38:40 +02:00 1926 0.0.0.0: osad/jabber_lib.__init__ > 2009/09/10 18:38:40 +02:00 1926 0.0.0.0: > osad/jabber_lib.connect('ERROR', 'Server did not return a<features /> > stanza') > 2009/09/10 18:38:40 +02:00 1926 0.0.0.0: > osad/jabber_lib.print_message('SSLError',) > 2009/09/10 18:38:40 +02:00 1926 0.0.0.0: > osad/jabber_lib.print_message('Could not connect to jabber server', > 'devmx01.buro.info.nl') > 2009/09/10 18:38:40 +02:00 1926 0.0.0.0: > osad/jabber_lib.setup_connection('Could not connect to any jabber server',) > 2009/09/10 18:38:40 +02:00 1926 0.0.0.0: osad/jabber_lib.main('Unable to > connect to jabber servers, sleeping 10 seconds',) > > > I also got some .rpmnew files with new ssl paths but wrong > passphrases/passwords. > > Does anyone know how I can fix my jabberd for the osad and osa-dispatcher? > > Kind regards, > > Michiel > Hello, > A few things: > - try to resolve the .rpmnew files > - make sure all <pass> and <secret> stanzas contain the same password > - in c2s.xml, have an 'id' tag similar to: > <id realm='' register-enable='true' require-starttls='false' > pemfile='/etc/pki/spacewalk/jabberd/server.pem'>full-domain.name</id> > - make sure /etc/pki/spacewalk/jabberd/server.pem is readable by the > jabber user (e.g. run: sudo -u jabber stat > /etc/pki/spacewalk/jabberd/server.pem) > - as a last resort, run osa-dispatcher by hand with verbosity and see > what it says: > osa-dispatcher -N -vvvvvvvvvvvv > Let us know if that works or doesn't. I still got some errors but I can not find out what, is there a way to log or debug the modules (router, s2s etc.) seperatly.. I also found out that when I do an service jabberd restart that s2s isn't correctly stopping (always a red FAILED). So my guess is that at least that config file is wrong. Can I post the config here? > Good luck, Thanks and kind regards, > Joshua Roys Michiel > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJKqU1/AAoJEKmnTNucqQlOLG4IALm6q4nzheVL2iNR0wUt9q6T AaqEcPbOBKTfI3S3jcWW19usLnZVqXHE+4IJ6ifJOwBC0j9V0yDJJI4y2h/3X5bt f0kOuYfLFCf1E/3cYsIVRpOemLC37nwNcaVmMzu9b5WW/TzM/g9aZLUCCu3gpzVv liGeYqSkG8Em2y1SiV+JAdm6YK+DwDQ1uyOutcDoBa7fMJ7zHQuSwIkJ8tDlyZ1I tSpRdkm8tLmkXNq+F9EcR8lvoMf0JaLgPefQ9FcXA5yABg7ea32f6jRQKY/TBivX K1DXDdmplF+c16/YYgzIAD8q2abQEYOtebU7F91PhKXj9KE2SqBrWse9gbXsOXo= =Dzvd -----END PGP SIGNATURE-----
0x9CA9094E.asc
Description: application/pgp-keys
0x9CA9094E.asc.sig
Description: Binary data
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
