On 2015-01-04T19:49:58, Oriol Mula-Valls omv.li...@gmail.com wrote:
I have a two node system with SLES 11 SP3 (pacemaker-1.1.9-0.19.102,
corosync-1.4.5-0.18.15, sbd-1.1-0.13.153). Since desember we started to
have several reboots of the system due to SBD; 22nd, 24th and 26th. Last
reboot
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
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)
They all look sane to me. Please proceed with a pull request :-)
We should probably start thinking about .13 (or .14 for the superstitious),
there have been quite a few important patches arrive since .12 was released.
On 10 Dec 2014, at 1:33 am, Lars Ellenberg lars.ellenb...@linbit.com
On 5 Dec 2014, at 4:16 am, steve st...@unliketea.com wrote:
Good Afternoon,
I am having loads of trouble with pacemaker/corosync/postgres. Defining the
symptoms is rather difficult. The primary being that postgres starts as
slave on both nodes. I have tested the pgsqlRA
Hello,
This is a tentative schedule for resource-agents v3.9.6:
3.9.6-rc1: January 16.
3.9.6: January 23.
Let's hope that this time the schedule will work out ;-)
I modified the corresponding milestones at
https://github.com/ClusterLabs/resource-agents
If there's anything you think should be
And there is no indication this is being called?
On 7 Jan 2015, at 6:21 pm, Marco Querci mquerc...@gmail.com wrote:
#!/bin/bash
monitorfile=/tmp/clustermonitor.html
hostname=$(hostname)
echo Cluster state changes detected | mail -r $hostname@domain -s
Cluster Monitor -a $monitorfile
On 8 Jan 2015, at 1:31 pm, Andrew Beekhof and...@beekhof.net wrote:
And there is no indication this is being called?
Doh. I know this one... you're actually using 1.1.12-rc3.
You need this patch which landed after 1.1.12 shipped:
https://github.com/beekhof/pacemaker/commit/3df6aff
On
Sorry, my fault. Forgot to include /usr/lib/lcrso/pacemaker.lcrso in my deb
package.
--
Best regards,
Sergey Arlashin
On Jan 7, 2015, at 2:18 PM, Sergey Arlashin sergeyarl.maill...@gmail.com
wrote:
After installing 1.1.12 on one of my nodes in staging environment I see the
following
