pcp
[Top] [All Lists]

Re: [pcp] pmie access to hosts via pmproxy

To: chandana@xxxxxxxxxxxxx
Subject: Re: [pcp] pmie access to hosts via pmproxy
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 26 May 2016 03:54:14 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1464244630.5726.30.camel@xxxxxxxxxxxxx>
References: <1464244630.5726.30.camel@xxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: 06z2VuiHqhJPGT/BuBuCTLLhgXaUMA==
Thread-topic: pmie access to hosts via pmproxy
Hi Chandana,

----- Original Message -----
> I am trying to access a pmcd host behind a firewall using pmie
> 
> This 'seems to work' with pmie, but then fails.
> 
> $ 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 via
> 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
> 

Was pmcd restarted on that machine, 6 minutes after pmie started?  That
would drop us into the pmReconnectContext logic in pmie ...

> 
> This has been working fine, untill I upgraded to pcp-3.10.6-1.el5
> 

I would start looking at commit 547cb50dd0b739988c81858e9a5346e8caed31c2
- seems the most likely pmie change that could be implicated.

Could you try building a pmie with that change backed out and see how it
goes?  That's going back a fair bit in history though - 3.10.6 is ancient
history, so I guess you were upgrading from something positively archaic ;)

cheers.

--
Nathan

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