Hey prefect I am trying to run `prefect server start` for th

Question

Hey prefect I am trying to run `prefect server start` for the first time and running into some errors with the postgres step Can you help troubleshoot

Zachary Hughes · Answer

Sure thing < Adam Roderick> What s up

Adam Roderick · Answer

I m looking for the first error

Adam Roderick · Answer

The first hard error looks like alembic

Adam Roderick · Answer

```apollo 1 | 2020 04 13T14 09 46 782Z Error fetching GraphQL health FetchError request to <http graphql 4201 health> failed reason connect ECONNREFUSED 172 25 0 4 4201```

Adam Roderick · Answer

There is an earlier warning with hasura 1 ```hasura 1 | internal could not connect to server Connection refused n tIs the server running on host postgres 172 25 0 2 and accepting n tTCP IP connections on port 5432 n path $ error connection error code postgres error ```

Zachary Hughes · Answer

Okay interesting So far definitely looking like the chain of failures I d expect to see from an error with Postgres

Adam Roderick · Answer

The first time I attempted there was a port conflict with a locally installed instance of postgres

Adam Roderick · Answer

So I shut down the local instance and retried

Adam Roderick · Answer

any way to do a wipe and clean slate retry

Zachary Hughes · Answer

Sure is With your Prefect Server inf still up I d recommend running `prefect server database reset` with the optional ` y` step to skip the confirmation step

Zachary Hughes · Answer

That ll rerun the alembic migrations and reapply the Hasura metadata If there was a fluke getting that up and started the first time should do the trick for you

Adam Roderick · Answer

I m getting `prefect server` is not a command

Adam Roderick · Answer

I have 10 1 installed

Zachary Hughes · Answer

Oh duh Sorry I m used to typing `prefect cloud` for local dev sweat smile

Adam Roderick · Answer

Sorry if I m dense here what should the command be

Zachary Hughes · Answer

Not dense at all wanted to make sure I gave you the proper command this time Sorry it s a little more complex here s what I d recommend cd into the `server` directory `pip install e ` then run `prefect server database reset y`

Zachary Hughes · Answer

There s probably room for us to improve the CLI experience there thanks for bringing it to our attention

Adam Roderick · Answer

No problem and thanks for the help What do you mean by server directory

Adam Roderick · Answer

I looked in the directory where I installed prefect and I looked in the virtual env s prefect directory I installed prefect from pyPI

Zachary Hughes · Answer

Yep I apologize again Adam this was a remnant from my local development on `prefect server` If you `pip install`ed prefect you won t have that directory

Zachary Hughes · Answer

Your best bet might be to cancel your original spin up of infrastructure and then run `prefect server start`

Zachary Hughes · Answer

If you re still running into errors there happy to walk you through them But if it was a transient issue with a port conflict that should do the trick

Jeremiah · Answer

< Adam Roderick> you mentioned an alembic error do you mind sharing that

Adam Roderick · Answer

I don t mind Give me a moment and I ll update and share the errors

Adam Roderick · Answer

Untitled

Adam Roderick · Answer

On my first run I had errors due to a port conflict between the postgres container and a local install of postgres After deleting all the containers shutting off my local postgres and trying again the above is pretty consistent output

Adam Roderick · Answer

At current state I can run the UI in the browser and I can register a flow It shows up in the UI But when I try to run it just hangs and eventually shows up in the Late Runs list

Jeremiah · Answer

Ok This log looks good and that makes sense that Postgres was unable to start before The current issue just sounds like there isn t a local agent running

Jeremiah · Answer

Your Cloud agents won t work with the open source server Try `prefect backend server` and `prefect agent start`to spin up a local one

Adam Roderick · Answer

That must be what I am missing I ll give that a try

Adam Roderick · Answer

That was it

Adam Roderick · Answer

The errors in the docker output are still there and confused me But I was able to register a flow locally with the UI and execute it from the UI

Adam Roderick · Answer

Thanks for your help

Adam Roderick · Answer

LMK if you want any other info from my machine

Jeremiah · Answer

ok I think we re good then those docker errors are most likely a consequence of our services being somewhat order dependent and docker not being a great place to have order dependent services slightly smiling face For example hasura depends on postgres being available graphql depends on hasura being available apollo depends on graphql being available Therefore there can be some noise as they jockey for position however we are going to look into it because we don t want it to be alarming

Adam Roderick · Answer

All good from my end Thanks again