Having ye old issue of Flows are submitted and an agent sees

Question

Having ye old issue of Flows are submitted and an agent sees them but they get stuck in submitted for execution I am wondering if anyone knows how to debug this I know that the labels on the task and the agent match the docker agent has pulled the image started a container and completed flow run submission from the logs Using either the Local executor or LocalDaskExecutor does not change the fact that Flows never progress from the submitted for execution state Is there a way of trying to look inside an agent to figure out what is not working

Mariia Kerimova · Answer

Hello Samuel Do you see any logs Can you pass a flag ` show flow logs` to the agent

Samuel Hinton · Answer

I can restart the agent with those kwargs one moment slightly smiling face

Samuel Hinton · Answer

Ah yes I see a ```urllib3 exceptions MaxRetryError HTTPConnectionPool host= ds prefect apollo port=4200 Max retries exceeded with url graphql graphql Caused by NewConnectionError lt urllib3 connection HTTPConnection object at 0x7fd8aa3018b0 gt Failed to establish a new connection Errno 2 Name or service not known ``` error when it tries to start I wonder if why its graphql graphql instead of graphql

Mariia Kerimova · Answer

Yes looks like

Josh Greenhalgh · Answer

< Samuel Hinton> did you ever work out what was going on here Where ` graphql graphql` came from What was causing the connection issues to apollo I am having very similar issues but no idea why

Josh Greenhalgh · Answer

My flow runs fine for the majority of its tasks then a few mapped tasks finish in a pending state and I have errors very similar to the one you have above

Samuel Hinton · Answer

I actually didnt manage to figure this out at all disappointed I upgraded to the latest version and restarted the services a few times and it started working consistently The root cause of the issue is still a mystery But yes sounds like exactly what I was experiencing but unfortunately no words of wisdom from me