Channels
pacc-may-31-2023
prefect-ai
pacc-clearcover-june-12-2023
marvin-in-the-wild
data-ecosystem
geo-israel
pacc-june-14-2023
geo-japan
prefect-cloud
ppcc-may-16-2023
prefect-azure
prefect-docker
prefect-recipes
gratitude
geo-nyc
geo-bay-area
geo-boston
geo-london
geo-dc
geo-chicago
geo-berlin
geo-texas
geo-seattle
geo-colorado
prefect-community
data-tricks-and-tips
prefect-aws
prefect-gcp
introductions
find-a-prefect-job
prefect-dbt
random
events
ask-marvin
show-us-what-you-got
prefect-getting-started
prefect-integrations
prefect-contributors
best-practices-coordination-plane
announcements
prefect-server
prefect-ui
prefect-kubernetes
Title
k
Kathryn Klarich
05/06/2022, 9:46 PMOur prefect agent has been running without issue on ECS for the past ~11 months (since June 28 2021), but about 1 hour ago we noticed we were unable to submit new flows. Upon further investigation it appears our agent crashed and has been trying to restart but keeps crashing. I’m not sure if this is what initially caused it to crash but the error message we are seeing in cloudwatch logs now is :
ValueError: You have not set an API key for authentication.z
Zanie
05/06/2022, 9:47 PMIt sounds like you were using API tokens for auth instead of keys and your agent has updated from a pre-1.0 container to a 1.0+ container which drops support for API tokens.
k
Kevin Kho
05/06/2022, 9:47 PMTokens were deprecated for API keys in 0.15
z
I’d recommend pinning your container version to resolve the immediate issue, then switch over to keys and upgrade at your leisure. I could be wrong about the cause though! Let me know if this isn’t the case.
:upvote: 2
k
Kathryn Klarich
05/06/2022, 9:52 PMah ok we will try that, thanks!
that worked!
we were using the :latest image so I think it must have pulled a new image which upgraded to 1.0
thanks for the quick response!