On Tue, May 5, 2009 at 6:16 PM, Pavel Georgiev wrote:
> When can we expect a fix for this?
You can either grab the latest source, or wait for the next
maintenance release later this month.
I try to keep this up-to-date:
http://www.clusterlabs.org/wiki/Releases#Supported_Release_Series
>
>
> O
When can we expect a fix for this?
On May 4, 2009, at 10:17 AM, Andrew Beekhof wrote:
Never mind, ignore all that. I see the problem.
What I dont understand is why no-one else has been seeing this.
Anyway, it really is a logging issue that you can safely ignore.
On Mon, May 4, 2009 at 9:15 A
: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] Pacemaker 1.0.3 errors
Never mind, ignore all that. I see the problem.
What I dont understand is why no-one else has been seeing this.
Anyway, it really is a logging issue that you can safely ignore.
On Mon, May 4, 2009 at 9:15 AM, Andrew Beekhof
Never mind, ignore all that. I see the problem.
What I dont understand is why no-one else has been seeing this.
Anyway, it really is a logging issue that you can safely ignore.
On Mon, May 4, 2009 at 9:15 AM, Andrew Beekhof wrote:
> On Thu, Apr 30, 2009 at 10:35 PM, Pavel Georgiev wrote:
>> I g
On Thu, Apr 30, 2009 at 10:35 PM, Pavel Georgiev wrote:
> I get an awful lot of ' Action * took *s to complete' error since switching
> from 1.0.2 to 1.0.3:
[snip]
> I`m running the prebuild rpms for centos5 (5.2 in my case).
What hardware?
I was expecting an ntpd clock jump, or a return of -1
Here is the full log from running heartbeat for ~ 5 minutes.
messages.gz
Description: GNU Zip compressed data
On May 1, 2009, at 3:33 PM, Andrew Beekhof wrote:
I'm almost positive these are bogus messages.
Can you include the full log entries (with the time stamps) for a
couple of them (a
I'm almost positive these are bogus messages.
Can you include the full log entries (with the time stamps) for a
couple of them (as well as some logs before and after the errror)?
On Thu, Apr 30, 2009 at 10:35 PM, Pavel Georgiev wrote:
> I get an awful lot of ' Action * took *s to complete' error