Re: [ClusterLabs] Issue with Stonith Resource parameters

2016-03-09 Thread vija ar 
here is the config 



  

  







  


  
  


  

  
  
  


  
  
  
  
  

  
  

  
  
  


  
  
  
  
  

  
  

  


  


  
  

  


  
  


  


  


  


  

  



On Wed, Mar 9, 2016 at 1:25 PM, emmanuel segura  wrote:

> I think you should give the parameters to the stonith agent, anyway
> show your config.
>
> 2016-03-09 5:29 GMT+01:00 vija ar :
> > I have configured SLEHA cluster on cisco ucs boxes with ipmi configured,
> i
> > have tested IPMI using impitool, however ipmitool to function neatly i
> have
> > to pass parameter -y i.e.  along with username and password,
> >
> > however  to configure stonith there is no parameter in pacemaker to pass
> > ? and due to which stonith is failing
> >
> > can you please let me know if there is any way to add it or is this a
> bug?
> >
> > ***
> >
> >
> >
> > Mar  9 00:26:28 server02 stonith: external_status: 'ipmi status' failed
> with
> > rc 1
> > Mar  9 00:26:28 server02 stonith: external/ipmi device not accessible.
> > Mar  9 00:26:28 server02 stonith-ng[99114]:   notice: log_operation:
> > Operation 'monitor' [99200] for device 'STONITH-server02' returned: -201
> > (Generic Pacemaker error)
> > Mar  9 00:26:28 server02 stonith-ng[99114]:  warning: log_operation:
> > STONITH-server02:99200 [ Performing: stonith -t external/ipmi -S ]
> > Mar  9 00:26:28 server02 stonith-ng[99114]:  warning: log_operation:
> > STONITH-server02:99200 [ logd is not runningfailed:  1 ]
> > Mar  9 00:26:28 server02 crmd[99118]:error: process_lrm_event: LRM
> > operation STONITH-server02_start_0 (call=13, status=4, cib-update=13,
> > confirmed=true) Error
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch:
> Update
> > relayed from server01
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> > Sending flush op to all hosts for: fail-count-STONITH-server02 (INFINITY)
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update:
> Sent
> > update 35: fail-count-STONITH-server02=INFINITY
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch:
> Update
> > relayed from server01
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> > Sending flush op to all hosts for: last-failure-STONITH-server02
> > (1457463388)
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update:
> Sent
> > update 37: last-failure-STONITH-server02=1457463388
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch:
> Update
> > relayed from server01
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> > Sending flush op to all hosts for: fail-count-STONITH-server02 (INFINITY)
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update:
> Sent
> > update 39: fail-count-STONITH-server02=INFINITY
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch:
> Update
> > relayed from server01
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> > Sending flush op to all hosts for: last-failure-STONITH-server02
> > (1457463388)
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update:
> Sent
> > update 41: last-failure-STONITH-server02=1457463388
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch:
> Update
> > relayed from server01
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> > Sending flush op to all hosts for: fail-count-STONITH-server02 (INFINITY)
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update:
> Sent
> > update 43: fail-count-STONITH-server02=INFINITY
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch:
> Update
> > relayed from server01
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> > Sending flush op to all hosts for: last-failure-STONITH-server02
> > (1457463388)
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update:
> Sent
> > update 45: last-failure-STONITH-server02=1457463388
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch:
> Update
> > relayed from server01
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> > Sending flush op to all hosts for: fail-count-STONITH-server02 (INFINITY)
> > Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update:
> Sent
> > update 47: fail-count-STONITH-server02=INFINITY
> > Mar  9 00:26:28 server02 attrd[99116]:

Re: [ClusterLabs] Issue with Stonith Resource parameters

2016-03-08 Thread emmanuel segura 
I think you should give the parameters to the stonith agent, anyway
show your config.

2016-03-09 5:29 GMT+01:00 vija ar :
> I have configured SLEHA cluster on cisco ucs boxes with ipmi configured, i
> have tested IPMI using impitool, however ipmitool to function neatly i have
> to pass parameter -y i.e.  along with username and password,
>
> however  to configure stonith there is no parameter in pacemaker to pass
> ? and due to which stonith is failing
>
> can you please let me know if there is any way to add it or is this a bug?
>
> ***
>
>
>
> Mar  9 00:26:28 server02 stonith: external_status: 'ipmi status' failed with
> rc 1
> Mar  9 00:26:28 server02 stonith: external/ipmi device not accessible.
> Mar  9 00:26:28 server02 stonith-ng[99114]:   notice: log_operation:
> Operation 'monitor' [99200] for device 'STONITH-server02' returned: -201
> (Generic Pacemaker error)
> Mar  9 00:26:28 server02 stonith-ng[99114]:  warning: log_operation:
> STONITH-server02:99200 [ Performing: stonith -t external/ipmi -S ]
> Mar  9 00:26:28 server02 stonith-ng[99114]:  warning: log_operation:
> STONITH-server02:99200 [ logd is not runningfailed:  1 ]
> Mar  9 00:26:28 server02 crmd[99118]:error: process_lrm_event: LRM
> operation STONITH-server02_start_0 (call=13, status=4, cib-update=13,
> confirmed=true) Error
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch: Update
> relayed from server01
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> Sending flush op to all hosts for: fail-count-STONITH-server02 (INFINITY)
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update: Sent
> update 35: fail-count-STONITH-server02=INFINITY
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch: Update
> relayed from server01
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> Sending flush op to all hosts for: last-failure-STONITH-server02
> (1457463388)
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update: Sent
> update 37: last-failure-STONITH-server02=1457463388
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch: Update
> relayed from server01
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> Sending flush op to all hosts for: fail-count-STONITH-server02 (INFINITY)
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update: Sent
> update 39: fail-count-STONITH-server02=INFINITY
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch: Update
> relayed from server01
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> Sending flush op to all hosts for: last-failure-STONITH-server02
> (1457463388)
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update: Sent
> update 41: last-failure-STONITH-server02=1457463388
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch: Update
> relayed from server01
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> Sending flush op to all hosts for: fail-count-STONITH-server02 (INFINITY)
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update: Sent
> update 43: fail-count-STONITH-server02=INFINITY
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch: Update
> relayed from server01
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> Sending flush op to all hosts for: last-failure-STONITH-server02
> (1457463388)
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update: Sent
> update 45: last-failure-STONITH-server02=1457463388
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch: Update
> relayed from server01
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> Sending flush op to all hosts for: fail-count-STONITH-server02 (INFINITY)
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update: Sent
> update 47: fail-count-STONITH-server02=INFINITY
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_cs_dispatch: Update
> relayed from server01
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_trigger_update:
> Sending flush op to all hosts for: last-failure-STONITH-server02
> (1457463388)
> Mar  9 00:26:28 server02 attrd[99116]:   notice: attrd_perform_update: Sent
> update 49: last-failure-STONITH-server02=1457463388
> Mar  9 00:26:28 server02 crmd[99118]:   notice: process_lrm_event: LRM
> operation STONITH-server02_stop_0 (call=14, rc=0, cib-update=14,
> confirmed=true) ok
> Mar  9 00:26:28 server01 crmd[16809]:  warning: status_from_rc: Action 9
> (STONITH-server02_start_0) on server02 failed (target: 0 vs. rc: 1): Error
> Mar  9 00:26:28 server01 crmd[16809]:  warning: update_failcount: Updating
> failcount for STONITH-server02 on server02 after failed start: rc=1
> (update=INFINITY, time=1457463388)
> Mar  9 00:26:28 server01 crmd[16809]:  warning: update_failcount: Updating
>