On 06/11/2010 07:16 AM, Andrew Beekhof wrote:
> On Fri, Jun 11, 2010 at 4:03 PM, Colin wrote:
>> On Thu, Jun 10, 2010 at 12:22 AM, Steven Dake wrote:
>>>
>>> This version has the following changes:
>>> * Fixes defects in logsys which are crashing pacemaker installations.
>>
>> Hm, don't know whet
On 06/11/2010 09:00 AM, Andrew Beekhof wrote:
> This is a bit convoluted, but hang in there.
>
>
> So there is this bug:
>http://developerbugs.linux-foundation.org/show_bug.cgi?id=2379
>
> Essentially, to reproduce, you stop syslog but leave it enabled in
> corosync.conf.
> Here is the logging
This is a bit convoluted, but hang in there.
So there is this bug:
http://developerbugs.linux-foundation.org/show_bug.cgi?id=2379
Essentially, to reproduce, you stop syslog but leave it enabled in
corosync.conf.
Here is the logging section I used:
logging {
debug: on
fileline: off
to_s
On Fri, Jun 11, 2010 at 4:03 PM, Colin wrote:
> On Thu, Jun 10, 2010 at 12:22 AM, Steven Dake wrote:
>>
>> This version has the following changes:
>> * Fixes defects in logsys which are crashing pacemaker installations.
>
> Hm, don't know whether I did something wrong, but I just compiled
> coros
On Thu, Jun 10, 2010 at 12:22 AM, Steven Dake wrote:
>
> This version has the following changes:
> * Fixes defects in logsys which are crashing pacemaker installations.
Hm, don't know whether I did something wrong, but I just compiled
corosync 1.2.4, and then pacemaker 1.0.8, and the pair immedia
Hi Steven,
I report a result.
When I started in corosync -p, I succeed in a stop.
When I do not start with a p option, VM succeed in a stop when corosync operate
it with a mutex lock.
Best Regards,
Hideo Yamauchi.
--- renayama19661...@ybb.ne.jp wrote:
> Hi Steven,
>
> Thank you for comment
