Chandana,
There are several layers in play here ... and the current pmie code is a little
different to 3.10.6 just around the area where you're having trouble.
On 26/05/16 16:37, Chandana De Silva wrote:
> I am trying to access a pmcd host behind a firewall using pmie
>
> This 'seems to work' with pmie, but then fails.
What does 'seems to work' mean? It is unclear from this log that it ever got
started.
> $ cat /var/log/pcp/pmie/singha-a.log
>
> Log for pmie on mon01.toc.mel.au.m4u.com.au started Thu May 26 16:28:08 2016
>
>
> pmie: PID = 2719, default host = singha-a.m4u.com.au
> viasingha-a.m4u.com.au@xxxxxxxxxxxxxxxxxxxxxxxxxx
> <mailto:singha-a.m4u.com.au@xxxxxxxxxxxxxxxxxxxxxxxxxx>
>
>
> [Thu May 26 16:34:08] pmie(2719) Info: Cannot connect to pmcd on host
> singha-a.m4u.com.au
>
> pmie: warning - host singha-a.m4u.com.au is unreachable
Can you please try a couple of things for me on the system where pmie is
expected to be running:
1. Output from
$ echo "hinv.ncpu" | pmie -h singha-a.m4u.com.au@xxxxxxxxxxxxxxxxxxxxxxxxxx
-v -Dcontext -t 1 -T 1
2. Output from
# <path to $PCP_BINADM_DIR>/pmie_check -N -V -V
And I assume there is no host referenced in the pmie rules that your pmie
control file associates with the pmie instance in question, but it would be
nice to confirm that ... send me the control file and the pmie rules file via
MM mail if that is easier.
|