[Spacewalk-list] Osa dispatcher can't connect to JabberD after restarting JabberD

[Konstantin Raskoshnyi]

Yes, that helped!

Thanks

On Tue, Aug 23, 2016 at 10:00 AM, Matt Moldvan <matt at moldvan.com> wrote:

> Check the rhndispatcher table in the Spacewalk database... if there are
> multiple entries there delete those rows first, they will be recreated.  I
> had a long rant about it earlier this week on the list that gets into a lot
> of detail and is partly related...
>
> On Tue, Aug 23, 2016 at 12:22 PM Konstantin Raskoshnyi <konrasko at gmail.com>
> wrote:
>
>> Everytime after I restart spacewalk service - I have to manually delete
>> /var/lib/jabberdb/db/*, unless that osa-dispatcher cannot connect to
>> jabberd.
>>
>> After that all clients has to re-register, and it takes some time.
>>
>> No any errors in log. SP 2.4, Scientific linux 7.2
>>
>> Thanks
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160823/493b964f/attachment.htm>