Hi Abhilash,

Thank you for the explanation, I've created a report: https://github.com/maxking/docker-mailman/issues/307

Danil

сб, 16 февр. 2019 г. в 18:40, Abhilash Raj maxking@asynchronous.in:

On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote:

...

Hi,

I'm interesting in Mailman3 deployment with archiving feature completely disabled.

I've tried to deploy Core + Postorius using this docker-compose template:

https://github.com/maxking/docker-mailman/blob/master/docker-compose-postori...

...

Unfortunately Postorius version came with this template is quite

outdated:

...

1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker image I see version 1.2.3.

I've also checked image maxking/postorius:rolling but it seems irrelevant/broken (container exits with error).

Are there newer Postorius docker image I can use?

No, but if you could report the failure and error that you, maybe the Maintainer can help fix that issue you have?

P.S. I maintain those images. The Postorius image is kind of neglected since there are fewer people using it, but I'd be happy to fix any error that you see.

Package ugprades are merely a version number bump in Dockerfile :)

-- thanks, Abhilash Raj (maxking)

Hi,

After upgrading my PostgreSQL from 9.2 to 9.6, I was able to up postorius container. But when I try to open UI, I'm getting 500 Internal Server Error all the time - either for /postorius/lists/ as well as for /admin/. I've checked all the logs but haven't found anything there which can bring some light at the issue. Just error 500...

I've checked:

• nginx logs: just error 500
• mailman-web docker container logs: no errors
• mailman-web (postorius) logs: mailmanweb.log is empty, uwsgi*.log with some errors
• mailman-core logs: no errors

I've also called curl localhost:8000 from inside the mailman-web container and got the same 500 Internal Server Error.

Could you guys advise what else should I check?

With my best regards, Danil

пт, 22 февр. 2019 г. в 09:12, Danil Smirnov danil@smirnov.la:

Hi Abhilash,

Thank you for the quick resolution, but I'm still unable t start the container: https://github.com/maxking/docker-mailman/issues/309

DB migrations are failing.

Danil

вс, 17 февр. 2019 г. в 12:21, Danil Smirnov danil@smirnov.la:

...

Hi Abhilash,

Thank you for the explanation, I've created a report: https://github.com/maxking/docker-mailman/issues/307

Danil

сб, 16 февр. 2019 г. в 18:40, Abhilash Raj maxking@asynchronous.in:

...

On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote:

...

Hi,

I'm interesting in Mailman3 deployment with archiving feature completely disabled.

I've tried to deploy Core + Postorius using this docker-compose template:

https://github.com/maxking/docker-mailman/blob/master/docker-compose-postori...

...

Unfortunately Postorius version came with this template is quite

outdated:

...

1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker image I see version 1.2.3.

I've also checked image maxking/postorius:rolling but it seems irrelevant/broken (container exits with error).

Are there newer Postorius docker image I can use?

No, but if you could report the failure and error that you, maybe the Maintainer can help fix that issue you have?

P.S. I maintain those images. The Postorius image is kind of neglected since there are fewer people using it, but I'd be happy to fix any error that you see.

Package ugprades are merely a version number bump in Dockerfile :)

-- thanks, Abhilash Raj (maxking)

Hi Abhilash,

ср, 27 февр. 2019 г. в 22:21, Abhilash Raj maxking@asynchronous.in:

So, what errors are you looking at in uwsgi*.log?

There are tons of errors like this:

Unknown command: 'qcluster' Type 'manage.py help' for usage. [uwsgi-daemons] respawning "./manage.py qcluster" (uid: 100 gid: 101) Unknown command: 'qcluster' Type 'manage.py help' for usage. [uwsgi-daemons] throttling "./manage.py qcluster" for 26 seconds

Do you see any successful requests in mailman core's mailman.log?

Nope, just 'runner started.' entries.

Danil

With my best regards, Danil

пт, 22 февр. 2019 г. в 09:12, Danil Smirnov danil@smirnov.la:

Hi Abhilash,

Thank you for the quick resolution, but I'm still unable t start the container: https://github.com/maxking/docker-mailman/issues/309

DB migrations are failing.

Danil

вс, 17 февр. 2019 г. в 12:21, Danil Smirnov danil@smirnov.la:

Hi Abhilash,

Thank you for the explanation, I've created a report: https://github.com/maxking/docker-mailman/issues/307

Danil

сб, 16 февр. 2019 г. в 18:40, Abhilash Raj maxking@asynchronous.in:

On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote:

...

Hi,

I'm interesting in Mailman3 deployment with archiving feature completely disabled.

I've tried to deploy Core + Postorius using this docker-compose template:

https://github.com/maxking/docker-mailman/blob/master/docker-compose-postori...

...

Unfortunately Postorius version came with this template is quite

outdated:

...

1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker image I see version 1.2.3.

I've also checked image maxking/postorius:rolling but it seems irrelevant/broken (container exits with error).

Are there newer Postorius docker image I can use?

No, but if you could report the failure and error that you, maybe the Maintainer can help fix that issue you have?

P.S. I maintain those images. The Postorius image is kind of neglected since there are fewer people using it, but I'd be happy to fix any error that you see.

Package ugprades are merely a version number bump in Dockerfile :)

-- thanks, Abhilash Raj (maxking)

-- thanks, Abhilash Raj (maxking)

Hi Mark,

Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow.

Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image.

The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error...

Now answering your questions:

ср, 27 февр. 2019 г., 22:56 Mark Sapiro mark@msapiro.net:

do you have django-q in INSTALLED_APPS in your Django settings and what is set for Q_CLUSTER?

I've checked settings.py inside the container and I haven't found any of the mentioned configurations there.

Does the manage.py that's being run here point to the right settings.py?

No clue.

Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image?

https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web/...

Danil

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On February 27, 2019 11:53:34 PM PST, Danil Smirnov danil@smirnov.la wrote:

Hi Mark,

Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow.

Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image.

The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error...

Now answering your questions:

ср, 27 февр. 2019 г., 22:56 Mark Sapiro mark@msapiro.net:

...

do you have django-q in INSTALLED_APPS in your Django settings and what is set for Q_CLUSTER?

I've checked settings.py inside the container and I haven't found any of the mentioned configurations there.

Does the manage.py that's being run here point to the right settings.py?

...

No clue.

Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image?

https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web/...

Because I am a dum dum ;-)

Will work on removing those crons and stuff. Would be nice if you opened an issue on Github so that I don't forget.

Danil

...

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Hi Abhilash,

Thank you very much - the previous error is fixed now.

But I have another one now, which causes the same 500 Server Error:

bash-4.3# cat /opt/mailman-web-data/logs/uwsgi-error.log *** Starting uWSGI 2.0.18 (64bit) on [Fri Mar 1 05:42:09 2019] *** compiled with version: 6.3.0 on 01 March 2019 01:52:42 os: Linux-3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 UTC 2017 nodename: mailman-web machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /opt/mailman-web detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! setgid() to 101 setuid() to 100 chdir() to /opt/mailman-web your memory page size is 4096 bytes detected max file descriptor number: 1048576 building mime-types dictionary from file /etc/mime.types...1168 entry found lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 Python version: 3.6.8 (default, Jan 30 2019, 23:58:16) [GCC 6.3.0] Python main interpreter initialized at 0x55a2df7f57e0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 20, in import_string return getattr(module, class_name) AttributeError: module 'django.contrib.auth.middleware' has no attribute 'SessionAuthenticationMiddleware'

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "wsgi.py", line 38, in <module> application = get_wsgi_application() File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application return WSGIHandler() File "/usr/local/lib/python3.6/site-packages/django/core/handlers/wsgi.py", line 136, in __init__ self.load_middleware() File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 34, in load_middleware middleware = import_string(middleware_path) File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 24, in import_string ) from err ImportError: Module "django.contrib.auth.middleware" does not define a "SessionAuthenticationMiddleware" attribute/class unable to load app 0 (mountpoint='') (callable not found or import error) *** no app loaded. going in full dynamic mode *** *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 1) spawned uWSGI worker 1 (pid: 37, cores: 2) --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors ---

As per my investigation, this error possibly caused by Django upgrade:

*The SessionAuthenticationMiddleware class is removed. It provided no functionality since session authentication is unconditionally enabled in Django 1.10.*

See https://docs.djangoproject.com/en/2.0/releases/2.0/

After I've removed the line https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web/... from settings.py, the container is finally working.

I've placed PR in github: https://github.com/maxking/docker-mailman/pull/314

Thank you for your help.

Danil

пт, 1 мар. 2019 г. в 04:33, Abhilash Raj maxking@asynchronous.in:

On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote:

...

On February 27, 2019 11:53:34 PM PST, Danil Smirnov danil@smirnov.la wrote:

...

Hi Mark,

Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow.

Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image.

The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error...

Now answering your questions:

ср, 27 февр. 2019 г., 22:56 Mark Sapiro mark@msapiro.net:

...

do you have django-q in INSTALLED_APPS in your Django settings and what is set for Q_CLUSTER?

I've checked settings.py inside the container and I haven't found any of the mentioned configurations there.

Does the manage.py that's being run here point to the right settings.py?

...

No clue.

Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image?

https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web/...

Because I am a dum dum ;-)

Will work on removing those crons and stuff. Would be nice if you opened an issue on Github so that I don't forget.

Should now be fixed in the latest image.

...

...

Danil

...

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- thanks, Abhilash Raj (maxking)

Test email to check something, please ignore.

Abhilash

On Fri, Mar 1, 2019, at 5:19 PM, Abhilash Raj wrote:

On Thu, Feb 28, 2019, at 10:18 PM, Danil Smirnov wrote:

...

Hi Abhilash,

Thank you very much - the previous error is fixed now.

But I have another one now, which causes the same 500 Server Error:

bash-4.3# cat /opt/mailman-web-data/logs/uwsgi-error.log *** Starting uWSGI 2.0.18 (64bit) on [Fri Mar 1 05:42:09 2019] *** compiled with version: 6.3.0 on 01 March 2019 01:52:42 os: Linux-3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 UTC 2017 nodename: mailman-web machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /opt/mailman-web detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! setgid() to 101 setuid() to 100 chdir() to /opt/mailman-web your memory page size is 4096 bytes detected max file descriptor number: 1048576 building mime-types dictionary from file /etc/mime.types...1168 entry found lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 Python version: 3.6.8 (default, Jan 30 2019, 23:58:16) [GCC 6.3.0] Python main interpreter initialized at 0x55a2df7f57e0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 20, in import_string return getattr(module, class_name) AttributeError: module 'django.contrib.auth.middleware' has no attribute 'SessionAuthenticationMiddleware'

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "wsgi.py", line 38, in <module> application = get_wsgi_application() File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application return WSGIHandler() File "/usr/local/lib/python3.6/site-packages/django/core/handlers/wsgi.py", line 136, in __init__ self.load_middleware() File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 34, in load_middleware middleware = import_string(middleware_path) File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 24, in import_string ) from err ImportError: Module "django.contrib.auth.middleware" does not define a "SessionAuthenticationMiddleware" attribute/class unable to load app 0 (mountpoint='') (callable not found or import error) *** no app loaded. going in full dynamic mode *** *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 1) spawned uWSGI worker 1 (pid: 37, cores: 2) --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors ---

As per my investigation, this error possibly caused by Django upgrade:

*The SessionAuthenticationMiddleware class is removed. It provided no functionality since session authentication is unconditionally enabled in Django 1.10.*

See https://docs.djangoproject.com/en/2.0/releases/2.0/

After I've removed the line https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web/... from settings.py, the container is finally working.

I've placed PR in github: https://github.com/maxking/docker-mailman/pull/314

Thank you for your contributions!

I have merged your pull request and it should now be out (hopefully!).

...

Thank you for your help.

Danil

пт, 1 мар. 2019 г. в 04:33, Abhilash Raj maxking@asynchronous.in:

...

On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote:

...

On February 27, 2019 11:53:34 PM PST, Danil Smirnov danil@smirnov.la wrote:

...

Hi Mark,

Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow.

Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image.

The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error...

Now answering your questions:

ср, 27 февр. 2019 г., 22:56 Mark Sapiro mark@msapiro.net:

...

do you have django-q in INSTALLED_APPS in your Django settings and what is set for Q_CLUSTER?

I've checked settings.py inside the container and I haven't found any of the mentioned configurations there.

Does the manage.py that's being run here point to the right settings.py?

...

No clue.

Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image?

https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web/...

Because I am a dum dum ;-)

Will work on removing those crons and stuff. Would be nice if you opened an issue on Github so that I don't forget.

Should now be fixed in the latest image.

...

...

Danil

...

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- thanks, Abhilash Raj (maxking)

-- thanks, Abhilash Raj (maxking)

-- thanks, Abhilash Raj (maxking)

On Sat, Mar 2, 2019, at 1:09 AM, Danil Smirnov wrote:

Thank you very much Abhilash!

Could you set up 'latest' tag in postotius repo https://hub.docker.com/r/maxking/postorius/tags please - as it exists for core/web? I'd like to have consistent approach across the images...

Done, triggered a build on Dockerhub.

docker.io/maxking/postorius:latest

This should be available when the build is done.

Also it would be really great to extend image labelling used for *quay.io/maxking/mailman-*:rolling* images to Docker Hub ones... Version identification is quite hard for Docker...

rolling tags should be available on DockerHub too. They are replicated on both registries.

With my best regards, Danil

сб, 2 мар. 2019 г. в 03:19, Abhilash Raj maxking@asynchronous.in:

...

__

On Thu, Feb 28, 2019, at 10:18 PM, Danil Smirnov wrote:

...

Hi Abhilash,

Thank you very much - the previous error is fixed now.

But I have another one now, which causes the same 500 Server Error:

bash-4.3# cat /opt/mailman-web-data/logs/uwsgi-error.log *** Starting uWSGI 2.0.18 (64bit) on [Fri Mar 1 05:42:09 2019] *** compiled with version: 6.3.0 on 01 March 2019 01:52:42 os: Linux-3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 UTC 2017 nodename: mailman-web machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /opt/mailman-web detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! setgid() to 101 setuid() to 100 chdir() to /opt/mailman-web your memory page size is 4096 bytes detected max file descriptor number: 1048576 building mime-types dictionary from file /etc/mime.types...1168 entry found lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 Python version: 3.6.8 (default, Jan 30 2019, 23:58:16) [GCC 6.3.0] Python main interpreter initialized at 0x55a2df7f57e0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 20, in import_string return getattr(module, class_name) AttributeError: module 'django.contrib.auth.middleware' has no attribute 'SessionAuthenticationMiddleware'

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "wsgi.py", line 38, in <module> application = get_wsgi_application() File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application return WSGIHandler() File "/usr/local/lib/python3.6/site-packages/django/core/handlers/wsgi.py", line 136, in __init__ self.load_middleware() File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 34, in load_middleware middleware = import_string(middleware_path) File "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", line 24, in import_string ) from err ImportError: Module "django.contrib.auth.middleware" does not define a "SessionAuthenticationMiddleware" attribute/class unable to load app 0 (mountpoint='') (callable not found or import error) *** no app loaded. going in full dynamic mode *** *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 1) spawned uWSGI worker 1 (pid: 37, cores: 2) --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors --- --- no python application found, check your startup logs for errors ---

As per my investigation, this error possibly caused by Django upgrade:

*The SessionAuthenticationMiddleware class is removed. It provided no functionality since session authentication is unconditionally enabled in Django 1.10.*

See https://docs.djangoproject.com/en/2.0/releases/2.0/

After I've removed the line https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web/... from settings.py, the container is finally working.

I've placed PR in github: https://github.com/maxking/docker-mailman/pull/314

Thank you for your contributions!

I have merged your pull request and it should now be out (hopefully!).

...

Thank you for your help.

Danil

пт, 1 мар. 2019 г. в 04:33, Abhilash Raj maxking@asynchronous.in:

...

On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote:

...

On February 27, 2019 11:53:34 PM PST, Danil Smirnov danil@smirnov.la wrote:

...

Hi Mark,

Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow.

Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image.

The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error...

Now answering your questions:

ср, 27 февр. 2019 г., 22:56 Mark Sapiro mark@msapiro.net:

> do you have django-q in INSTALLED_APPS in your Django settings and what > is set for Q_CLUSTER? >

I've checked settings.py inside the container and I haven't found any of the mentioned configurations there.

Does the manage.py that's being run here point to the right settings.py? >

No clue.

Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image?

https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web/...

Because I am a dum dum ;-)

Will work on removing those crons and stuff. Would be nice if you opened an issue on Github so that I don't forget.

Should now be fixed in the latest image.

...

...

Danil

> -- > Mark Sapiro mark@msapiro.net The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users@mailman3.org > To unsubscribe send an email to mailman-users-leave@mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- thanks, Abhilash Raj (maxking)

-- thanks, Abhilash Raj (maxking)

-- thanks, Abhilash Raj (maxking)

On Sun, Mar 3, 2019, at 8:03 AM, Danil Smirnov wrote:

Hi Abhilash,

сб, 2 мар. 2019 г. в 21:22, Abhilash Raj maxking@asynchronous.in:

...

__ Done, triggered a build on Dockerhub.

Cool, thanks!

...

rolling tags should be available on DockerHub too. They are replicated on both registries.

Ah, I see - I mean if we can have then on 'latest' tag too?...

All the images should be available in both registry.

• latest images basically use the stable released version of Mailman and are re-built on every commit.
• rolling images track the git head and are built on every commit and also every night.

Danil

-- thanks, Abhilash Raj (maxking)