[Spacewalk-list] jabber sm segfault

[Thomas Mueller]

Am 25.02.2016 um 12:50 schrieb Stehle, Christian:
>
> Hi,
>
>  
>
> i tried this workaround and it seems to work.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1222868
>
>  
>
> in etc/crontab I call once a day this command to reset the jabbed db,
> now with a short sleep before starting osa-dispatcher.
>
>  
>
> service jabberd stop
>
> service osa-dispatcher stop
>
> rm -Rf /var/lib/jabberd/db/*
>
> service jabberd start
>
> sleep 10m (or other time, depends on number of systems running)
>
> service osa-dispatcher start
>
>  
>
Deleting /var/lib/jabberd you'll delete all state information about
jabber clients. This will cause you trouble if you have
spacewalk/satellite proxies in use. The clients connected to the
spacewalk-proxy won't notice the deleted data and therefore not
re-subscribe. Any osad action regarding this clients will be queued
without a error message until the osad service on the affected services
get restarted.

I would not recommend to delete jabberd data.


- Thomas


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160226/f0546b6f/attachment.htm>