Re: [Linux-cluster] Not restarting max_restart times before relocating failed service

2012-10-31 Thread emmanuel segura
Hello Maybe you missing recovery=restart in your services 2012/10/31 Parvez Shaikh parvez.h.sha...@gmail.com Hi Digimer, cman_tool version gives following - 6.2.0 config 22 Cluster.conf - ?xml version=1.0? cluster alias=PARVEZ config_version=22 name=PARVEZ clusternodes

Re: [Linux-cluster] Not restarting max_restart times before relocating failed service

2012-10-31 Thread Parvez Shaikh
Hi, I am using recovery=restart as evident from earlier attached cluster.conf Thanks, Parvez On Wed, Oct 31, 2012 at 2:53 PM, emmanuel segura emi2f...@gmail.com wrote: Hello Maybe you missing recovery=restart in your services 2012/10/31 Parvez Shaikh parvez.h.sha...@gmail.com Hi

[Linux-cluster] Not restarting max_restart times before relocating failed service

2012-10-30 Thread Parvez Shaikh
Hi experts, I have defined a service as follows in cluster.conf - service autostart=0 domain=mydomain exclusive=0 max_restarts=5 name=mgmt recovery=restart script ref=myHaAgent/ ip ref=192.168.51.51/ /service I

Re: [Linux-cluster] Not restarting max_restart times before relocating failed service

2012-10-30 Thread Digimer
On 10/30/2012 01:54 AM, Parvez Shaikh wrote: Hi experts, I have defined a service as follows in cluster.conf - service autostart=0 domain=mydomain exclusive=0 max_restarts=5 name=mgmt recovery=restart script ref=myHaAgent/

Re: [Linux-cluster] Not restarting max_restart times before relocating failed service

2012-10-30 Thread Parvez Shaikh
Hi Digimer, cman_tool version gives following - 6.2.0 config 22 Cluster.conf - ?xml version=1.0? cluster alias=PARVEZ config_version=22 name=PARVEZ clusternodes clusternode name=myblade2 nodeid=2 votes=1 fence

Re: [Linux-cluster] Not restarting max_restart times before relocating failed service

2012-10-30 Thread Digimer
What does 'rpm -q cman' return? This looks very odd; fencedevice agent=fence_bladecenter ipaddr=mm-1.mydomain.com http://mm-1.mydomain.com Please remove this for now; fence_daemon clean_start=1 post_fail_delay=0 post_join_delay=0/ In general, you don't want to assume a clean start. It's