Hi again,
> Are there any downsides to not using OSAD/osa-dispatcher?
>
> This may sound ignorant on my part so I'll apologize ahead of time for that.
>
> I personally don't care about the pushing down of updates immediately.
>
> I've set rhnsd's interval to be 1 which means it checks in every min
I think I am pretty close to getting this working. Jabberd seems to be running
fine, but when I start osa-dispatcher on the server, I get:
Starting osa-dispatcher: RHN 670 2009/07/30 13:52:15 -04:00: ('Traceback
caught:',)
RHN 670 2009/07/30 13:52:15 -04:00: ('Traceback (most recent call last):
Are there any downsides to not using OSAD/osa-dispatcher?
This may sound ignorant on my part so I'll apologize ahead of time for that.
I personally don't care about the pushing down of updates immediately.
I've set rhnsd's interval to be 1 which means it checks in every minute anyway.
For now,
Hopefully all OSAD / Jabber issues will be addressed / RESOLVED in .6 - I've
had quirky operability between identically configured systems. Some would
accept updates, some would not. This needs to be fixed.
>Hi Again.
>>
>> on the latest nightly build I got an error while trying to start jabb
Hi Again.
>
> on the latest nightly build I got an error while trying to start jabber/sm:
>
> /usr/bin/sm: symbol lookup error: /usr/lib/jabberd/storage_db.so:
> undefined symbol: ser_string_set
The bug seems to be related to jabberd-2.2.5-1 and is fixed in
upstream. Could you perhaps update jabb
Hi all,
on the latest nightly build I got an error while trying to start jabber/sm:
/usr/bin/sm: symbol lookup error: /usr/lib/jabberd/storage_db.so:
undefined symbol: ser_string_set
osa-dispatcher.log continuously reports:
osad/jabber_lib.setup_connection('Could not connect to any jabber serv
