In addition to the comments from everyone else ...
1. Check xxx.log in the same place where pmcd.log is being created
... this has to be a daemon PMDA, and by default they all use their
name to create their own log file ... check also xxx.log.prev which
may be the previous one if the problem is not deterministic.
2. Turn on PDU tracing in the PMDA ... add -D pdu to the arguments
in pmcd.conf and restart the PMDA (SIGHUP to pmcd should suffice).
The output will be in xxx.log.
3. Turn on PDU tracing in PMCD
pmstore pmcd.control.debug 1
and then restart the PMDA. The additional output will be in
pmcd.log.
4. Look for a core file in the directory where pmcd.log is created
... check if this is your PMDA.
5. Debug your PMDA with dbpma ... this will let you exercise very
low-level interactions with PMDA independent of PMCD, but using
the same message passing protocols (PDUs) as PMCD will use.
If all else fails, post the pmcd and pmda log files from 2. and 3. above.
On Fri, 15 Feb 2002, Sadanand Kota wrote:
> Hi,
> I have written a PMDA to find the network characteristics of a process.
> I have assigned it a domain number number 254 ( in domain.h).
> I dont have any other PMDA with same number. Byt when I install the PMDA
> and check it with 'pminfo' command, it gives the error message as ' No
> PMCD agent for domain of request'.
>
> I have checked the pmcd.conf file to see for any conflicts and found
> nothing. The message at the end of pmcd.log is 'Cleanup "xxx" agent
> (dom 254): protocol failure for fd=14, exit(255)' where 'xxx' is name of
> my PMDA.
>
> Also, the installation scripts of PMDA does not give any error messages.
>
> Any idea to correct it?
>
> Sadanand
>
>
>
|