[Spacewalk-list] error jabber after upgrade 0.5 => 0.6

[Joshua Roys]

On 09/10/2009 12:40 PM, Michiel van Es wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJKqSv5AAoJEKmnTNucqQlORBsIAK8LhRNBzse8HDSiYixTrM33
> 5cJcE7deRgaQS9abQWmU65hPIy0A2XtNvoSoFBsgoy8cZ2Rs5wu7OlZy8tjuydfR
> WtLTH5ZW7xrVfkFBX4uqcK2cBuH7QvQJlSkjGbcMO7p1tGR1dm5ZC+neac+MmGnm
> FXqoeXvEa/Hz0nZrmsr2pQ1sf1wSoMvlToBq/RZr4YXFxD9/1WBeyMUCKsDdAOyJ
> UXuLzfDlVxr3NL7oOMAj4BSr3KKWxRwl8PQHcFIvCtkoZD81felZP5DlgYZJMc/R
> h4b04pexchzRy3UUDhrhrQbZWfGhmECfThJHRz32KrcpLfPz56YFFLt21KrtD7o=
> =Ng63
> -----END PGP SIGNATURE-----

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.

Good luck,

Joshua Roys