Re: [PDB Tech] [External Mail] Re: Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Milton Ngan
Thanks. I saw your reply to the list. Glad you managed to get it working. I was using it for our peering managed tool, but I have since switched to Peering Manager which does its own little sync (not a complete sync) instead of using peeringdb-py, so we have not had to worry about this bug in a

Re: [PDB Tech] [External Mail] Re: Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Matt Griswold
* Milton Ngan [200516 01:02 +]: > Thanks. I saw your reply to the list. Glad you managed to get it > working. I was using it for our peering managed tool, but I have > since switched to Peering Manager which does its own little sync (not > a complete sync) instead of using peeringdb-py, so we

Re: [PDB Tech] [External Mail] Re: Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Milton Ngan
I replicated the problem and added some additional debugging to illustrate the problem. The first time stamp is what is in the object and is in UTC, the second is the UTC timestamp for now, and the third is the local timestamp. You can see that the update time is in the "future" by about 37 minu

Re: [PDB Tech] [External Mail] Re: Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Brian Dickson
Hi, Milton, Just want to confirm (to keep you in the loop), your suggestion did fix the problem for me. Thanks again, Brian On Fri, May 15, 2020 at 3:41 PM Milton Ngan wrote: > I replicated the problem and added some additional debugging to illustrate > the problem. The first time stamp is what

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Milton Ngan
If you are situated West of UTC you might be running into the timezone issue I reported. The work around I had was to change this line in peeringdb/_update.py from self.st

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Brian Dickson
And yes, it is now sync'd. Thanks again! Brian On Fri, May 15, 2020 at 2:55 PM Brian Dickson wrote: > Yes, it's still running, but I'm not getting the error messages I was > seeing before. > I expect it to work completely now. > > Thanks, everyone, especially Milton! > > (Also, you may want to

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Brian Dickson
Yes, it's still running, but I'm not getting the error messages I was seeing before. I expect it to work completely now. Thanks, everyone, especially Milton! (Also, you may want to approve his patch. :-) ) Brian On Fri, May 15, 2020 at 2:42 PM Chris Caputo wrote: > Any better with Milton's 's

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Chris Caputo
Any better with Milton's 'self.start_time = datetime.utcnow()' change? Thanks, Chris On Fri, 15 May 2020, Brian Dickson wrote: > On Fri, May 15, 2020 at 12:57 PM Brian Dickson > wrote: > The local database is empty. I'll make sure that's the case just to be > safe. > > # peeringdb --ver

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Asbjørn Sloth Tønnesen
Hi Brian, On 5/15/20 5:43 PM, Brian Dickson wrote: (This is kind of urgent for me, my goal is to get a snapshot of the data, so any alternative workaround would be helpful in the meantime.) Alternatively you could use: https://git.2e8.dk/peeringdb-simplesync/about/ -- Best regards Asbjørn Slo

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Brian Dickson
On Fri, May 15, 2020 at 12:57 PM Brian Dickson < brian.peter.dick...@gmail.com> wrote: > The local database is empty. I'll make sure that's the case just to be > safe. > > # peeringdb --version > > peeringdb 1.0.0 > > > # django-admin --version > > 2.2.12 > > > # pip freeze > > asgiref==3.2.7 > >

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Brian Dickson
The local database is empty. I'll make sure that's the case just to be safe. # peeringdb --version peeringdb 1.0.0 # django-admin --version 2.2.12 # pip freeze asgiref==3.2.7 certifi==2020.4.5.1 cfu==1.5.0 chardet==3.0.4 click==7.1.2 Django==2.2.12 django-countries==6.1.2 django-hand

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Chris Caputo
Hi. Does restarting with a fresh/empty local database help at all? Also, what does the following show?: peeringdb --version django-admin --version pip freeze Thanks, Chris On Fri, 15 May 2020, Brian Dickson wrote: > Arnold Nipper said to send to this list. > > (This is kind of urgent for me,

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

2020-05-15 Thread Brian Dickson
Arnold Nipper said to send to this list. (This is kind of urgent for me, my goal is to get a snapshot of the data, so any alternative workaround would be helpful in the meantime.) I'm in the process of setting up a local copy, and have run into a problem after getting the peeringdb-py stuff set u