Replies: 2 comments 7 replies
-
If your pod is not answering requests, then Socket.IO is not even running yet, so I don't see how the Socket.IO part of your application can be responsible. I suggest you debug the interaction between Gunicorn and Kubernetes, which is where the problem is most likely. |
Beta Was this translation helpful? Give feedback.
5 replies
-
If this is kubernetes, have you exposed a service and is there an endpoint for the service? This should be pretty straightforward to figure out. I am not using Django but I run flask and celery apps with socketio on k8 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Trying to run a django application with python-socketio.
Using below command for the running the pod:
exec gunicorn rc_app.wsgi:application --name $APP_NAME --workers 1 --worker-class eventlet --worker-tmp-dir /dev/shm --bind 0.0.0.0:8000 --log-level debug
Running only one pod for now to test it out.
The pod is not processing request, response is conn refused.
Beta Was this translation helpful? Give feedback.
All reactions