peeringdb: PeeringDB sync fails on MacOS
Sync is failing. It fails on IX 3233 which looks like a tunnel IX. Maybe #782 should be rethought?
Traceback (most recent call last):
File "/usr/local/bin/peeringdb", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.8/site-packages/peeringdb/cli.py", line 62, in main
return handler(config=cfg, **vars(options))
File "/usr/local/lib/python3.8/site-packages/peeringdb/commands.py", line 20, in _wrapped
r = func(*a, **k)
File "/usr/local/lib/python3.8/site-packages/peeringdb/commands.py", line 219, in handle
client.update_all(rs)
File "/usr/local/lib/python3.8/site-packages/peeringdb/_update.py", line 66, in update_all
self._atomic_update(lambda: ctx.sync_resource(r, since=since))
File "/usr/local/lib/python3.8/site-packages/peeringdb/_update.py", line 78, in _atomic_update
sync_func()
File "/usr/local/lib/python3.8/site-packages/peeringdb/_update.py", line 66, in <lambda>
self._atomic_update(lambda: ctx.sync_resource(r, since=since))
File "/usr/local/lib/python3.8/site-packages/peeringdb/_tasks_async.py", line 65, in _wrapped
return loop.run_until_complete(func(*a, **k))
File "/usr/local/Cellar/python@3.8/3.8.5/Frameworks/Python.framework/Versions/3.8/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
return future.result()
File "/usr/local/lib/python3.8/site-packages/peeringdb/_tasks_async.py", line 41, in _wrapped
item = gen.send(r)
File "/usr/local/lib/python3.8/site-packages/peeringdb/_update.py", line 287, in sync_row
B.clean(obj)
File "/usr/local/lib/python3.8/site-packages/django_peeringdb/client_adaptor/backend.py", line 150, in clean
obj.full_clean()
File "/usr/local/lib/python3.8/site-packages/django/db/models/base.py", line 1171, in full_clean
raise ValidationError(errors)
django.core.exceptions.ValidationError: {'ix': ['Internet Exchange instance with id 3233 does not exist.']}
%
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 3
- Comments: 33 (19 by maintainers)
I’ll point out that my instance doesn’t fail with a “virtual” IXP, and in the network objects. Without digging into the code, I think we can safely rule out that as a possible cause.
deleting the db, and starting again, i get error on a new network/ix/fac. i’m going to spin up a VM now to test.
I built and installed on MacOS (Catalina 10.15.5). Ran into a different (but similar) issue with a network not existing, that clearly does: https://www.peeringdb.com/net/2425
OSX 10.15.6
That WAS a fresh table.