Re: [ClusterLabs] 'expected' node attribute missing

2017-10-29 Thread Sergey Korobitsin
7;expected_up' is the other one. Actually, I've found it trying to start the exporter. > For each node in your cluster, you should see a "" entry in > "crm_mon -X" output, and it should include "expected_up=true" or > "expected_up=false". --

[ClusterLabs] 'expected' node attribute missing

2017-10-27 Thread Sergey Korobitsin
Hello, I'm trying to use https://github.com/marcan/pacemaker-exporter, and it wants 'expected' node attribute from my crm_mon -X output, but it's missing. Is that because I'm using no-quorum-policy=ignore? -- Bright regards, Sergey Korobitsin, Chief Research Officer Arta

Re: [ClusterLabs] Debugging problems with resource timeout without any actions from cluster

2017-10-17 Thread Sergey Korobitsin
il=ignore lets you see failures in cluster status. > However, I'm not sure bypassing the monitor is the best solution to > this problem. If the problem is simply that your database monitor can > legitimately take longer than 20 seconds in normal operation, then > raise the timeou