I think this is the bug I reported recently. Update your python modules and do a full resync. It is the Django module in particular that causes the problem. There was an issue with time zone handling which would cause gaps in your data every time you synced.
Sent from my iPad On Jun 2, 2017, at 1:39 AM, Ruairi Carroll <[email protected]<mailto:[email protected]>> wrote: Hey Andrew, I hit exactly the same issue a few weeks ago ( thread<http://lists.peeringdb.com/pipermail/pdb-tech/2017-April/000311.html> ). If you can re-create the local DB, it's best you do that. /Ruairi On 31 May 2017 at 16:58, Andrew Dampf <[email protected]<mailto:[email protected]>> wrote: Hello all, I'm running into an issue when I issue a peeringdb sync command. I receive the following error: {'net': [u'network instance with id 13598 does not exist.']} : errors: {'net': [u'network instance with id 13598 does not exist.']} Network matching query does not exist. I've received this error in the past and my workaround was to add a row with fake data to the peeringdb_network table, and that allows the peeringdb sync command to complete, but I'm hoping there's a better fix available. Does anyone know why this is happening and can help me out? Thanks so much! -- Andrew Dampf Network Engineer Linode _______________________________________________ Pdb-tech mailing list [email protected]<mailto:[email protected]> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech _______________________________________________ Pdb-tech mailing list [email protected]<mailto:[email protected]> http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
_______________________________________________ Pdb-tech mailing list [email protected] http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
