element-hq / element-hq/sygnal

Investigate Sentry error: "Could not connect to server:" from aioapns

Open
#202 0 comments 0 reactions 0 assignees View on GitHub
bug help wanted
Dominant language
Python
Stars
44
Forks
20
Avg merge
16h 53m
Merged PRs (30d)
1

Description

*This issue was originally created by [**@callahad**](https://github.com/callahad) at .*

Our monitoring for Syngal on matrix.org occasionally sees an error:

`Could not connect to server:`

For whatever reason, Sentry does log a traceback for this error; it just reports the line above.

That error message appears to come from this line in aioapns: https://github.com/Fatal1ty/aioapns/blob/v2.0.2/aioapns/connection.py#L356

So... what could cause this to happen? What calls does Sygnal make that eventually trigger that error? Can we handle the error more gracefully?

(For Element employees, this is https://sentry.matrix.org/sentry/sygnal-matrixorg/issues/15228/)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.