Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-28 Thread Dejan Muhamedagic
Hi, On Thu, Jun 21, 2012 at 09:32:22AM +0200, Kadlecsik József wrote: > On Thu, 21 Jun 2012, Andrew Beekhof wrote: > > > Ah, I see you subsequently got some good advice from Phil. Glad to hear > > your problem is resolved. In general, when you run into "why isn't > > resource X starting? or st

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-21 Thread Kadlecsik József
On Thu, 21 Jun 2012, Andrew Beekhof wrote: > Ah, I see you subsequently got some good advice from Phil. Glad to hear > your problem is resolved. In general, when you run into "why isn't > resource X starting? or starting in the wrong place?" its always a good > idea to include a dump of the cu

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Andrew Beekhof
On Thu, Jun 21, 2012 at 12:30 PM, Andrew Beekhof wrote: > On Wed, Jun 20, 2012 at 11:51 PM, emmanuel segura wrote: >> Hello >> >> Why you say there is not error in the message > > Because it doesn't say "error" anywhere? > The logs below look completely normal for a node thats just joined the >

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Andrew Beekhof
On Wed, Jun 20, 2012 at 11:51 PM, emmanuel segura wrote: > Hello > > Why you say there is not error in the message Because it doesn't say "error" anywhere? The logs below look completely normal for a node thats just joined the cluster. > =

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Andrew Beekhof
On Thu, Jun 21, 2012 at 12:11 AM, emmanuel segura wrote: > I don't know but see the fail it's in the operation lx0_monitor_0, so i ask > to someone with more experience then me, if pacemaker does a monitor > operation before start? Always. We never start a resource unless we know for sure its not

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Kadlecsik József
On Wed, 20 Jun 2012, Phil Frost wrote: > On 06/20/2012 01:48 PM, Kadlecsik József wrote: > > Your crystal ball worked perfectly:-) - it was the memory utilization. > > I don't know if you already found it, but crm_simulate has option, "-U", > to display the utilization calculations, and if you

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Phil Frost
On 06/20/2012 01:48 PM, Kadlecsik József wrote: Your crystal ball worked perfectly:-) - it was the memory utilization. I don't know if you already found it, but crm_simulate has option, "-U", to display the utilization calculations, and if you crank up the verbosity (specify -V a couple time

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Kadlecsik József
On Wed, 20 Jun 2012, Phil Frost wrote: > Well, if the dot file you attached is the output of "crm_simulate -LS -D > pacemaker.dot", then this at least tells you that the policy engine, > given the current state of things, would like to do something else. > Normally when you run this you get an

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Kadlecsik József
On Wed, 20 Jun 2012, Kadlecsik József wrote: > On Wed, 20 Jun 2012, Phil Frost wrote: > > > Firstly, I'd try running "crm_simulate -LS -D pacemaker.dot", then viewing > > the generated pacemaker.dot with graphviz [1] (specifically "dot". It might > > also be helpful to pass pacemaker.dot through

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Phil Frost
On 06/20/2012 01:09 PM, Kadlecsik József wrote: On Wed, 20 Jun 2012, Phil Frost wrote: Firstly, I'd try running "crm_simulate -LS -D pacemaker.dot", then viewing the generated pacemaker.dot with graphviz [1] (specifically "dot". It might also be helpful to pass pacemaker.dot through "tred" firs

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Kadlecsik József
On Wed, 20 Jun 2012, Phil Frost wrote: > Firstly, I'd try running "crm_simulate -LS -D pacemaker.dot", then viewing > the generated pacemaker.dot with graphviz [1] (specifically "dot". It might > also be helpful to pass pacemaker.dot through "tred" first, to make it more > readable). This asks crm

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Kadlecsik József
On Wed, 20 Jun 2012, emmanuel segura wrote: > I readed the resource agent VirtualDomain and it's like that > > VirtualDomain_Start() { >     if VirtualDomain_Status; then >     ocf_log info "Virtual domain $DOMAIN_NAME already running." >   

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread emmanuel segura
Thanks Phil I readed the resource agent VirtualDomain and it's like that VirtualDomain_Start() { if VirtualDomain_Status; then ocf_log info "Virtual domain $DOMAIN_NAME already running." return $OCF_SUCCESS fi virsh

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Phil Frost
On 06/20/2012 10:11 AM, emmanuel segura wrote: I don't know but see the fail it's in the operation lx0_monitor_0, so i ask to someone with more experience then me, if pacemaker does a monitor operation before start? I'm just learning Pacemaker myself, so I could be wrong on some points. I don

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Kadlecsik József
On Wed, 20 Jun 2012, emmanuel segura wrote: > Why you say there is not error in the message > = > Jun 20 11:57:25 atlas4 lrmd: [17568]: info: operation monitor[35] on lx0 > for client 17571: pid 30179 exited with return code 7 > Jun 20 11:57:

Re: [Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread emmanuel segura
Hello Why you say there is not error in the message = Jun 20 11:57:25 atlas4 lrmd: [17568]: info: operation monitor[35] on lx0 for client 17571: pid 30179 exited with return code 7 Jun 20 11:57:25 atlas4 crmd: [17571]: debug: create_operation

[Pacemaker] Cannot start VirtualDomain resource after restart

2012-06-20 Thread Kadlecsik József
Hello, Somehow a VirtualDomain resource after a "crm resource restart", which did *not* start the resource but just stop, the resource cannot be started anymore. The most baffling is that I do not see an error message. The resource in question, named 'lx0', can be started directly via virsh/li