On Mon, Aug 3, 2009 at 11:27 AM, Lars Marowsky-Bree wrote:
> On 2009-08-02T11:14:35, Andrew Beekhof wrote:
>
>>> The transition graph already includes an unique identifier for each
>>> action. If this was made, maybe, a bit shorter, and provided to the RA
>>> as part of the environment, the RA cou
On 2009-08-03T10:44:27, Dominik Klein wrote:
> > Though I don't see the point, grepping for the resource id is usually
> > just as effective.
> I totally agree here. I have helped quite a few people understand their
> problems on IRC and grepping the resource id usually works well.
The first par
On 2009-08-02T11:14:35, Andrew Beekhof wrote:
>> The transition graph already includes an unique identifier for each
>> action. If this was made, maybe, a bit shorter, and provided to the RA
>> as part of the environment, the RA could include this as part of each
>> log message - and if then this
> Though I don't see the point, grepping for the resource id is usually
> just as effective.
I totally agree here. I have helped quite a few people understand their
problems on IRC and grepping the resource id usually works well.
> I'd suggest focusing on improving the error logging that most RAs
On Aug 1, 2009, at 12:56 PM, Lars Marowsky-Bree wrote:
Hi,
so we all have seen plenty of cases where people, when asked what is
wrong with their resources, report the pengine logfile
(unpack_rsc_op).
Now, we all know that this is not the real error message, but just the
PE analyzing the st
Hi,
so we all have seen plenty of cases where people, when asked what is
wrong with their resources, report the pengine logfile (unpack_rsc_op).
Now, we all know that this is not the real error message, but just the
PE analyzing the state of the cluster, based on the error to exit code
mapping by
