You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Might be related to this
I've started getting those errors out of the blue every few graphql queries, while the server freezes completely and stays unresponsive until I restart.
2024-04-29 17:57:33,887 DEBUG [daphne.http_protocol:261] http_protocol 1 281473823117408 HTTP 200 response started for ['172.22.0.1', 33126]
2024-04-29 17:57:33,889 DEBUG [daphne.http_protocol:229] http_protocol 1 281473823117408 HTTP close for ['172.22.0.1', 33126]
2024-04-29 17:57:33,890 DEBUG [daphne.http_protocol:275] http_protocol 1 281473823117408 HTTP response complete for ['172.22.0.1', 33126]
2024-04-29 17:57:33,890 INFO [django.channels.server:168] runserver 1 281473823117408 HTTP POST /graphql 200 [5.55, 172.22.0.1:33126]
2024-04-29 17:57:43,729 DEBUG [daphne.http_protocol:219] http_protocol 1 281473823117408 HTTP disconnect for ['172.22.0.1', 54880]
2024-04-29 17:57:54,242 WARNING [daphne.server:278] server 1 281473823117408 Application instance <Task pending name='Task-38' coro=<ASGIStaticFilesHandler.__call__() running at /env/lib/python3.12/site-packages/django/contrib/staticfiles/handlers.py:101> wait_for=<Task cancelling name='Task-43' coro=<ASGIHandler.handle.<locals>.process_request() running at /env/lib/python3.12/site-packages/django/core/handlers/asgi.py:193> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/local/lib/python3.12/asyncio/futures.py:387, Task.task_wakeup()]> cb=[Task.task_wakeup()]>> for connection <WebRequest at 0xffffb36689e0 method=POST uri=/graphql clientproto=HTTP/1.1> took too long to shut down and was killed.
2024-04-29 17:57:55,246 WARNING [daphne.server:278] server 1 281473823117408 Application instance <Task cancelling name='Task-38' coro=<ASGIStaticFilesHandler.__call__() running at /env/lib/python3.12/site-packages/django/contrib/staticfiles/handlers.py:101> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]>> for connection <WebRequest at 0xffffb36689e0 method=POST uri=/graphql clientproto=HTTP/1.1> took too long to shut down and was killed.
Debug logs makes me think that the server is experiencing issues when attempting to close down tasks after processing requests.
It started few days ago without any change on my side and it happens all the time now.
There is no particular query who causes this, its just happens after few api calls, even if I just pick some random query and call it few times from Postman.
I don't experience those issues on prod, which using different environment, only on my dev server which I'm running on local host, using docker desktop.
I've tried updating packages to most updated versions, but nothing changed.
My requirements file
python version is 3.11
When it happens there is no notable spike in CPU or memory usage on the docker container.
I guess the errors are just the symptoms of the timeouts caused by the server unresponsiveness but I don't know even where I can even start debugging this issue.
The text was updated successfully, but these errors were encountered:
I'm going to lock this conversation as all the "Me too" comment are just noise.
ASGIStaticFilesHandler is only used in development, and this is a artefact of the development server reloading.
If someone wants to look at making ASGIStaticFilesHandler exit cleanly in that case, PRs are welcome.
django
locked as off-topic and limited conversation to collaborators
Aug 15, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Might be related to this
I've started getting those errors out of the blue every few graphql queries, while the server freezes completely and stays unresponsive until I restart.
Debug logs makes me think that the server is experiencing issues when attempting to close down tasks after processing requests.
It started few days ago without any change on my side and it happens all the time now.
There is no particular query who causes this, its just happens after few api calls, even if I just pick some random query and call it few times from Postman.
I don't experience those issues on prod, which using different environment, only on my dev server which I'm running on local host, using docker desktop.
I've tried updating packages to most updated versions, but nothing changed.
My requirements file
My dev docker compose file
My prod docker compose file
python version is 3.11
When it happens there is no notable spike in CPU or memory usage on the docker container.
I guess the errors are just the symptoms of the timeouts caused by the server unresponsiveness but I don't know even where I can even start debugging this issue.
The text was updated successfully, but these errors were encountered: