Re: [Pacemaker] crm_mon and last-failure timestamp not always present

2015-01-07 Thread Gianluca Cecchi
On Wed, Jan 7, 2015 at 10:21 AM, Gianluca Cecchi gianluca.cec...@gmail.com
wrote:
[snip]



 Is there any parameter inside configuration of cluster and/or resources
 that could control if last-failure information will be shown or not?



Ok, solved.
On the cluster where timestamp is shown the resource has the meta parameter

meta failure-timeout=2min

On the other cluster there isn't this kind of parameter.
I also tried to dynamically put and omit the parameter on a resource with 1
failure and the timestamp is shown or not, depending on the setting.
I think it is all related to this page features:
http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-failure-migration.html

Gianluca
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [Pacemaker] crm_mon and last-failure timestamp not always present

2015-01-07 Thread emmanuel segura
if you want to see the time stamp of your resource operations without
failure-timeout, because is used for reset the failcount, you can use
the -t option:

crm_mon -Arf1t

..
..

Operations:
* Node node01:
   sambaip: migration-threshold=100
+ (30) start: rc=0 (ok)
   Dummy1: migration-threshold=100 fail-count=2
+ (67) start: last-rc-change='Wed Jan  7 13:53:41 2015'
last-run='Wed Jan  7 13:53:41 2015' exec-time=20ms queue-time=0ms rc=0
(ok)
+ (68) monitor: interval=3ms last-rc-change='Wed Jan  7
13:53:41 2015' exec-time=20ms queue-time=0ms rc=0 (ok)
   Dummy2: migration-threshold=100
+ (69) start: last-rc-change='Wed Jan  7 13:53:41 2015'
last-run='Wed Jan  7 13:53:41 2015' exec-time=20ms queue-time=0ms rc=0
(ok)
+ (70) monitor: interval=240ms last-rc-change='Wed Jan  7
13:53:41 2015' exec-time=20ms queue-time=0ms rc=0 (ok)
   Dummy3: migration-threshold=100
+ (71) start: last-rc-change='Wed Jan  7 13:53:41 2015'
last-run='Wed Jan  7 13:53:41 2015' exec-time=20ms queue-time=0ms rc=0
(ok)
+ (72) monitor: interval=240ms last-rc-change='Wed Jan  7
13:53:41 2015' exec-time=10ms queue-time=0ms rc=0 (ok)

2015-01-07 12:14 GMT+01:00 Gianluca Cecchi gianluca.cec...@gmail.com:
 On Wed, Jan 7, 2015 at 10:21 AM, Gianluca Cecchi gianluca.cec...@gmail.com
 wrote:
 [snip]



 Is there any parameter inside configuration of cluster and/or resources
 that could control if last-failure information will be shown or not?



 Ok, solved.
 On the cluster where timestamp is shown the resource has the meta parameter

 meta failure-timeout=2min

 On the other cluster there isn't this kind of parameter.
 I also tried to dynamically put and omit the parameter on a resource with 1
 failure and the timestamp is shown or not, depending on the setting.
 I think it is all related to this page features:
 http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-failure-migration.html

 Gianluca


 ___
 Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
 http://oss.clusterlabs.org/mailman/listinfo/pacemaker

 Project Home: http://www.clusterlabs.org
 Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
 Bugs: http://bugs.clusterlabs.org




-- 
esta es mi vida e me la vivo hasta que dios quiera

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org