[ClusterLabs] SuSE12SP3 HAE SBD Communication Issue

[Klaus Wenninger]

On 12/21/2018 08:15 AM, Fulong Wang wrote:
> Hello Experts,
>
> I'm New to this mail lists.
> Pls kindlyforgive me if this mail has disturb you!
>
> Our Company recently is evaluating the usage of the SuSE HAE on x86
> platform.
> Wen simulating the storage disaster fail-over, i finally found that
> the SBD communication functioned normal on SuSE11 SP4 but abnormal on
> SuSE12 SP3.

I have no experience with SBD on SLES but I know that handling of the
logging verbosity-levels has changed recently in the upstream-repo.
Given that it was done by Yan Gao iirc I'd assume it went into SLES.
So changing the verbosity of the sbd-daemon might get you back
these logs.
And of course you can use the list command on the other node
to verify as well.

Klaus

> The SBD device was added during the initialization of the first
> cluster node.
>
> I have requested help from SuSE guys, but they didn't give me any
> valuable feedback yet now!
>
>
> Below are some screenshots to explain what i have encountered.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> on a SuSE11 SP4 HAE cluster,  i  run the sbd test command as below:
>
>
> then there will be some information showed up in the local system
> message log
>
>
>
> on the second node,  we can found that the communication is normal by 
>
>
>
> but when i turn to a SuSE12 SP3 HAE cluster,  ran the same command as
> above:
>
>
>
> I didn't get any  response in the system message log.
>
>
> "systemctl status sbd" also doesn't give me any clue on this.
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> What could be the reason for this abnormal behavior?  Is there any
> problems with my setup?
> Any suggestions are appreciate!
>
> Thanks!
>
>
> Regards
> FuLong
>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20181221/e2380163/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 57698 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20181221/e2380163/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 161176 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20181221/e2380163/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 148274 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20181221/e2380163/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 58918 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20181221/e2380163/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 11062 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20181221/e2380163/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 48638 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20181221/e2380163/attachment-0017.png>