<html><head></head><body><div class="yahoo-style-wrap" style="font-family:courier new, courier, monaco, monospace, sans-serif;font-size:16px;"><div dir="ltr" data-setdir="false">Hello Community,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I have a question about the stack in newer version compared to our SLES 11 openais stack.</div><div dir="ltr" data-setdir="false">Can someone clarify if a node with SBD will invoke a crashkernel before self killing ?</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">According to my tests on SLES 11 ,when another node kills the unresponsive one - crashkernel is invoked and a dump is present at /var/crash , but if the node stucks for some reason (naughty admin) - there is no sign of a crash (checked on the iLO to be sure).</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I'm not sure if this behaviour is the same on newer software version (SLES 12/15) and if I can workaround it - as we still struggle to find the reason why our clusters fence on a very specific situation (the clusters are using MDADM raid1-s on a dual-DC environment instead of SAN replication) where remote DC is unavailable for 20-30s until SAN/Network is rerouted. We have enabled crashdump on some of the systems , but we are pending a reboot and then a real DC<->DC connectivity outage to gather valuable info,as corosync is using dual-rings and is not affected, SBD is using survive on pacemaker and we suspect that the nodes suicide.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Best Regards,</div><div dir="ltr" data-setdir="false">Strahil Nikolov</div></div></body></html>