The installation of the libqb  was done with yum install  commnad, and it was the 64bit. I tried the repoquery command but my output it was different from yours.
-------------------------------------------------------------
]# repoquery --requires --recursive --resolve pacemaker
pacemaker-0:1.1.12-8.el6.x86_64
corosynclib-0:1.4.1-17.el6.x86_64
bash-0:4.1.2-15.el6_5.1.x86_64
libxml2-0:2.7.6-8.el6_3.3.x86_64
glibc-0:2.12-1.80.el6_3.3.i686
pam-0:1.1.1-10.el6_2.1.x86_64
libuuid-0:2.17.2-12.7.el6.x86_64
libxslt-0:1.1.26-2.el6_3.1.x86_64
python-0:2.6.6-29.el6_2.2.i686
glib2-0:2.28.8-4.el6.x86_64
pacemaker-libs-0:1.1.12-8.el6.x86_64
perl-4:5.10.1-127.el6.x86_64
ncurses-libs-0:5.7-3.20090208.el6.x86_64
pacemaker-libs-0:1.1.12-8.el6.i686
resource-agents-0:3.9.2-12.el6.x86_64
pacemaker-cluster-libs-0:1.1.12-8.el6.x86_64
corosync-0:1.4.1-17.el6.x86_64
libqb-0:0.16.0-2.el6.x86_64
gnutls-0:2.8.5-18.el6.x86_64
libqb-0:0.16.0-2.el6.i686
bzip2-libs-0:1.0.5-7.el6_0.x86_64
pacemaker-cli-0:1.1.12-8.el6.x86_64
python-0:2.6.6-29.el6_2.2.x86_64
pacemaker-cluster-libs-0:1.1.12-8.el6.i686
clusterlib-0:3.0.12.1-59.el6.x86_64
glibc-0:2.12-1.80.el6_3.5.x86_64
libtool-ltdl-0:2.2.6-15.5.el6.x86_64

--------------------------------------------------------------

I just noticed, that my server is running 6.3 version of SL, and not the latest 6.6 (as i thought at first). May thats the problem.

Antonis

On 4/8/2015 5:02 μμ, Andreas Mock wrote:
[log in to unmask]" type="cite">
Hmmm,

at my site it seems to work. How have you installed it?
Right version 32bit/64bit?
rpm -i ./libqb-0.17.1-1.el6.x86_64.rpm
or 
yum install ./libqb-0.17.1-1.el6.x86_64.rpm

So, it's time to 
compare:

I do habe SL 6.6 64bit.

A repoquery --requires --recursive --resolve pacemaker shows the following:

pacemaker-0:1.1.12-8.el6.x86_64
corosynclib-0:1.4.7-1.el6.x86_64
bash-0:4.1.2-29.el6.x86_64
libxml2-0:2.7.6-20.el6.x86_64
glibc-0:2.12-1.149.el6_6.5.i686
pam-0:1.1.1-20.el6.x86_64
libuuid-0:2.17.2-12.18.el6.x86_64
libxslt-0:1.1.26-2.el6_3.1.x86_64
python-0:2.6.6-64.el6.i686
glib2-0:2.28.8-4.el6.x86_64
pacemaker-libs-0:1.1.12-8.el6.x86_64
perl-4:5.10.1-136.el6.x86_64
ncurses-libs-0:5.7-3.20090208.el6.x86_64
pacemaker-libs-0:1.1.12-8.el6.i686
resource-agents-0:3.9.5-12.el6.x86_64
pacemaker-cluster-libs-0:1.1.12-8.el6.x86_64
corosync-0:1.4.7-1.el6.x86_64
libqb-0:0.16.0-2.el6.x86_64
gnutls-0:2.8.5-14.el6_5.x86_64
libqb-0:0.16.0-2.el6.i686
bzip2-libs-0:1.0.5-7.el6_0.x86_64
pacemaker-cli-0:1.1.12-8.el6.x86_64
python-0:2.6.6-52.el6.x86_64
pacemaker-cluster-libs-0:1.1.12-8.el6.i686
clusterlib-0:3.0.12.1-68.el6.x86_64
glibc-0:2.12-1.149.el6_6.4.x86_64
libtool-ltdl-0:2.2.6-15.5.el6.x86_64

yum list libqb
Geladene Plugins: changelog, security
Installierte Pakete
libqb.x86_64   0.17.1-1.el6     @/libqb-0.17.1-1.el6.x86_64
Verfügbare Pakete
libqb.i686     0.16.0-2.el6     sl

Hope that helps to investigate your problem.

Best regards
Andreas


-----Ursprüngliche Nachricht-----
Von: [log in to unmask] [mailto:owner-
[log in to unmask]] Im Auftrag von Antonis Kopsaftis
Gesendet: Dienstag, 4. August 2015 15:54
An: [log in to unmask]
Betreff: Re: Pacemaker problem after last night updates..

After installing the updated libqb, and restarting
pacemaker/corosync...i get segfaults...and  pacemaker does not work..

Aug  4 16:49:10 percona2 kernel: cib[3009]: segfault at 888 ip
00007f31f1c550ac sp 00007fff545697e0 error 4 in
libc-2.12.so[7f31f1bdc000+18a000]
Aug  4 16:49:12 percona2 kernel: cib[3012]: segfault at 888 ip
00007f9da998c75d sp 00007fffbe951450 error 4 in
libc-2.12.so[7f9da9913000+18a000]
Aug  4 16:49:13 percona2 kernel: cib[3015]: segfault at 888 ip
00007f3e4b03375d sp 00007fff621a0470 error 4 in
libc-2.12.so[7f3e4afba000+18a000]
Aug  4 16:49:14 percona2 kernel: cib[3018]: segfault at 888 ip
00007fd537fb775d sp 00007fffc288aee0 error 4 in
libc-2.12.so[7fd537f3e000+18a000]
Aug  4 16:49:15 percona2 kernel: cib[3021]: segfault at 888 ip
00007faa2db1175d sp 00007fffed481d00 error 4 in
libc-2.12.so[7faa2da98000+18a000]

The problem with  libcrmcommon.so.3 stopped by the way...

Antonis

On 4/8/2015 3:53 μμ, Akemi Yagi wrote:
On Tue, Aug 4, 2015 at 4:46 AM, Andreas Mock <[log in to unmask]>
wrote:
Hi all,

just jumped into the same mess...

There is a bug report at RHEL
https://access.redhat.com/solutions/1415913

But I don't know the solution.

It seems that libqb should have been updated too.

Can you please investigate this problem?
Try installing libqb-0.17.1-1.el6 from "sl6rolling":


http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/os/Package
s/libqb-0.17.1-1.el6.i686.rpm
or

http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/os/Package
s/libqb-0.17.1-1.el6.x86_64.rpm
I believe that will solve the issue.

Akemi