https://prefect.io logo
Channels
Powered by
#prefect-community
Title
# prefect-community
m

Manuel Mourato

04/16/2020, 4:40 PM
Hello all, I am trying to create a project in Prefect's local backend from version 10.0, but I am getting the following error:
Copy code
$ prefect create project "Test-Project"


....
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
  File "python3.6/site-packages/urllib3/connectionpool.py", line 416, in _make_request
    httplib_response = conn.getresponse()
  File "python3.6/http/client.py", line 1354, in getresponse
    response.begin()
  File "python3.6/http/client.py", line 307, in begin
    version, status, reason = self._read_status()
  File "python3.6/http/client.py", line 268, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "python3.6/socket.py", line 586, in readinto
    return self._sock.recv_into(b)
urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
As anyone experienced this before?
n

nicholas

04/16/2020, 4:42 PM
Hi @Manuel Aristarán, haven't seen that exact error but one of the ways Prefect Server differs from Prefect Cloud is that Server has no concept of Projects - all flows live centrally
So when registering a flow locally, you'd use just 
flow.register()
as opposed to 
flow.register(project_name="some_project")
m

Manuel Mourato

04/16/2020, 4:47 PM
Hey @nicholas. I see, but actually that is precisely my issue. I want to register a flow, and am doing it like this 
flow.register()
, but I am getting a very similar error 
requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
I mentioned the create project command , because I saw I got a very similar error and might be easier for someone to test,
n

nicholas

04/16/2020, 4:50 PM
Ahh understood @Manuel Aristarán - my apologies. Do you have Prefect Server output that you can share? I wonder if something happened with one of the containers, perhaps the Apollo server container is down or having issues?
m

Manuel Mourato

04/16/2020, 4:54 PM
The Apollo server is indeed having issues:
Copy code
2020-04-16T16:47:30.191Z Error fetching GraphQL health: FetchError: request to <http://graphql:4201/health> failed, reason: connect ETIMEDOUT 172.18.0.4:4201
2020-04-16T16:47:30.191Z Error: Could not safely build a schema!
As is the graphql server:
Copy code
Could not upgrade the database!
Error: (psycopg2.OperationalError) could not connect to server: Connection timed out
	Is the server running on host "postgres" (172.18.0.2) and accepting
	TCP/IP connections on port 5432?
The postgres instance however does not seem to have any issues
I should probably analyze the docker compose file a little better, and understand the dependencies of all these services
n

nicholas

04/16/2020, 4:56 PM
That would do it! So most likely the migrations weren't applied for some reason, which is what would lead Apollo to be unable to build the schema
You might try stopping the server and restarting it
(which will attempt to re-apply the migrations)
m

Manuel Mourato

04/16/2020, 5:04 PM
I tried restarting a couple of times but it still has that error. But I will investigate a bit more. Thank you for the help! 🙂
n

nicholas

04/16/2020, 5:05 PM
Happy to help! 😄
j

Jeremiah

04/16/2020, 5:12 PM
Just as a hint, @Manuel Mourato it sounds like one of your services (maybe Postgres) is unable to start, which is cascading into other services — perhaps if you look near the top of the docker compose logs you’ll see some issue there. For example, maybe the port for postgres is already taken by some other process?
upvote 1
m

Manuel Mourato

04/17/2020, 11:54 AM
@Jeremiah it was an issue with an ip table rule, it's working now, thank you 🙂
j

Jeremiah

04/17/2020, 12:43 PM
@Manuel Mourato Glad to hear you solved it!
Powered by