[PDB-tech] POC sync not complete

[Martin J. Levy]

You only get "public" ones. This count was zero on March/15'th

> On Apr 13, 2016, at 8:04 AM, Paul Vlaar <pvlaar at afilias.info> wrote:
> 
> P.S. in my ~/.peerindb/config.yaml I have:
> 
> peeringdb:
>  password: '[password]'
>  timeout: 0
>  url: https://www.peeringdb.com/api
>  user: 'pvlaar'
> 
> 
> Thanks.
> 
> 
>> On 13/4/16 4:57 PM, Paul Vlaar wrote:
>> Just did an initial "peeringdb sync" and noticed the number of POCs is
>> not complete:
>> 
>> pvlaar at peering:~$ peeringdb sync
>> [...]
>> Starting new HTTPS connection (1): beta.peeringdb.com
>> "GET /api/poc?since=0 HTTP/1.1" 302 160
>> Starting new HTTPS connection (1): www.peeringdb.com
>> "GET /api/poc?since=0 HTTP/1.1" 200 None
>> poc last update 0 225 changed
>> data to be processed 225
>> 
>> 225 seems way too low.
>> 
>> When I go via my browser (https://www.peeringdb.com/api/poc?since=0) I
>> do seem to get the full list.
>> 
>> What may be the problem here?
>> 
>>     ~paul
> 
> -- 
> Paul Vlaar
> DNS Infrastructure Group
> Afilias
> 
> e-mail: pvlaar at afilias.info
> _______________________________________________
> Pdb-tech mailing list
> Pdb-tech at lists.peeringdb.com
> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech