[Spacewalk-list] Osad not connecting to jabberd

[Goff, Raal]

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


On 24/07/2009, at 10:50 AM, Goff, Raal wrote:

> I've been working through this problem as well...
>
>> The authreg_db.so module is in /usr/lib64/jabberd/authreg_db.so
>>
>> I added /usr/lib64/jabberd to ld.so.conf.d/jabberd.conf and ran
>> ldconfig -v but
>> it still couldn't find authreg_db.so
> The path for the libs is actually specified in the config file for
> each jabber component, so you have to go through and change the path:
>
> eg:
>     <!-- Dynamic authreg modules path -->
>     <path>/usr/lib64/jabberd</path>
>
> After the authreg_db.so problems I also found that jabberd was
> complaining about the db4 database being corrupted, so i changed all
> the db backend directives to use sqlite instead. Now the daemons load,
> and osad clients can connect, but they dont seem to receive any
> messages.
>
> osa-dispatcher complains about the following:
>
> 2009/07/24 10:44:38 +09:00 3038 0.0.0.0: osad/jabber_lib.main('ERROR',
> 'Traceback (most recent call last):\n  File "/usr/share/rhn/osad/
> jabber_lib.py", line 120, in main\n    c = self.setup_connection
> (no_fork=no_fork)\n  File "/usr/share/rhn/osad/jabber_lib.py", line
> 285, in setup_connection\n    resource=self._resource)\n  File "/usr/
> share/rhn/osad/dispatcher_client.py", line 33, in start\n    self.auth
> (username, password, resource)\n  File "/usr/share/rhn/osad/
> jabber_lib.py", line 883, in auth\n    self.SendAndWaitForResponse
> (auth_set_iq)\n  File "/usr/lib/python2.4/site-packages/jabber/
> jabber.py", line 401, in SendAndWaitForResponse\n    return
> self.waitForResponse(ID,timeout)\n  File "/usr/share/rhn/osad/
> jabber_lib.py", line 1151, in waitForResponse\n    raise TimeoutError
> ()
> \nTimeoutError\n')
>
> I'm wondering if there is any way to replace jabberd2 with one of the
> other available jabber servers such as openfire or jabberd1.4 or
> ejabberd. Has anyone attempted this?
>
> -R
>
>
> ZettaServe Disclaimer: This email and any files transmitted with it
> are confidential and intended solely for the use of the individual
> or entity to whom they are addressed. If you are not the named
> addressee you should not disseminate, distribute or copy this e-
> mail. Please notify the sender immediately if you have received this
> email by mistake and delete this email from your system. Computer
> viruses can be transmitted via email. The recipient should check
> this email and any attachments for the presence of viruses.
> ZettaServe Pty Ltd accepts no liability for any damage caused by any
> virus transmitted by this email.
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list


ZettaServe Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately if you have received this email by mistake and delete this email from your system. Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. ZettaServe Pty Ltd accepts no liability for any damage caused by any virus transmitted by this email.