Re: [ClusterLabs] stonith-ng - performing action 'monitor' timed out with signal 15
On Tue, 2019-09-03 at 10:09 +0200, Marco Marino wrote: > Hi, I have a problem with fencing on a two node cluster. It seems > that randomly the cluster cannot complete monitor operation for fence > devices. In log I see: > crmd[8206]: error: Result of monitor operation for fence-node2 on > ld2.mydomain.it: Timed Out > As attachment there is > - /var/log/messages for node1 (only the important part) > - /var/log/messages for node2 (only the important part) <-- Problem > starts here > - pcs status > - pcs stonith show (for both fence devices) > > I think it could be a timeout problem, so how can I see timeout value > for monitor operation in stonith devices? > Please, someone can help me with this problem? > Furthermore, how can I fix the state of fence devices without > downtime? > > Thank you How to investigate depends on whether this is an occasional monitor failure, or happens every time the device start is attempted. From the status you attached, I'm guessing it's at start. In that case, my next step (since you've already verified ipmitool works directly) would be to run the fence agent manually using the same arguments used in the cluster configuration. Check the man page for the fence agent, looking at the section for "Stdin Parameters". These are what's used in the cluster configuration, so make a note of what values you've configured. Then run the fence agent like this: echo -e "action=status\nPARAMETER=VALUE\nPARAMETER=VALUE\n..." | /path/to/agent where PARAMETER=VALUE entries are what you have configured in the cluster. If the problem isn't obvious from that, you can try adding a debug_file parameter. -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Pacemaker 1.1.12 does not compile with CMAN Stack.
On 16/09/19 12:01 +, Somanath Jeeva wrote: > Thanks for your extended support and advise. I would like to give > some background information about my exercise, which will give some > fair idea to you folks. > > We are planning to use pacemaker + Corosync + CMAN stack in RHEL 6.5 > OS. For the same, we are trying to collect the source from > Clusterlab. If my memory serves me correctly and if the actual hard limitation is usage of RHEL 6.5, pacemaker option would still be available for you to consier... > Initially we got the Pacemaker and Corosync Source successfully from > Clusterlab and we were unable to fetch the source for CMAN from > Cluster lab. ClusterLabs is currently a loose "makers association". I am not even sure what you call "getting corosync source from ClusterLabs", since corosync project is even more independent, see for instance a separate top-level GitHub associating naame (https://github.com/corosync/corosync). > As you suggested, We already tried to use the latest set of > Pacemaker with its prerequisites (Corosync) on top of RHEL 6.5, but > it fails due to dependencies of RHEL 7.x Components (Systemd). This may be a matter of poor understanding of how to pre-arrange the actual compilation of the components. It might deserve more room in README/INSTALL kind of top-level documents, but the habitual approach working across any SW with build system backed with autotools (autoconf, automake, ...) is to run these exploratory steps: 1. ./autogen.sh (sometimes also ./bootstrap.sh, etc., sometimes, for instance, mere "autoreconf -if" is suggested instead) 2. ./configure --help The latter will overwhelm you on the first contact, but then, when you don't give up and try to understand your options with the project at hand, you'll realize that you can change quite a lot about the final products of the compilation, and indirectly about the prerequisites needed to get there. In case of pacemaker, you can, for instance, spot: > --enable-systemd Enable support for managing resources via systemd [try] It follows then to disble this support + dependencies by force, you'll just need to invoke the configure script as: ./configure --disable-systemd > So we are requesting you to provide the below information. > > Is it possible for me to get the source code for CMAN from Cluster > lab ??? (since we are planning to use it for our production purpose, > that's why we don't want to go with Red hat sites (even for Publicly > available)). > Somanath, it's basic to understand some facts first, since blind fixation on ClusterLabs group and, conversely, blank refusal of Red Hat as a vendor (sigh) won't lead anyway, I am afraid: 1. CMAN pre-exists ClusterLabs establishment by multiple years 2. CMAN used to be, more or less, single vendor show, and this vendor was, surprise surprise, Red Hat 3. from 2., it follows that the only authoritative sources of CMAN ever were associated with this vendor -- you want it? better to grab it from there ... or from trustable enough and associated still mirror (currently hosted at pagure.io, see below) So, take it or leave it, the links I provided for you (below) still stand, don't expect any ClusterLabs rembranding-by-force of what practically amounts to a dead project now. Thanks for understanding. And keep in mind, if I were you, I'd skip CMAN and RHEL 6 today. > -Original Message- > From: Jan Pokorný > Sent: Friday, August 30, 2019 20:15 > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] Pacemaker 1.1.12 does not compile with CMAN Stack. > > [...] > > For CMAN in particular, look here: > > https://pagure.io/linux-cluster/cluster/blob/STABLE32/f/cman > https://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHS/SRPMS/cluster-3.0.12.1-73.el6.src.rpm > > > [...] > -- Jan (Poki) pgpjkHb093_qS.pgp Description: PGP signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Pacemaker 1.1.12 does not compile with CMAN Stack.
Somanath, Hi , Thanks for your extended support and advise. I would like to give some background information about my exercise, which will give some fair idea to you folks. We are planning to use pacemaker + Corosync + CMAN stack in RHEL 6.5 OS. For the same, we are trying to collect the source from Clusterlab. Are you really sure 6.5? AFAIK 6.5 is no longer supported. Initially we got the Pacemaker and Corosync Source successfully from Clusterlab and we were unable to fetch the source for CMAN from Cluster lab. As you suggested, We already tried to use the latest set of Pacemaker with its prerequisites (Corosync) on top of RHEL 6.5, but it fails due to dependencies of RHEL 7.x Components (Systemd). At least corosync 2.x should work just fine on RHEL 6 and there is no hard dependency on systemd. So we are requesting you to provide the below information. Is it possible for me to get the source code for CMAN from Cluster lab ??? (since we are planning to use it for our production purpose, that's why we don't want to go with Red hat sites (even for Publicly available)). Take following comment as just my 0.02$. Honestly I would go with what distribution provides. RHEL 6 is still supported and what is there is tested by QE/other customers in production. If you decide to go with newer versions on top of old distro you are on your own and you may face weird bugs which nobody will really care about much. Regards, Honza With Regards Somanath Thilak J -Original Message- From: Jan Pokorný Sent: Friday, August 30, 2019 20:15 To: users@clusterlabs.org Subject: Re: [ClusterLabs] Pacemaker 1.1.12 does not compile with CMAN Stack. On 30/08/19 13:03 +, Somanath Jeeva wrote: In Pacemaker 1.1.12 version try to compile with CMAN Stack, midly put, it's like trying to run with dinosaurs; that version of pacemaker together with that effectively superseded bundle of other components will hardly receive any attention in 2019. But let's assume there's a reason. but we are unable to achieve that . Source taken path : https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-1.1.12 After Extracting, we installed required dependencies as per README.markdown, ## Installing from source $ ./autogen.sh $ ./configure $ make $ sudo make install After performing above task, we are unable to start pacemaker due to cman stack is unrecognized service. Well, pacemaker alone won't magically bootstrap these other prerequisites, you need to take an effort of grabbing them as well. For CMAN in particular, look here: https://pagure.io/linux-cluster/cluster/blob/STABLE32/f/cman https://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHS/SRPMS/cluster-3.0.12.1-73.el6.src.rpm # service pacemaker status pacemakerd dead but pid file exists #service cman status cman: unrecognized service Easy, no /etc/init.d/cman around, for the mentioned reason. Still, I am not sure how far you'll get, sounds like an uphill battle. Settling with the rather recent state of development may avoid significant chunks of troubles, incl. those that were only fixed in later versions of pacemaker. Please find the ./configure screenshot of the system: pacemaker configuration: Version = 1.1.12 (Build: 561c4cfda1) Features = libqb-logging libqb-ipc lha-fencing nagios corosync-plugin cman acls Prefix = /usr Executables = /usr/sbin Man pages= /usr/share/man Libraries= /usr/lib64 Header files = /usr/include Arch-independent files = /usr/share State information= /var System configuration = /etc Corosync Plugins = /usr/libexec/lcrso Use system LTDL = yes HA group name= haclient HA user name = hacluster CFLAGS = -g -O2 -I/usr/include -I/usr/include/heartbeat -ggdb -fgnu89-inline -fstack-protector-all -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wdeclaration-after-statement -Wendif-labels -Wfloat-equal -Wformat=2 -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Wno-long-long -Wno-strict-aliasing -Wunused-but-set-variable -Wpointer-arith -Wwrite-strings -Werror Libraries= -lgnutls -lqb -lplumb -lpils -lqb -lbz2 -lxslt -lxml2 -lc -luuid -lpam -lrt -ldl -lglib-2.0 -lltdl -lqb -ldl -lrt -lpthread Stack Libraries = -lcoroipcc -lcpg -lcfg -lconfdb -lcman -lfenced Is there anything I am missing in the configure, to get the cman stack. I think having "cman" enumerated amongst features might be enough, but once you'll get past the "cman: unrecognized service" phase, you shall see. Hope this helps. -- Jan (Poki) ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home:
Re: [ClusterLabs] Pacemaker 1.1.12 does not compile with CMAN Stack.
Hi , Thanks for your extended support and advise. I would like to give some background information about my exercise, which will give some fair idea to you folks. We are planning to use pacemaker + Corosync + CMAN stack in RHEL 6.5 OS. For the same, we are trying to collect the source from Clusterlab. Initially we got the Pacemaker and Corosync Source successfully from Clusterlab and we were unable to fetch the source for CMAN from Cluster lab. As you suggested, We already tried to use the latest set of Pacemaker with its prerequisites (Corosync) on top of RHEL 6.5, but it fails due to dependencies of RHEL 7.x Components (Systemd). So we are requesting you to provide the below information. Is it possible for me to get the source code for CMAN from Cluster lab ??? (since we are planning to use it for our production purpose, that's why we don't want to go with Red hat sites (even for Publicly available)). With Regards Somanath Thilak J -Original Message- From: Jan Pokorný Sent: Friday, August 30, 2019 20:15 To: users@clusterlabs.org Subject: Re: [ClusterLabs] Pacemaker 1.1.12 does not compile with CMAN Stack. On 30/08/19 13:03 +, Somanath Jeeva wrote: > In Pacemaker 1.1.12 version try to compile with CMAN Stack, midly put, it's like trying to run with dinosaurs; that version of pacemaker together with that effectively superseded bundle of other components will hardly receive any attention in 2019. But let's assume there's a reason. > but we are unable to achieve that . > > Source taken path : > https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-1.1.12 > > After Extracting, we installed required dependencies as per > README.markdown, > > ## Installing from source > > $ ./autogen.sh > $ ./configure > $ make > $ sudo make install > > After performing above task, we are unable to start pacemaker due to > cman stack is unrecognized service. Well, pacemaker alone won't magically bootstrap these other prerequisites, you need to take an effort of grabbing them as well. For CMAN in particular, look here: https://pagure.io/linux-cluster/cluster/blob/STABLE32/f/cman https://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHS/SRPMS/cluster-3.0.12.1-73.el6.src.rpm > # service pacemaker status > pacemakerd dead but pid file exists > #service cman status > cman: unrecognized service Easy, no /etc/init.d/cman around, for the mentioned reason. Still, I am not sure how far you'll get, sounds like an uphill battle. Settling with the rather recent state of development may avoid significant chunks of troubles, incl. those that were only fixed in later versions of pacemaker. > Please find the ./configure screenshot of the system: > > pacemaker configuration: > Version = 1.1.12 (Build: 561c4cfda1) > Features = libqb-logging libqb-ipc lha-fencing nagios > corosync-plugin cman acls > > Prefix = /usr > Executables = /usr/sbin > Man pages= /usr/share/man > Libraries= /usr/lib64 > Header files = /usr/include > Arch-independent files = /usr/share > State information= /var > System configuration = /etc > Corosync Plugins = /usr/libexec/lcrso > > Use system LTDL = yes > > HA group name= haclient > HA user name = hacluster > > CFLAGS = -g -O2 -I/usr/include -I/usr/include/heartbeat >-ggdb -fgnu89-inline -fstack-protector-all -Wall -Waggregate-return > -Wbad-function-cast -Wcast-align -Wdeclaration-after-statement -Wendif-labels > -Wfloat-equal -Wformat=2 -Wmissing-prototypes -Wmissing-declarations > -Wnested-externs -Wno-long-long -Wno-strict-aliasing > -Wunused-but-set-variable -Wpointer-arith -Wwrite-strings -Werror > Libraries= -lgnutls -lqb -lplumb -lpils -lqb -lbz2 -lxslt > -lxml2 -lc -luuid -lpam -lrt -ldl -lglib-2.0 -lltdl -lqb -ldl -lrt > -lpthread > Stack Libraries = -lcoroipcc -lcpg -lcfg -lconfdb -lcman > -lfenced > > > Is there anything I am missing in the configure, to get the cman > stack. I think having "cman" enumerated amongst features might be enough, but once you'll get past the "cman: unrecognized service" phase, you shall see. Hope this helps. -- Jan (Poki) ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
