https://prefect.io logo
Title
g

Gitanshu Sardana

09/25/2020, 10:54 PM
Hi. I just updated to prefect 0.13.8 and I'm seeing logs for graphql foreign key violations on starting the server. I cleaned up the existing docker images and volumes, and everything in ~/.prefect except config.toml and backend.toml, just to see if that changes anything, but I still see it.
n

nicholas

09/25/2020, 10:59 PM
Hi @Gitanshu Sardana - just to clarify is this on a clean installation?
g

Gitanshu Sardana

09/25/2020, 11:00 PM
Hi @nicholas! 😄 No. I already had a prefect + dask setup, i think it was 0.13.4 and then i updated the prefect version.
n

nicholas

09/25/2020, 11:04 PM
Got it - thank you! Let me look into this; I may ask you to open a ticket on the Server repo if this isn't immediately solvable, just so we can look into it next week.
g

Gitanshu Sardana

09/25/2020, 11:05 PM
Sounds good!
n

nicholas

09/25/2020, 11:15 PM
Hm since it's a foreign key violation it seems you're trying to write something to the DB from an inherited model whose ancestor doesn't exist. In this case the flow/task run doesn't seem to exist. When you upgraded, did you run the db migrations?
g

Gitanshu Sardana

09/25/2020, 11:48 PM
No i didn't. Didn't know I have to do this. Where do i find this in the docs?
n

nicholas

09/25/2020, 11:58 PM
Normally you shouldn't need to (
prefect server start
does this by default)
Just trying to figure out how you could get into this state, it's an odd one. Would you mind opening an issue at the link i posted above?
g

Gitanshu Sardana

09/26/2020, 12:01 AM
Sure. I'll do that
What I am confused about is how do I still see this even though I cleared all docker images and volumes and ~./prefect. Is the DB stored somewhere else?
n

nicholas

09/26/2020, 12:03 AM
Yeah that's very odd to me, if you've cleared your images and volumes it doesn't make much sense
You could try pruning your images/system with
docker system prune
and
docker images prune
g

Gitanshu Sardana

09/26/2020, 3:11 AM
I tried that. I also tried reproducing it on 2 other machines but couldn't. Opened an issue here with full logs
n

nicholas

09/26/2020, 6:49 AM
Thanks @Gitanshu Sardana - odd for sure but if we can repro somehow we'll see what's up.
m

Michael J Hall

09/27/2020, 11:44 PM
I am having the same issue with my upgrade.
Plus when I attempt to bring up the server on a web page using port 8080, I get the message
n

nicholas

09/28/2020, 2:05 PM
@Michael J Hall - would you mind starting a new thread describing your issue?
m

Michael J Hall

09/28/2020, 2:15 PM
Sure, np. I was able to get the graphql API to work when I logged on to the Linux server via localhost, which is not what I want. I want to be able to access a web browser client remote from the server. Is there a setting to do this via the config.toml config file?
http:/<remote.server.address>/graphql