[Pacemaker] MySQL after FailOver doesn't allow login

2014-05-09 Thread Denis Witt
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 resta

Re: [Pacemaker] Monitor and standby

2013-07-03 Thread Denis Witt
Am 03.07.2013 um 22:31 schrieb Lars Ellenberg : > 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

Re: [Pacemaker] Monitor and standby

2013-07-03 Thread Denis Witt
. 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

[Pacemaker] Monitor and standby

2013-07-03 Thread Denis Witt
) >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: + How could we solve this? Thanks in advance. Best regards Denis Witt ___ Pacemaker mailing list: P

Re: [Pacemaker] [OT] MySQL Replication

2013-06-27 Thread Denis Witt
'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: Pacemake

Re: [Pacemaker] ERROR: Wrong stack o2cb

2013-06-26 Thread Denis Witt
ets, but I get used to it. :) > > Thanks a lot! > Glad it helped! That's what we're all here for And you all are doing a very good job here. This list is remarkably helpful and friendly. Best regards Denis Witt ___ Pacemaker m

Re: [Pacemaker] [OT] MySQL Replication

2013-06-26 Thread Denis Witt
pile 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 W

Re: [Pacemaker] ERROR: Wrong stack o2cb

2013-06-26 Thread Denis Witt
;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: ht

Re: [Pacemaker] ERROR: Wrong stack o2cb

2013-06-26 Thread Denis Witt
t; 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

Re: [Pacemaker] [OT] MySQL Replication

2013-06-26 Thread Denis Witt
alled. 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: Pacemak

Re: [Pacemaker] ERROR: Wrong stack o2cb

2013-06-26 Thread Denis Witt
aded_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 modu

Re: [Pacemaker] [OT] MySQL Replication

2013-06-25 Thread Denis Witt
On Tue, 25 Jun 2013 17:12:15 +0200 Denis Witt 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

Re: [Pacemaker] ERROR: Wrong stack o2cb

2013-06-25 Thread Denis Witt
ted "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 ___

Re: [Pacemaker] ERROR: Wrong stack o2cb

2013-06-25 Thread Denis Witt
ot, 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.clu

[Pacemaker] ERROR: Wrong stack o2cb

2013-06-25 Thread Denis Witt
:p_o2cb:0 probe[23] (pid 467) Jun 25 17:06:52 test4 lrmd: [28587]: info: RA output: (p_controld:0:probe:stderr) dlm_controld.pcmk: no process found Jun 25 17:06:52 test4 lrmd: [28587]: info: operation monitor[22] on p_controld:0 for client 28590: pid 466 exited with return code 7

Re: [Pacemaker] [OT] MySQL Replication

2013-06-25 Thread Denis Witt
re 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@o

[Pacemaker] [OT] MySQL Replication

2013-06-24 Thread Denis Witt
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 resona

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
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.clu

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
="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="f2317cad3d54c

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
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 Proje

Re: [Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
test location loc_all_on_best_ping grp_all \ rule $id="loc_all_on_best_ping-rule" -inf: not_defined pingd or pingd lt 1000 colocation coloc_all_on_drbd inf: grp_all ms_drbd:Master order order_all_after_drbd inf: ms_drbd:promote grp_all:start property $id="cib-bootstrap

[Pacemaker] Recovery after lost quorum

2013-06-04 Thread Denis Witt
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.clus

Re: [Pacemaker] Troube mounting filesystem (DRBD)

2013-06-04 Thread Denis Witt
On Tue, 4 Jun 2013 15:38:57 +0200 Denis Witt 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

Re: [Pacemaker] Troube mounting filesystem (DRBD)

2013-06-04 Thread Denis Witt
On Tue, 4 Jun 2013 15:48:28 +0200 emmanuel segura 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.

[Pacemaker] Troube mounting filesystem (DRBD)

2013-06-04 Thread Denis Witt
, 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_r