[ClusterLabs] SuSE12SP3 HAE SBD Communication Issue

[Gao,Yan]

First thanks for your reply, Klaus!

On 2018/12/21 10:09, Klaus Wenninger wrote:
> 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.
Yes, I think it's the issue. Could you please retrieve the latest 
maintenance update for SLE12SP3 and try? Otherwise of course you could 
temporarily enable verbose/debug logging by adding a couple of "-v" into 
  "SBD_OPTS" in /etc/sysconfig/sbd.

But frankly, it makes more sense to manually trigger fencing for example 
by "crm node fence" and see if it indeed works correctly.

> And of course you can use the list command on the other node
> to verify as well.
The "test" message in the slot might get overwritten soon by a "clear" 
if the sbd daemon is running.

Regards,
   Yan


> 
> 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
> 
> 
> 
> _______________________________________________
> 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
>