Re: [ClusterLabs] Antw: Re: Upgrade corosync problem

[Salvatore D'angelo]

Hi again, I did another test. I modified docker container in order to be able to run strace. Running strace corosync-quorumtool -ps I got the following:

corosync-quorumtool-strace.log
Description: Binary data

I tried to understand what happen behind the scene but it is not easy for me. Hoping someone on this list can help. On 26 Jun 2018, at 16:06, Ulrich Windl <ulrich.wi...@rz.uni-regensburg.de> wrote: Salvatore D'angelo <sasadang...@gmail.com> schrieb am 26.06.2018 um 10:40 in Nachricht <fe52370c-4968-4223-a531-3ee2ab793...@gmail.com>: Hi, Yes, I am reproducing only the required part for test. I think the original system has a larger shm. The problem is that I do not know exactly how to change it. If you want to go paranoid, here's a setting from a SLES11 system: # grep shm /etc/sysctl.conf kernel.shmmax = 9223372036854775807 kernel.shmall = 1152921504606846720 [...] See SYSCTL(8) Regards, Ulrich _______________________________________________ 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