Compose hangs at [uWSGI] getting INI configuration from /opt/mailman-web/uwsgi.ini

[BearGFR]

Attempting to bring up containerized mailman/mailman-web following the instructions at https://asynchronous.in/docker-mailman/

Everything seems to progress more or less normally, then everything stops/hangs after the message:

             [uWSGI] getting INI configuration from /opt/mailman-web/uwsgi.ini

No matter how long I let it sit, it never gets past that.

[maxking]

The next step is the container waiting for the database to be up and running, is your database container and up and running fine?

[BearGFR]

Yes, they are. I can see that the database and tables have been initialized and loaded.
Here are some snippets from the container log.

`Nov 02 08:25:05 RHEL01.(mydomain) (mycontainer)[479382]: MySQL is up - continuing
Nov 02 08:25:05 RHEL01.(mydomain) (mycontainer)[479382]: Creating log file for mailman web
Nov 02 08:25:05 RHEL01.(mydomain) (mycontainer)[479382]: Creating log file for uwsgi..
Nov 02 08:25:05 RHEL01.(mydomain) (mycontainer)[479382]: settings_local.py not found, it is highly recommended that you provide one
Nov 02 08:25:05 RHEL01.(mydomain) (mycontainer)[479382]: Using default configuration to run.
Nov 02 08:25:06 RHEL01.(mydomain) (mycontainer)[479382]: Compiling locale files in /usr/lib/python3.8/site-packages
Nov 02 08:25:07 RHEL01.(mydomain) (mycontainer)[479382]: processing file django.po in /usr/lib/python3.8/site-packages/django/contrib/flatpages/locale/udm/LC_MESSAGES
Nov 02 08:25:07 RHEL01.(mydomain) (mycontainer)[479382]: processing file django.po in /usr/lib/python3.8/site-packages/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
Nov 02 08:25:07 RHEL01.(mydomain) (mycontainer)[479382]: processing file django.po in /usr/lib/python3.8/site-packages/django/contrib/flatpages/locale/cy/LC_MESSAGES
Nov 02 08:25:07 RHEL01.(mydomain) (mycontainer)[479382]: processing file django.po in /usr/lib/python3.8/site-packages/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
.
.
.
.
Nov 02 08:25:12 RHEL01.(mydomain) (mycontainer)[479382]: /opt/mailman-web
Nov 02 08:25:14 RHEL01.(mydomain) (mycontainer)[479382]: Compressing... done
Nov 02 08:25:14 RHEL01.(mydomain) (mycontainer)[479382]: Compressed 2 block(s) from 126 template(s) for 0 context(s).
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Operations to perform:
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, openid, postorius, sessions, sites, socialaccount
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Running migrations:
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying contenttypes.0001_initial... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying auth.0001_initial... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying account.0001_initial... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying account.0002_email_max_length... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying admin.0001_initial... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying admin.0002_logentry_remove_auto_add... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying admin.0003_logentry_add_action_flag_choices... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying contenttypes.0002_remove_content_type_name... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying auth.0002_alter_permission_name_max_length... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying auth.0003_alter_user_email_max_length... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying auth.0004_alter_user_username_opts... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying auth.0005_alter_user_last_login_null... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying auth.0006_require_contenttypes_0002... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying auth.0007_alter_validators_add_error_messages... OK
.
.
.

Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying postorius.0011_auto_20191109_1219... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying postorius.0012_auto_20200420_2136... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying postorius.0013_auto_20201116_0058... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying sessions.0001_initial... OK
Nov 02 08:25:54 RHEL01.(mydomain) (mycontainer)[479382]: Applying sites.0002_alter_domain_unique... OK
Nov 02 08:25:55 RHEL01.(mydomain) (mycontainer)[479382]: Creating admin user admin ...
Nov 02 08:25:56 RHEL01.(mydomain) (mycontainer)[479382]: Superuser created successfully.
Nov 02 08:25:56 RHEL01.(mydomain) (mycontainer)[479382]: Setting mmweb.(mydomain) as the default domain ...
Nov 02 08:25:57 RHEL01.(mydomain) (mycontainer)[479382]: [uWSGI] getting INI configuration from /opt/mailman-web/uwsgi.ini
`

...and that's where everything hangs. There are no more messages after that.

[BearGFR]

Perusing the logs after I persisted them, I found a message in uwsgi-error.log:

       MySQLdb._exceptions.OperationalError: (2013, 'Lost connection to MySQL server during query')

I don't understand how that could be because the other components of mailmanweb that ran ahead of this were clearly able to access and update the database?

[BearGFR]

No ideas I guess?

[maxking]

I don't have any great ideas why something like this would happen. Can you try it out with some other versions of mysql to see if this is an isolated issue?