I replaced 'setenv' with 'set' in file 083. The former problem is
fixed, but I got a new problem.
Please see the following result. I got this result on pcp-2.3.0-8.
From now on, I am moving to the new version of pcp, all future result files
correspond to this new pcp.
----------------------------------------------------------
083 - output mismatch (see 083.out.bad)
33c33
< Unable to connect to primary pmlogger at ME: No permission to perform
requested operation
---
> Unable to connect to primary pmlogger at ME: No such PMAPI error code
(-1042)C
----------------------------------------------------------
Sonic Zhang
-----Original Message-----
From: kenmcd@xxxxxxxxxxxxxxxxx [mailto:kenmcd@xxxxxxxxxxxxxxxxx]
Sent: 2003?1?6? 19:10
To: Zhang, Sonic
Cc: PCP (E-mail)
Subject: Re: New result for case 083
On Fri, 3 Jan 2003, Zhang, Sonic wrote:
> Hi
> See the attachment.
> The cause of 083 is also related to pmlogger.
>
> Arrgghhh ... pmlogger (pid=29436) failed to start after 20 seconds
In this case, the configuration file that 083 generates looks to be broken.
I need to see 083.full.
But you can probably debug it yourself ... here is my 083.full from a
successful run ...
me=snowy.melbourne.sgi.com
shortme=snowy.melbourne.sgi.com
other1=wobbly.melbourne.sgi.com
other2=rattle.melbourne.sgi.com
# test various "all" commands
log mandatory on 1 hour {
kernel.all.load [ "1 minute" ]
}
log mandatory maybe sample.bin["bin-100","bin-200","bin-300","bin-400"]
log mandatory off sample.bin["bin-600","bin-700","bin-800","bin-900"]
[access]
allow wobbly.melbourne.sgi.com : all except mandatory;
disallow rattle.melbourne.sgi.com : all;
allow snowy.melbourne.sgi.com : all;
083.out.ZIP
Description: Binary data
|