On 12/22/18 5:27 AM, Andrei Borzenkov wrote:
21.12.2018 12:09, 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.
Do you mean
commit 2dbdee29736fcbf0fe1d41c306959b22d05f72b0
Author: Gao,Yan <y...@suse.com>
Date: Mon Apr 30 18:02:04 2018 +0200
Log: upgrade important messages and downgrade unimportant ones
?? This commit actually increased severity for message on target node:
@@ -1180,7 +1180,7 @@ int servant(const char *diskname, int mode, const
void* argp)
}
if (s_mbox->cmd > 0) {
- cl_log(LOG_INFO,
+ cl_log(LOG_NOTICE,
"Received command %s from %s on disk %s",
char2cmd(s_mbox->cmd), s_mbox->from,
diskname);
and did not change severity for messages on source node (they are still
INFO).
True. Not sure if any of them should belong to notice if everything
works well... sbd commands that send messages can be supplied with -v as
well of course.
Regards,
Yan
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@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@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@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@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
