Re: [Pacemaker] meta failure-timeout: crashed resource is assumed to be Started?

2014-10-28 Thread Carsten Otto
FYI: I cannot reproduce this problem right now. I guess I made a mistake analyzing the logs. -- andrena objects ag Büro Frankfurt Clemensstr. 8 60487 Frankfurt Tel: +49 (0) 69 977 860 38 Fax: +49 (0) 69 977 860 39 http://www.andrena.de Vorstand: Hagen Buchwald, Matthias Grund, Dr. Dieter Kuhn Au

Re: [Pacemaker] meta failure-timeout: crashed resource is assumed to be Started?

2014-10-23 Thread Carsten Otto
Dear all, I did not get any response so far. Could you please find the time and tell me how the "meta failure-timeout" is supposed to work, in combination with monitor operations? Thanks, Carsten On Thu, Oct 16, 2014 at 05:06:41PM +0200, Carsten Otto wrote: > Dear all, > >

[Pacemaker] meta failure-timeout: crashed resource is assumed to be Started?

2014-10-16 Thread Carsten Otto
Dear all, I configured meta failure-timeout=60sec on all of my resources. For the sake of simplicity, assume I have a group of two resources FIRST and SECOND (where SECOND is started after FIRST, surprise!). If now FIRST crashes, I see a failure, as expected. I also see that SECOND is stopped, as

Re: [Pacemaker] Pacemaker on system with disk failure

2014-10-01 Thread Carsten Otto
Dear Andrew, please find the time to have a look at this. Thank you, Carsten -- andrena objects ag Büro Frankfurt Clemensstr. 8 60487 Frankfurt Tel: +49 (0) 69 977 860 38 Fax: +49 (0) 69 977 860 39 http://www.andrena.de Vorstand: Hagen Buchwald, Matthias Grund, Dr. Dieter Kuhn Aufsichtsratsvor

Re: [Pacemaker] Pacemaker on system with disk failure

2014-09-25 Thread Carsten Otto
The web archive seems to not like my shell script, so here it is again. #!/bin/ksh

Re: [Pacemaker] Pacemaker on system with disk failure

2014-09-25 Thread Carsten Otto
Dear John, On Thu, Sep 25, 2014 at 10:03:27AM -0400, John Lauro wrote: > One of the reasons I like ksh is that true, echo, and sleep (among > many others) are all builtin, so you don't need those commands on the > filesystem, so the script is less likely to fail if the filesystem > fails... that

Re: [Pacemaker] Pacemaker on system with disk failure

2014-09-25 Thread Carsten Otto
Dear John, thank you for confirming the problem. Your script might do the job, although I see that some files like echo/true/sleep/cron might not be available - but I can really work with that. Best regards, Carsten -- andrena objects ag Büro Frankfurt Clemensstr. 8 60487 Frankfurt Tel: +49 (0)

Re: [Pacemaker] Pacemaker on system with disk failure

2014-09-25 Thread Carsten Otto
On Tue, Sep 23, 2014 at 10:14:33AM -0400, Digimer wrote: > You don't have real fencing configured, by the looks of it. Without > real, working fencing, recovery can be unpredictable. Can you set > that up and see if the problem goes away? I now have real fencing which also is fully automatic, non-

Re: [Pacemaker] Pacemaker on system with disk failure

2014-09-23 Thread Carsten Otto
On Tue, Sep 23, 2014 at 10:14:33AM -0400, Digimer wrote: > You don't have real fencing configured, by the looks of it. Without > real, working fencing, recovery can be unpredictable. Can you set that > up and see if the problem goes away? I do have real, working fencing - although manual for testi

Re: [Pacemaker] Pacemaker on system with disk failure

2014-09-23 Thread Carsten Otto
On Tue, Sep 23, 2014 at 09:50:12AM -0400, Digimer wrote: > Can you share your pacemaker and drbd configurations please? drbd.d/global_comman.conf: global { usage-count no; } common { protocol C; handlers { split-brain "/usr/lib/drbd/notify-split-brain.sh root"; out-of-sync "/usr/lib

Re: [Pacemaker] Pacemaker on system with disk failure

2014-09-23 Thread Carsten Otto
On Tue, Sep 23, 2014 at 03:39:45PM +0200, Carsten Otto wrote: >While this demote operation obviously should not be confirmed, I also >strongly believe that running the stop operations of the standard ^^^ "disbelieve" >resources works without having acc

[Pacemaker] Pacemaker on system with disk failure

2014-09-23 Thread Carsten Otto
Hello, I run Corosync + Pacemaker + DRBD in a two node cluster, where all resources are part of a group/colocated with DRBD (DRBD + virtual IP + filesystem + ...). To test my configuration, I currently have two nodes with only a single disk drive. This drive is the only LVM physical drive in a LVM