Repository navigation
broken encoding #1527
Unanswered
MinkaKaraivanova
asked this question in
Q&A
broken encoding
#1527
Replies: 3 comments
|
does the issue get resolved after a Docker compose restart web/celery_worker? |
0 replies
|
I just pushed a new release, 8.1.2 which removes this check you mention above, since it's redundant anyways. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
MediaCMS running as dockered installation on an Ubuntu 22.04.5 LTS.
Mediacms was upgraded from 7.6.0 to 8.0.8 using
Initial testing: after a video was uploaded, the Encoding to the
different Ecoding profiles does not start. In the Django interface,
the encodings are reported as Pending. In some cases, they are
reported as Failed.
All DB migrations during the upgrade are done successfully.
The hypothesis is that after the celery worker container starts it
initializes the django application; django loads installed apps and
among them lti. And when ensure_keys_exist() is run, it touches the
database (we see django warnings like: Accessing the database during app
initialization is discouraged). When celery forks the forks its worker
children, they inherit a bad/half-used database connection. From here
on any query a child performs would fail. Django raises errors like
lti (and apps.py) seems to be introduced in v7.7.0 on 11th of May 2026.
If lti/apps.py (in the celery_worker container) is changed to the following, encoding starts working
after restart of that container only and when new video is uploaded.
Searching through the logs (celery_long.log), this is the first error seen in connection
to the encodings is shown at the end of the message.
All reactions