[Spacewalk-list] jabber sm segfault

Thu Feb 25 13:01:32 UTC 2016

Do not forget to recreate the sqlite sm db by doing :

sudo -u jabber sqlite3 /var/lib/jabberd/db/sqlite.db < /usr/share/jabberd/db-setup.sqlite

This is forgotten in many documentations but mandatory (unless using another storage)

De : spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] De la part de Stehle, Christian
Envoyé : jeudi 25 février 2016 12:50
À : spacewalk-list at redhat.com
Objet : Re: [Spacewalk-list] jabber sm segfault

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

Christian

Von: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] Im Auftrag von Slava Bendersky
Gesendet: Donnerstag, 25. Februar 2016 05:29
An: spacewalk-list <spacewalk-list at redhat.com>
Betreff: Re: [Spacewalk-list] jabber sm segfault

Hello Everyone,

I understand that everybody busy. The current solution/workaround is create spacewalk proxy and re register affected clients through new proxy. This solution work, because segfault cause by osa-dispatcher and when jabber run on proxy without osa-dispatcher, no problems by far. I think something not right in SSL implementation of osa-dispatcher.  Please see my comments in bug report. 

I tried update to last glibc update, but segfault still present.

I hope it will take some priority.

Slava. 

  _____  

From: "Christian Stehle" < <mailto:Christian.Stehle at hs-neu-ulm.de> Christian.Stehle at hs-neu-ulm.de>
To: "spacewalk-list" < <mailto:spacewalk-list at redhat.com> spacewalk-list at redhat.com>, "Jan Hutař" < <mailto:jhutar at redhat.com> jhutar at redhat.com>
Sent: Wednesday, 24 February, 2016 01:27:00
Subject: Re: [Spacewalk-list] jabber sm segfault

Helle Slava,

any news on this issue?

We updated from 2.2->2.3->2.4 and have the same problems with osa-dispatcher on centos6. 

For a few minutes it works but then it stops. After restarting jabberd SM fails stopping.

With 2.2, it was fine. But now osa is nearly useless.

We also applied the workarounds (deleting db, deleting conf on clients), but without success. 

You also use centos 6, maybe it works on 7?

Any help or advice would be great!

Christian

Von: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] Im Auftrag von Slava Bendersky
Gesendet: Donnerstag, 18. Februar 2016 19:36
An: Jan Hutař < <mailto:jhutar at redhat.com> jhutar at redhat.com>
Cc: spacewalk-list < <mailto:spacewalk-list at redhat.com> spacewalk-list at redhat.com>
Betreff: Re: [Spacewalk-list] jabber sm segfault

Hello Everyone,

I opened bug report a week ago. I need get attention to this report  <https://bugzilla.redhat.com/show_bug.cgi?id=1306563> https://bugzilla.redhat.com/show_bug.cgi?id=1306563 it affect daily operations.

Slava.

  _____  

From: "Jan Hutař" < <mailto:jhutar at redhat.com> jhutar at redhat.com>
To: "spacewalk-list" < <mailto:spacewalk-list at redhat.com> spacewalk-list at redhat.com>
Cc: "Slava Bendersky" < <mailto:volga629 at networklab.ca> volga629 at networklab.ca>
Sent: Thursday, 11 February, 2016 01:49:34
Subject: Re: [Spacewalk-list] jabber sm segfault

On Wed, 10 Feb 2016 12:09:15 -0500 (EST) Slava Bendersky
< <mailto:volga629 at networklab.ca> volga629 at networklab.ca> wrote:

> Hello Everyone, 
> After upgrade to spacewalk 2.4 jabber sm module is send
> segfault. And it happened on different spacewalk servers. 
> 
> 
> [root at qa01repo00 ~]# cat /etc/redhat-release 
> Red Hat Enterprise Linux Server release 6.7 (Santiago) 
> 
> [root at qa01repo00 ~]# rpm -qa | grep jabber 
> jabberpy-0.5-0.21.el6.noarch 
> spacewalk-setup-jabberd-2.3.2-1.el6.noarch 
> jabberd-2.2.14-6.el6.x86_64 
> 
> Feb 10 11:12:46 qa01repo00 kernel: sm[29540]: segfault at 18
> ip 00007f724e0593f6 sp 00007fff5e7ac508 error 4 in libc-2.12.so
> [7f724df31000+18a000] 
> 
> Feb 10 10:26:09 ca01repo00 kernel: sm[15823]: segfault at 18
> ip 00007fe62c9ce2b6 sp 00007fff01fb0078 error 4 in libc-2.12.so
> [7fe62c8a6000+18a000] 
> 
> Slava. 

Hello,
same I have just wrote you in the other email applies for this
and this might be quite severe. When you will be creating the
bugzilla, please make sure you describe your setup in detail so
the issue can be reproduced on developers system.

   <https://bugzilla.redhat.com/enter_bug.cgi?product=Spacewalk> https://bugzilla.redhat.com/enter_bug.cgi?product=Spacewalk

Also take a look if ABRT noticed the failure and upload its info
about it as well (e.g. stacktrace might be very important).

Thank you in advance,
Jan

-- 
Jan Hutar     Systems Management QA
 <mailto:jhutar at redhat.com> jhutar at redhat.com     Red Hat, Inc.

_______________________________________________
Spacewalk-list mailing list
 <mailto:Spacewalk-list at redhat.com> Spacewalk-list at redhat.com
 <https://www.redhat.com/mailman/listinfo/spacewalk-list> https://www.redhat.com/mailman/listinfo/spacewalk-list

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