pcp
[Top] [All Lists]

Re: pmFetch - invalid results

To: Mark Goodwin <markgw@xxxxxxx>
Subject: Re: pmFetch - invalid results
From: Sadanand Kota <sada@xxxxxxxxxxx>
Date: Mon, 29 Apr 2002 13:42:47 -0500 (CDT)
Cc: pcp@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.33.0204291333500.1795-100000@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-pcp@xxxxxxxxxxx
Mark,
Thanks for reply. I did check it again with the pmDebug flag. The
OUTPUT on two machines are DIFFERENT. On the faulty machine, even
after I say pmUseContext(remote context), the pcp function calls are using
the local context.

I am attaching the code with this mail. Also, I have attached the outputs
written on to a file.
'output1' is the output on faulty machine and 'output2' that of correct
one. (The output clearly differ on line 8).

I would really appreciate if you can let me know why its happening.

Thanks,
Sadanand



On Mon, 29 Apr 2002, Mark Goodwin wrote:

> On Wed, 17 Apr 2002, Sadanand Kota wrote:
>
> > I am collecting metrics of two linux systems through my program
> > using pcp API. But I am getting the metrics for only one machine i.e
> > always pmfetch returns the metrics of home node even if the context of
> > remote machine is set through pmUseContext. Neither pmUseContext nor
> > pmWhichContext gave any error while they were called.
> >
> > Another strange thing is that, the same program works properly when run
> > on a different machine i.e it gets the metrics of both home(new) machine
> > and remote machine.
> >
> > Any idea for solution?
> >
>
> Sadanand,
>
> Is this reproducible? Could you post your code, or is it proprietary?
> Please re-run your program again on the two different machines, but with
>
> extern int pmDebug;
> pmDebug = 18;
>
> This will enable debug messages for pmFetch calls and for pcp context
> manipulation. You should be able to compare the debug listings to
> see what's different.
>
> To see all available pmDebug settings, run pmdbg -l
>
> thanks
> -- Mark
>

Attachment: output1
Description: Text document

Attachment: output2
Description: Text document

Attachment: test.tgz
Description: Binary data

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