Your message dated Wed, 20 Sep 2017 18:55:46 +0200 with message-id <87fubh48dp....@lant.ki.iif.hu> and subject line Re: corosync: cannot set lrm parameters has caused the Debian Bug report #690342, regarding corosync: cannot set lrm parameters to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 690342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: corosync Version: 1.4.2-3 Severity: normal Dear Maintainer, I need to set the lrm max-children parameter when corosync/pacemaker starts as it is not persisted, but the corosync init script provides no way to do this. I have inserted the following code into /etc/init.d/corosync: maxwait=10 while [ $maxwait -gt 0 -a "`pidof lrmd`" = "" ] do echo waiting $maxwait maxwait=`expr $maxwait - 1` sleep 1 done /usr/sbin/lrmadmin -p max-children 16 at the end of the start function, but something a bit more flexible is required. Also the "wait 10 seconds for lrmd to appear" code might be a a bit fragile - it might still be possible for lrmd to have started but not be ready to accept lrmadmin requests so the script could race. I'm thinking something along the lines of LRM_MAX_CHILDREN= in /etc/default/corosync file and parsing that in the init script. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages corosync depends on: ii adduser 3.113+nmu2 ii libc6 2.13-32 ii libcfg4 1.4.2-3 ii libconfdb4 1.4.2-3 ii libcoroipcc4 1.4.2-3 ii libcoroipcs4 1.4.2-3 ii libcpg4 1.4.2-3 ii libevs4 1.4.2-3 ii liblogsys4 1.4.2-3 ii libpload4 1.4.2-3 ii libquorum4 1.4.2-3 ii libsam4 1.4.2-3 ii libtotem-pg4 1.4.2-3 ii libvotequorum4 1.4.2-3 ii lsb-base 4.1+Debian4 corosync recommends no packages. corosync suggests no packages. -- Configuration Files: /etc/corosync/corosync.conf changed [not included] /etc/default/corosync changed [not included] /etc/init.d/corosync changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---On Sat, 13 Oct 2012 09:37:37 +1100 root <james.har...@bendigoit.com.au> wrote: > I need to set the lrm max-children parameter when corosync/pacemaker > starts as it is not persisted, but the corosync init script provides > no way to do this. Almost five years later, this is accomplished by the node-action-limit cluster property, see man crmd. For a node-local override you can set the PCMK_node_action_limit variable in /etc/default/pacemaker. -- Feri
--- End Message ---
