Hi All.
Recently we got a lrmd coredump. It occured only once and we don't know how to
reproduce it.
The version we use is pacemaker-1.1.15-11. Ths os is centos 7.
Core was generated by `/usr/libexec/pacemaker/lrmd'.
Program terminated with signal 11, Segmentation fault.
#0 __strcasecmp_l_avx
Yes, it was running on bare-metal.
After upgrade to SL7.3 and pacemaker 1.1.15 the problem is gone.
I hope gone forever.
--
Alexey Kurnosov
> ... and it is running on bare-metal?
> Just to be sure it is not due to some code-patching done by a hypervisor ...
>
pgpDdYGEVrMdf.pgp
Description:
On 01/31/2017 03:12 PM, ale...@kurnosov.spb.ru wrote:
> As i said, we used rpm from standard repo, hardly it compiled incorrectly.
> And according
> to a spec L5630 (the node's CPU) has SSE4.2 support. And in that case it
> should be
> illegal instruction exception, not segfault.
... and it is
As i said, we used rpm from standard repo, hardly it compiled incorrectly. And
according
to a spec L5630 (the node's CPU) has SSE4.2 support. And in that case it should
be
illegal instruction exception, not segfault.
--
Alexey Kurnosov
On Tue, Jan 31, 2017 at 07:34:18AM +0100, Kristoffer
Hi All.
We have the heterogeneous corosync/pacemaker cluster of 5 nodes: 3
SL7(Scientific linux) and 2 SL6.
SL7 pacemaker installed from a standard repo (corosync - 2.3.4, pacemaker -
1.1.13-10), SL6 build from sources (same version).
The cluster not unified, some nodes have RA which other do
