On 05/29/2017 02:16 PM, Simon Liebold via Mailman-users wrote:
Now, I get to see the confirmation view and upon confirming I see these (luckily different) errors like below (same with Django 1.10):
Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table 'mailmansuite.django_q_ormq' doesn't exist") Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table 'mailmansuite.django_q_ormq' doesn't exist")
True, this table doesn't exist in the database. It isn't created by python manage.py migrate.
The error is served with HTTP-200. No stack trace in mailmansuite.log.
Do you have django_q in INSTALLED_APPLICATIONS in your Django config and do you have
# # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', }
in your Django config and are you running
django-admin qcluster
at startup?
See <https://mail.python.org/pipermail/mailman-developers/2017-May/026064.html>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan