[Spacewalk-list] Osad not connecting to jabberd

Devan Goodwin dgoodwin at redhat.com
Fri Jul 24 13:07:57 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 24 Jul 2009 11:28:07 +0800
"Goff, Raal" <raal.goff at zettaserve.com> wrote:

> Looks like i managed to fix mine, i missed one of the shared libs
> directories in sm.xml,
> 
> So this is how i got it working, your mileage may vary:
> 
> - Change all instances of "/usr/lib/jabberd" to "/usr/lib64/jabberd"
> in s2s.xml, c2s.xml, sm.xml and router.xml
> - Change the authreg backend module to sqlite instead of db in c2s.xml
> eg:
>      <!-- Backend module to use -->
>      <module>sqlite</module>
> - Change the storage backend to use sqlite instead of db in sm.xml eg:
>      <driver>sqlite</driver>
> 
> Of course, this looks like its only an issue on x86_64 systems.
> 
> Has there been any work done on replacing osad with func? I've seen a
> few mentions of it being a future feature, but havent seen anyone
> tackling it yet?
> 
> -R

Done some investigation into it but no code yet. Func would imply some
changes, would need fully resolvable hostnames for SSL to work, and
would require clients to have ports listening for connections from the
master. Not necessarily bad things just have to consider if they're ok
for most users. Personally I'd quite like to switch from the jabber
approach to func.

Also if you're on EL5, you may want to try the 2.2.8 jabberd packages
in epel testing, they might get you past the db/sqlite issue you had,
though if you've got it working may as well leave it. :)

Cheers,

Devan



- -- 
  Devan Goodwin <dgoodwin at redhat.com>
  Software Engineer     Spacewalk / RHN Satellite
  Halifax, Canada       650.567.9039x79267
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkppsjIACgkQAyHWaPV9my7qvwCfb4uAdajQJKNiygpT5BlRkYJW
xfIAoIdAL/2JBwdEHab+URZvM0fW0mfh
=C5Wl
-----END PGP SIGNATURE-----




More information about the Spacewalk-list mailing list