pcp
[Top] [All Lists]

Re: One pmwebapi against multiple pcp running hosts

To: Dev Priya <devpriya00@xxxxxxxxx>
Subject: Re: One pmwebapi against multiple pcp running hosts
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Tue, 2 Apr 2013 18:27:22 -0400
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <CADPXOe=NbKrgxCtvePnAMM_MCUHibdWseAni5p+_e4k4Hwp1ow@xxxxxxxxxxxxxx>
References: <CADPXOeknVWyG8ZWgEcnVnxtHoYr3tq+g5EVof4AdAhxGZH4eiA@xxxxxxxxxxxxxx> <20130402205337.GD3659@xxxxxxxxxx> <CADPXOe=NbKrgxCtvePnAMM_MCUHibdWseAni5p+_e4k4Hwp1ow@xxxxxxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi -

> [...]
> I verified it by manually CURLing the url too. Even in verbose mode the
> output is too less to find out why the context creation might have failed.
> Is there a way to increase the verbosity of the logs even further?

The current fche/pmwebapi branch contains a fix for a thinko that
could explain misbehaving context creation.  With one level of "pmwebd -v"
verbosity, you get a pmErrStr explanation for the failing contexts.

- FChE

<Prev in Thread] Current Thread [Next in Thread>