Replies: 5 comments 1 reply
-
I've also tried to execute the celery worker manually, but it stills exits early:
|
Beta Was this translation helpful? Give feedback.
-
Hi @fcoedno , can you try out the Docker compose version rather than the single version? https://github.com/mediacms-io/mediacms/blob/main/docs/admins_docs.md#3-docker-installation Would be interesting if you can include your methodology. Also @swiftugandan could provide useful feedback here. Thanks |
Beta Was this translation helpful? Give feedback.
-
Changed the title, as I don't think it's that much related with Celery rather than how this is tested against Kubernetes environment. |
Beta Was this translation helpful? Give feedback.
-
@fcoedno @mgogoulos looks like we have a kubernetes deployment here - https://youtu.be/MnvO2OMs5e4 |
Beta Was this translation helpful? Give feedback.
-
Thanks for the link @swiftugandan ! I saw the video, and have placed a comment if the configuration is available. |
Beta Was this translation helpful? Give feedback.
-
Describe the issue
I am trying to deploy MediaCMS with Kubernetes. My first attempt is using a "single server" approach. So both WEB and celery workers are enabled in a single container.
I have managed to test the web application and uploaded media. However, the encoding never finishes.
Taking a look at supervisor services, the celery long and short workers always exit early:
I haven't found any useful logs at
logs/celery_long.log
andlogs/celery_short.log
but will place the contents here:logs/celery_long.log
:The redis instance is up, and there are keys in the connected DB (1):
Any idea on how to debug this?
Beta Was this translation helpful? Give feedback.
All reactions