Celery worker deploy on Azure fails: didn't respond to HTTP pings on port: 80

[sglebs]

If we could have some port that these PaaS platforms could ping to check for liveness, it would make things so much easier.

2024-02-05T18:59:27.316Z ERROR - Container staging-foobarcelery_0_3ed668ba for site staging-foobarcelery has exited, failing site start 2024-02-05T18:59:27.318Z ERROR - Container staging-foobarcelery_0_3ed668ba didn't respond to HTTP pings on port: 80, failing site start. See container logs for debugging.

How can I run Celery in worker mode and still have a port that can be pinged for something? Even a "nothing here" reply would do.

Any tips on how to do this? Subclass? Or is it in the roadmap? Thanks!

[sglebs]

#1177 seems to be related. But I am using Redis and not RabbitMQ. And I am using Azure (free credits!), and not Kubernetes. It using this GitHub hook: https://github.com/Azure/webapps-deploy

I have not been able to disable the liveness check on the exposed port on deploy. And I have not being able to bundle a tiny web server to just reply "just go away". Docker compose is experimental on Azure (compose with celery+nginx might be a valid hack).

I am willing to write my own code which is like celery-worker+FastAPI for a single stupid endpoint, but I am not sure how to achieve this.

Help is welcome. Thanks.

[sglebs]

The current workaround I am trying requires 2 more python VMs:

1. supervisord
2. http.server

Here's the supervisord.conf:

[supervisord]
# http://supervisord.org/configuration.html
nodaemon=true
logfile=/dev/null
logfile_maxbytes=0

[program:celery]
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
redirect_stderr=true
command=celery worker --loglevel=info -E

[program:web]
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
redirect_stderr=true
#https://realpython.com/python-http-server/
command=python3 -m http.server -b "::" -d ./app/static 80