pcp
[Top] [All Lists]

Re: [pcp] dns configuration error with pcp.io

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] dns configuration error with pcp.io
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 1 Jun 2016 17:40:50 +1000
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20160531002857.GA15708@xxxxxxxxxx>
References: <20160531002857.GA15708@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
On 31/05/16 10:28, Frank Ch. Eigler wrote:
> Hi -
> 
> Formally reporting here, for having done so on IRC appears not enough:
> 
> The pcp.io domain is misconfigured.  It both has NS records (with the
> onlydomains.com registrar (?)), and a CNAME record (pointing to
> oss.sgi.com).  This is a violation of RFC2181 section 10.1, and makes
> the domain unresolvable to some name servers.
> 
> This could be fixed by changing the CNAME to an A record, or other ways.

Is anyone attending to this?

I have a new bozo with Ubuntu 16.04 and I'm now seeing on a regular basis ...

kenj@vm11:~/src/pcp$ git pull
fatal: Unable to look up pcp.io (port 9418) (Temporary failure in name 
resolution)

and I presume this is related to Frank's observations.

ps bozo has had a bit of a steroids injection ...

kenj@bozo:~$ pcp
Performance Co-Pilot configuration on bozo:

 platform: Linux bozo 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 
2016 x86_64
 hardware: 12 cpus, 5 disks, 1 node, 32075MB RAM
 timezone: AEST-10
 services: pmcd pmproxy pmwebd
     pmcd: Version 3.11.3-1, 10 agents, 5 clients
     pmda: root pmcd proc xfs sample sampledso linux mmv jbd2 simple
 pmlogger: bozo: /var/log/pcp/pmmgr/bozo/archive-20160601.044503
           primary logger: /var/log/pcp/pmlogger/bozo/20160601.14.44
     pmie: bozo: /var/log/pcp/pmie/bozo/pmie.log
           bozo: /var/log/pcp/pmmgr/bozo/pmie.log


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