Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconnect after GraphQL outage #6

Open
scottyeager opened this issue Dec 9, 2023 · 0 comments
Open

Reconnect after GraphQL outage #6

scottyeager opened this issue Dec 9, 2023 · 0 comments

Comments

@scottyeager
Copy link
Collaborator

If there's an outage on GraphQL, we can get into a state where the bot is disconnected and won't reconnect. Need to figure out which error to look for and how to reset the connection.

Some hints from the logs:

urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='graphql.dev.grid.tf', port=443): Max retries exceeded with url: /graphql (Caused by ResponseError('too many 503 
error responses'))

requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='graphql.grid.tf', port=443): Max retries exceeded with url: /graphql (Caused by ConnectTimeoutError(<urllib3.c
onnection.HTTPSConnection object at 0x7f2b752d8b50>, 'Connection to graphql.grid.tf timed out. (connect timeout=None)'))

gql.transport.exceptions.TransportAlreadyConnected: Transport is already connected

The thing is that all of these errors can occur in the course of normal operation, and are normally recovered from. Maybe some further investigation in the logs can help see root cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant