On Tue, Nov 6, 2012 at 6:15 AM, King, Christopher
wrote:
> Hey all,
>
>
>
> Running pacemaker-1.1.5-5.9.11.1 (on SLES 11 SP1) we seem to be experiencing
> sporadic “lost” crm_resource commands. All indications are that the
> crm_resource command was issued correctly.
>
>
>
> Specifically, we have
1.0 dies on both nodes in cluster
Hi Angus,
I recompiled corosync with the changes you suggested in exec/main.c to generate
fdata when SIGBUS is triggered. Here 's the corresponding coredump and fdata
files:
http://sources.xes-inc.com/downloads/core.13027
http://sources.xes-inc.com/do
rresponding coredump and fdata
files:
http://sources.xes-inc.com/downloads/core.13027
http://sources.xes-inc.com/downloads/fdata.20121106
(gdb) thread apply all bt
Thread 1 (Thread 0x77fec700 (LWP 13027)):
#0 0x7775bda3 in qb_rb_chunk_alloc () from /usr/lib/libqb.so.0
#1 0x7
Hi Angus,
I recompiled corosync with the changes you suggested in exec/main.c to generate
fdata when SIGBUS is triggered. Here 's the corresponding coredump and fdata
files:
http://sources.xes-inc.com/downloads/core.13027
http://sources.xes-inc.com/downloads/fdata.20121106
(gdb) t
On 2012-11-06T19:30:20, "Gao,Yan" wrote:
Hi Yan,
thanks for proposing this.
Let me try to add -
The proposal has essentially three parts.
First, like Yan said, a new resource agent class so that we can wrap
around the Icinga/nagios plugins, provide meta-data, etc. This is quite
separate from
Hi,
Currently, we can manage VMs via the VM agents. But the services running
within VMs are not very easy to be monitored. If we could use
nagios/icinga probes from the host to the guest, that would allow us to
achieve this.
Lars, Dejan and I have been discussing on this for some time. There have
