Open ahankinson opened 8 months ago
Any way I can reproduce this?
Unfortunately I'm not getting any information about any requests that are triggering this, other than what is in the stack trace.
My current working hypothesis is that it's a client that prematurely closes the request. The only other clue is that sometimes it's failing with the buf
variable being something like:
b'\x00\x00\x00*\x80\x04\x95\x1f\x00\x00\x00\x00\x00\x00\x00(\x8c\x0c7f7c1afd5f40\x94\x8c\x06values\x94)}\x94t\x94.'
I don't know how to decode it, nor do I know if it's useful if I did. It is never the same value, though.
Is there an existing issue for this?
Describe the bug
I have Sentry monitoring my Sanic server processes. Increasingly, I am seeing EOFError exceptions. A minimal stack trace is this:
I am running Sanic with the following command (formatted as a python list):
This is run through a systemd unit file:
I'm attaching a PDF of the full stack trace that Sentry is reporting. I apologize that it's not in a more convenient form, but I couldn't figure out how to get it out in a readable manner. stack-trace.pdf
Code snippet
There does not seem to be any interaction with my own application code.
Expected Behavior
No response
How do you run Sanic?
Sanic CLI
Operating System
Linux
Sanic Version
23.12.1
Additional context
Ubuntu 22.04 (Linux-5.15.0-89-generic-x86_64-with-glibc2.35)
Python 3.11.0