[PDB Tech] peeringdb sync error

[Paul Vlaar]

On 20/9/16 21:35, Stefan Pratter wrote:
-snip-
> pip uninstall django-peeringdb -y
> pip install git+https://github.com/peeringdb/django-peeringdb@0.2.2.2

That seems to have fixed it:

pvlaar at peering:~$ /usr/local/bin/peeringdb sync
Operations to perform:
  Synchronize unmigrated apps: django_peeringdb
  Apply all migrations: admin, contenttypes, auth, sessions
Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
  Installing custom SQL...
Running migrations:
  No migrations to apply.
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/org?since=1474390503 HTTP/1.1" 200 None
org last update 1474390503 0 changed
data to be processed 0
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/fac?since=1473922504 HTTP/1.1" 200 None
fac last update 1473922504 27 changed
data to be processed 27
org.15066 not found locally, trying to fetch object...
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/org/15066?depth=0 HTTP/1.1" 200 None
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/net?since=1473944104 HTTP/1.1" 200 None
net last update 1473944104 111 changed
data to be processed 111
org.15068 not found locally, trying to fetch object...
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/org/15068?depth=0 HTTP/1.1" 200 None
org.14997 not found locally, trying to fetch object...
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/org/14997?depth=0 HTTP/1.1" 200 None
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/ix?since=1473443705 HTTP/1.1" 200 None
ix last update 1473443705 14 changed
data to be processed 14
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/ixfac?since=1473782107 HTTP/1.1" 200 None
ixfac last update 1473782107 46 changed
data to be processed 46
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/ixlan?since=1473540907 HTTP/1.1" 200 None
ixlan last update 1473540907 10 changed
data to be processed 10
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/ixpfx?since=1473245709 HTTP/1.1" 200 None
ixpfx last update 1473245709 19 changed
data to be processed 19
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/poc?since=1473944108 HTTP/1.1" 200 None
poc last update 1473944108 84 changed
data to be processed 84
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/netfac?since=1473926111 HTTP/1.1" 200 None
netfac last update 1473926111 531 changed
data to be processed 531
Starting new HTTPS connection (1): www.peeringdb.com
"GET /api/netixlan?since=1473944112 HTTP/1.1" 200 None
netixlan last update 1473944112 96 changed
data to be processed 96
pvlaar at peering:~$

> Since this fixes the updated \ created fields it is recommended you
> start from a fresh database, but in the tests we have done it didn't
> cause any immediate problems to just do an incremental sync on a 0.2.2
> database that has local times in those fields.

I ran this on the existing DB and it seems to have gone through okay.
I'll keep an eye on future runs.

Thanks!

	~paul

-- 
Paul Vlaar
Contracting for DNS Infrastructure Group, Afilias PLC

e-mail: pvlaar at afilias.info