Hello Ulrich,

1. "corosync[13979]:   [MAIN  ] parse error in config: The token hold timeout parameter (16 ms) may not be less than (30 ms)."

----There is no difference between corosync 1 (SLES11 SP4) and corosync 2 (SLES12 SP4). The error occurred because you specified the "hold" in totem less than 30 ms (I guess, because there is no config file you provided) . This is not allowed. Please reference corosync.conf(5). The 30ms is come from "(int)(1000/HZ)*3", the HZ used is 100 because it stands for the low utilization of CPU.

2. "corosync[13979]:   [MAIN  ] interface section bindnetaddr is used together with nodelist. Nodelist one is going to be used"

----- This is a wired problem, the nodelist must be specified if you use UDPU as the totem.transport with bindnetaddr. If you want to figure out the reason caused that, please publish the config file.


Regards,

Yuan

On 4/25/19 9:05 PM, Roger Zhou wrote:
Hi Yuan,

I'm wondering you might have some clue, coincidentally with your recent finding?

Cheers,
Roger

---------- Forwarded message ---------
From: *Ulrich Windl* <[email protected] <mailto:[email protected]>>
Date: Tue, 23 Apr 2019 at 10:33
Subject: [ClusterLabs] "Funny" message from corosync (SLES12 SP4)
To: <[email protected] <mailto:[email protected]>>


Hi!

Fighting with the cahnges between corosync 1 (SLES11 SP4) and corosync 2 (SLES12 SP4), I got some "funny" error message: corosync[13979]:   [MAIN  ] parse error in config: The token hold timeout parameter (16 ms) may not be less than (30 ms).

The funny part is that "hold" is not set at all in the config file!

I guess it's auto-computed from other parameters.

The other funny thing is when following corosync.conf.example.unicast (using interface and nodelist), I see this message: corosync[13979]:   [MAIN  ] interface section bindnetaddr is used together with nodelist. Nodelist one is going to be used.
corosync[13979]:   [MAIN  ] Please migrate config file to nodelist.

I guess the sample is not up-to-date...

Regards,
Ulrich




_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Reply via email to