[Pacemaker] MySQL after FailOver doesn't allow login
Hi List, since the newest update of corosync/pacemaker (running Debian Wheezy so versions are 1.1.7-1 for pacemaker and 1.4.2-3 for corosync) every time the services move to another host MySQL reports that everything works fine (using lsb-RA). But nobody is allowed to log in to MySQL until a restart of MySQL. Any ideas what could cause this? Thanks in advance. signature.asc Description: PGP signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Monitor and standby
Hi List, we have a two node cluster (test1-node1, test1-node2) with an additional quorum node (test1). On all nodes MySQL is running. test1-node1 and test1-node2 sharing the MySQL-Database via DRBD, so only one Node should run MySQL. On test1 there is a MySQL-Slave connected to test1-node1/test1-node2. test1 is always in Standby-Mode. The problem is now that the MySQL-Slave on test1 is shut down by crmd: Jul 3 12:05:12 test2 crmd: [5945]: info: te_rsc_command: Initiating action 22: monitor p_mysql_monitor_0 on test2 (local) Jul 3 12:05:14 test2 pengine: [5944]: ERROR: native_create_actions: Resource p_mysql (lsb::mysql) is active on 2 nodes attempting recovery Jul 3 12:05:14 test2 pengine: [5944]: notice: LogActions: Restart p_mysql#011(Started test2-node1) Jul 3 12:05:15 test2 crmd: [5945]: info: te_rsc_command: Initiating action 54: stop p_mysql_stop_0 on test2 (local) From my understanding this shouldn't happen as test1 was set to standby before: Jul 3 12:04:48 test2 cib: [5940]: info: cib:diff: + nvpair id=nodes-test2-standby name=standby value=on / How could we solve this? Thanks in advance. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Monitor and standby
On Wed, 3 Jul 2013 12:35:34 +0200 Lars Ellenberg lars.ellenb...@linbit.com wrote: Maybe you and pacemaker disagree about the meaning of standby? Hi Lars, obviously, yes. My understanding was that a standby node just adds it vote for quorum but isn't monitored at all. Thanks for clarify this. We solved it by renaming the Init-Script from mysql to mysqlslave on this node. Now the monitor complains about mysql isn't installed, but we can live with that. Thanks again, also to the other Lars and Andrey. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Monitor and standby
Am 03.07.2013 um 22:31 schrieb Lars Ellenberg lars.ellenb...@linbit.com: What purpose, exactly, is pacemaker supposed to serve in your setup? Hi Lars, running a two node Active/Passive-Cluster. As we don't have a STONITH-Device we decided to add a third node as quorum node into the setup and stop all services if we ever loose quorum. Unfortunately the third node has to run an MySQL-Slave which should never become active, but pacemaker of course has to manage MySQL on the two other nodes. It might not be the perfect Cluster setup you will find in any books but I can see nothing what's really wrong with it. I could think of a setup were MySQL will run with one master and two slaves and forbid the migration/promotion to the third node but I would like to share the Database-Files between the active and the passive node via DRBD as I expect it to be more reliable. The downside is that you has to wait until the MySQL-Server on the (no longer) passive node has been started in case of failover, but I can live with that. Of course, I'm very open to any comments or recommendations you might have. Best regards Denis Witt___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [OT] MySQL Replication
On Thu, 27 Jun 2013 21:59:29 +1000 Andrew Beekhof and...@beekhof.net wrote: I would _highly_ recommend 0.14 for use with any version of pacemaker that uses libqb. Hi Andrew, using the libqb-dev from Debian Sid I was able to compile the recent pacemaker version (from github) without errors. I didn't had time yet to check if this version will restart all my services after a restored quorum (see Recovery after lost quorum-Thread on this list), but I'll check that later. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] ERROR: Wrong stack o2cb
dlmc_fs_result: Invalid argument Jun 26 10:32:41 test4 ocfs2_controld: dlmcontrol connection died Jun 26 10:32:41 test4 ocfs2_controld: [3495]: notice: terminate_ais_connection: Disconnecting from Corosync Also in the above thread the 4th to last post from Andreas Kurz @Hastexo mentions this: This message was immediately followed by Wrong stack errors, and check the content of /sysfs/fs/ocfs2/loaded_cluster_plugins ... and if you have that configfile and it contains the value user this is a good sign you have started ocfs2/o2cb via init It says user but the init-scripts are still disabled and not used. Also it says user since I loaded the ocfs2_stack_user module, before that change it was ocfs2. I also tried reformatting the cluster-drive, now I'm able to mount it by hand, but corosync still fails. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [OT] MySQL Replication
On Wed, 26 Jun 2013 12:35:33 +1000 Andrew Beekhof and...@beekhof.net wrote: System is Debian Wheezy which means version 0.11.1-2 for libqb-dev. rpm errors on debian? I'm confused. When you run ./autogen.sh it tries to start an rpm command, this failed because I didn't had rpm installed. Anyway, I don't think is has anything to do with the compile error I occurred when I tried first. Which is the latest pacemaker version that is compatible with libqb 0.11? Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] ERROR: Wrong stack o2cb
On Wed, 26 Jun 2013 11:07:05 +0200 Lars Marowsky-Bree l...@suse.com wrote: This indicates you have a 'wrong stack' on disk still. You need to run mkfs.ocfs2/tunefs.ocfs while the o2cb cluster resource is running, or to set it to pcmk manually. Hi Lars, at the moment I assume I have a user-Stack on disk. /sys/fs/ocfs2/cluster_stack says pcmk. loaded_cluster_plugins says user. active_cluster_plugins is empty. I'm not sure if anyone has tested pcmk+ocfs2 on Debian for a while. Perhaps it's a good thing to check the debian cluster list if any exists? I'll have a look. I'd just delete /etc/ocfs2/cluster.conf. Anything that requires it indicates that it's not working properly with pacemaker ;-) The problem is that it won't start, so I can't write a new stack. Is there a way to start it manually using the pcmk stack? Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] ERROR: Wrong stack o2cb
On Wed, 26 Jun 2013 07:53:37 -0400 (EDT) jsmith jsm...@argotec.com wrote: You could start ocfs2 in the cluster just disable/remove the filesystem resource for now. Once pacemaker has started ocfs2 I believe you can do what you need? Hi Jake, Node test4: standby Online: [ test4-node1 test4-node2 ] Master/Slave Set: ms_drbd [drbd] Masters: [ test4-node1 test4-node2 ] Clone Set: clone_pingtest [pingtest] Started: [ test4-node1 test4-node2 ] Stopped: [ pingtest:2 ] Resource Group: grp_all sip(ocf::heartbeat:IPaddr2): Started test4-node1 apache (ocf::heartbeat:apache):Started test4-node1 Clone Set: cl_ocfs2mgmt [g_ocfs2mgmt] Started: [ test4-node2 test4-node1 ] Stopped: [ g_ocfs2mgmt:2 ] Clone Set: cl_fs_ocfs2 [fs_drbd] Started: [ test4-node2 test4-node1 ] Stopped: [ fs_drbd:2 ] Failed actions: p_o2cb:0_monitor_0 (node=test4, call=164, rc=5, status=complete): not installed p_controld:0_monitor_0 (node=test4, call=163, rc=5, status=complete): not installed drbd:0_monitor_0 (node=test4, call=159, rc=5, status=complete): not installed Thanks a lot! For the record, using DRBD/OCFS2 with Pacemaker/corosync on Debian Wheezy: apt-get install ocfs2-tools ocfs2-tools-pacemaker openais dlm-pcmk Configure your DRBD-Drives, make sure they are running (you can format them as ext4 to test if they mount well, but don't run them as dual-primary, yet). DON'T add /etc/ocfs2/cluster.conf update-rc.d ocfs2 disable update-rc.d o2cb disable Add ocfs2_stack_user to /etc/modules Then add all groups/clone sets/primitives, except fs_drbd related ones. When the cluster is running format the drive, so that the correct stack will be written. Then add the fs_drbd related stuff. Should work then. I'll check this procedure on a new machine and extend the list if necessary. Again, thanks a lot! Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [OT] MySQL Replication
On Wed, 26 Jun 2013 21:33:30 +1000
Andrew Beekhof and...@beekhof.net wrote:
When you run ./autogen.sh it tries to start an rpm command, this
failed because I didn't had rpm installed.
How did it fail?
That whole block if intended to be skipped if rpm isn't available.
if [ -e `which rpm` ]; then
echo Suggested invocation:
rpm --eval %{configure} | grep -v program-prefix
fi
./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force --warnings=no-portability -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: subdirectory libltdl not present
autoreconf: running: libtoolize --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: linking file `./ltmain.sh'
libtoolize: putting macros in `m4'.
libtoolize: linking file `m4/libtool.m4'
libtoolize: linking file `m4/ltoptions.m4'
libtoolize: linking file `m4/ltsugar.m4'
libtoolize: linking file `m4/ltversion.m4'
libtoolize: linking file `m4/lt~obsolete.m4'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac
and libtoolize: rerunning libtoolize, to keep the correct libtool
macros in-tree. autoreconf: running: /usr/bin/autoconf --force
--warnings=no-portability autoreconf: running: /usr/bin/autoheader
--force --warnings=no-portability autoreconf: running: automake
--add-missing --force-missing --warnings=no-portability
fencing/Makefile.am:91: `CFLAGS' is a user variable, you should not
override it; fencing/Makefile.am:91: use `AM_CFLAGS' instead.
lib/ais/Makefile.am:33: `CFLAGS' is a user variable, you should not
override it; lib/ais/Makefile.am:33: use `AM_CFLAGS' instead.
lib/common/Makefile.am:33: `CFLAGS' is a user variable, you should not
override it; lib/common/Makefile.am:33: use `AM_CFLAGS' instead.
autoreconf: Leaving directory `.' Now run ./configure
Now run configure with any arguments (eg. --prefix) specific to your
system Suggested invocation:
./autogen.sh: 38: ./autogen.sh: rpm: not found
Nothing serious...
Which is the latest pacemaker version that is compatible with libqb
0.11?
Ummm I don't know to be honest.
May it be possible that the version I tried to compile two or three
weeks ago was compatible, as I was able to run ./configure (by hand)
successfully?
Any reason not to upgrade it?
I'd like to stick with the debian repository version to receive
updates. For testing I might could use the version from sid which is
0.14.
Best regards
Denis Witt
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [OT] MySQL Replication
On Tue, 25 Jun 2013 10:39:30 +1000 Andrew Beekhof and...@beekhof.net wrote: @andrew: I know I owe you some informations about the Problem we discussed earlier on this list but at the moment i'm unable to compile the current Pacemaker Version, Sorry. Details? Hi Andrew, ./configure runs fine, but make didn't. I don't remember the exact error message and before I could run it again I have to solve my OCFS2-Problem. But I'll try again and post it here. Btw. This address wasn't subscribed to the list, you'll need to sign up before replying. Yes, sorry. The Mails was occidentally send from the wrong account (used my cell phone) later I resend it using the correct account but the From-Header wasn't replaced. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] ERROR: Wrong stack o2cb
On Tue, 25 Jun 2013 17:31:49 +0200 emmanuel segura emi2f...@gmail.com wrote: If you use ocfs with pacemaker, you don't need to configure ocfs in legacy mode using /etc/ocfs2/cluster.conf Hi, I just added the cluster.conf to be able to run tunefs.ocfs2. It doesn't matter if it is present or not, the error is the same. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] ERROR: Wrong stack o2cb
On Tue, 25 Jun 2013 11:37:15 -0400 (EDT) Jake Smith jsm...@argotec.com wrote: You probably already know but you're going to get failed not installed from test4 always unless you install the same packages there. Do you have logs from test4-node[1|2] that are generating the not installed for o2cb? The log below is just from test4 if I'm not mistaken which we expect doesn't have o2cb installed. Hi Jake, the log is from test4-node2, the machine was renamed and in the logs it still shows up as test4. It has o2cb installed. I can use the Drive fine on this machine when I start o2cb and ocfs2 by hand and mount the drive. A quick search for ERROR: Wrong stack o2cb indicates you may want to verify o2cb isn't starting on boot? But that's just a guess without the logs from the affected nodes. I've executed update-rc.d o2cb disable and update-rc.d ocfs2 disable. The services are stopped and pacemaker/corosync should handle everything. o2cb is still enabled in /etc/default/o2cb but the init-Script isn't executed on boot. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [OT] MySQL Replication
On Tue, 25 Jun 2013 17:12:15 +0200 Denis Witt denis.w...@concepts-and-training.de wrote: ./configure runs fine, but make didn't. I don't remember the exact error message and before I could run it again I have to solve my OCFS2-Problem. But I'll try again and post it here. Hi Andrew, last time I didn't had rpm installed and started ./configure and make by hand. (I didn't saw the rpm error message last time, it was very late.) Now ./autogen.sh runs fine, but my libqb is too old: configure: error: Version of libqb is too old: v0.13 or greater requried System is Debian Wheezy which means version 0.11.1-2 for libqb-dev. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] [OT] MySQL Replication
Hi List, might be offtopic but I'm sure there are may People on this List who had answered this question for themselfs. I have a MySQL Master/Master/Slave setup which is rather unreliable, so i'm asking myself if it might be better to use DRBD to keep the databases in Sync. Is this a resonable setup? What are you using and why? Thanks in advance. @andrew: I know I owe you some informations about the Problem we discussed earlier on this list but at the moment i'm unable to compile the current Pacemaker Version, Sorry. Best regards. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Troube mounting filesystem (DRBD)
. rc: 5): Error Jun 4 15:11:29 test3 crmd: [1762]: info: abort_transition_graph: match_graph_event:277 - Triggered transition abort (complete=0, tag=lrm_rsc_op, id=fs_drbd_last_failure_0, magic=0:5;9:8:7:8571cc98-5a20-4d51-b175-fe4db979fc09, cib=0.12.5) : Event failed Jun 4 15:11:29 test3 pengine: [1761]: notice: unpack_rsc_op: Preventing fs_drbd from re-starting on test3: operation monitor failed 'not installed' (rc=5) Jun 4 15:11:29 test3 pengine: [1761]: notice: unpack_rsc_op: Preventing fs_drbd from re-starting on test4: operation monitor failed 'not installed' (rc=5) Any help is really appreciated as I'm really lost at this point. If you need any more details I'm happy to provide them, but please keep in mind that I'm very new to pacemaker, so please provide me some kind of tip how to provide the requested information. Thanks a lot! Best regards, Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Troube mounting filesystem (DRBD)
On Tue, 4 Jun 2013 15:48:28 +0200 emmanuel segura emi2f...@gmail.com wrote: Did you tried to mount the filesystem manualy, without the cluster? Hi Emmanuel, yes, I did, works fine. Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Troube mounting filesystem (DRBD)
On Tue, 4 Jun 2013 15:38:57 +0200 Denis Witt denis.w...@concepts-and-training.de wrote: I'm trying to setup a Apache/DRBD cluster, but the Filesystem isn't mounted. crm status always tells me not installed as status for the filesystem primitive. Mounting the filesystem by hand works fine. Hi List, I got it fixed. fuser wasn't installed. I had installed fuse-utils but the correct package (for Debian) is psmisc. Sorry for the noise. ;) Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Recovery after lost quorum
Hi List, I have a cluster with two nodes running services, to make the Cluster more reliable I added a third node with no services (I didn't start pacemaker there, only corosync). I can't use STONITH in my setup so I choose no-quorum-policy=stop to avoid data corruption on my DRBD-Resources. The setup works fine, when two of my nodes disappear all services are stopped as expected. Unfortunately if the quorum has been restored the resources aren't restarted. Running crm_resource -P brings anything up, but of course it would be nice if this happens automatically. Is there any way to archive this? Thanks in advance. Best regards, Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Recovery after lost quorum
-lrm-refresh=1370360692 \ default-resource-stickiness=100 \ maintenance-mode=false Best regards, Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Recovery after lost quorum
Am 05.06.2013 um 02:15 schrieb Andrew Beekhof and...@beekhof.net: Jun 5 01:11:06 test4 pengine: [18625]: WARN: cluster_status: We do not have quorum - fencing and resource management disabled Jun 5 01:11:06 test4 pengine: [18625]: notice: LogActions: Start pingtest:0#011(test4 - blocked) Jun 5 01:11:06 test4 pengine: [18625]: notice: LogActions: Start drbd:0#011(test4 - blocked) Here's your reason. We didn't get quorum until: Jun 5 01:11:11 test4 crmd: [18626]: notice: ais_dispatch_message: Membership 128: quorum acquired Hi Andrew, I thought this means that there is a quorum. Anyway, crm status says: root@test4:~# crm status Last updated: Wed Jun 5 02:36:20 2013 Last change: Tue Jun 4 17:55:28 2013 via crm_attribute on backup3 Stack: openais Current DC: test4 - partition with quorum Version: 1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff 3 Nodes configured, 3 expected votes 8 Resources configured. Online: [ test4 backup3 ] OFFLINE: [ test3 ] But no resources are started, so I suspect there really is quorum. Anyway, I noticed, that, if I start pacemaker on the backup3-node the services are restarted, even if it sometime takes some time. So I might have to live with the not installed messages and start the backup3-node in standby-Mode as long no one comes up with a better solution. Maybe I'll fake the status of the monitors on this node and add some location-rules to avoid that resources will be moved to this node. Thanks for your help. Best regards, Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Recovery after lost quorum
-digest=e0cde594906f5ecf8fa72d58000e0c45/ /lrm_resource lrm_resource id=apache type=apache2 class=lsb lrm_rsc_op id=apache_last_failure_0 operation_key=apache_monitor_0 operation=monitor crm-debug-origin=build_active_RAs crm_feature_set=3.0.6 transition-key=7:81:7:ca6fd6dd-bf3c-4b75-9214-26e3a36b2f1c transition-magic=0:0;7:81:7:ca6fd6dd-bf3c-4b75-9214-26e3a36b2f1c call-id=138 rc-code=0 op-status=0 interval=0 op-digest=f2317cad3d54cec5d7d7aa7d0bf35cf8/ 117,118c129,130 lrm_rsc_op id=sip_monitor_1 operation_key=sip_monitor_1 operation=monitor crm-debug-origin=build_active_RAs crm_feature_set=3.0.6 transition-key=44:48:0:ca6fd6dd-bf3c-4b75-9214-26e3a36b2f1c transition-magic=0:0;44:48:0:ca6fd6dd-bf3c-4b75-9214-26e3a36b2f1c call-id=108 rc-code=0 op-status=0 interval=1 op-digest=f92644ce891641f5d8a4019b289dbbd0/ --- 120a133 122c135,146 --- /lrm_resource /lrm_resources /lrm /node_state node_state id=backup3 uname=backup3 crmd=online crm-debug-origin=do_update_resource ha=active in_ccm=true join=member expected=member shutdown=0 lrm id=backup3 lrm_resources lrm_resource id=drbd:0 type=drbd class=ocf provider=linbit /lrm_resource lrm_resource id=pingtest:0 type=ping class=ocf provider=pacemaker 125,127c149,152 --- /lrm_resource lrm_resource id=sip type=IPaddr2 class=ocf provider=heartbeat 130,132c155 --- 135a159,163 transient_attributes id=backup3 instance_attributes id=status-backup3 nvpair id=status-backup3-probe_complete name=probe_complete value=true/ /instance_attributes /transient_attributes 137d164 node_state id=backup3 uname=backup3 crmd=online crm-debug-origin=post_cache_update ha=active in_ccm=true join=member expected=member shutdown=0/ Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Recovery after lost quorum
Am 05.06.2013 um 04:04 schrieb Andrew Beekhof and...@beekhof.net: But no resources are started, so I suspect there really is quorum. Can you send me the output of cibadmin -Ql please? Perhaps those two resources are blocked for other reasons. It looks like you may have hit a bug in an older version (I just passed your config to a newer version of crm_simulate and it wanted to start resources). Is trying 1.1.9 or rc3 of 1.1.10 possible? Hi Andrew, I think so, yes. But it might take until the end of this week. At the moment I'm using pacemaker 1.1.7-1amd64 (debian wheezy) and corosync 1.4.2-3. Is it possible to run pacemaker 1.1.10 together with corosync 1.4.2.3? Best regards Denis Witt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
