[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Mark Sapiro
On 10/14/22 16:42, Martin Lorenz wrote: everything is nice and silky again ... And your site looks good to me. If you have further questions about this, please join the mailman-us...@mailman3.org list at https://lists.mailman3.org/mailman3/lists/mailman-us...@mailman3.org/ and post there.

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Martin Lorenz
everything is nice and silky again ... that's what I finally did to the database: ``` sudo -u postgres psql postgres=# \connect mailmanweb mailmanweb=# insert into django_site(id, domain, name) values (1, 'example.com', ''); INSERT 0 1 mailmanweb=# insert into django_mailman3_maildomain(id, mail

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Martin Lorenz
i think, I hit a bug I had mailman up and running, sent testmails to a testlist, used the webinterface ... but than I played around with the domains. I had added one of my domains for the test list but in the archive interface I still had "example.com" as a header. so I switched over to the

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Martin Lorenz
heureka! added two lines to the nginx config and now it seems up and running ... _location_ now looks like this: ``` location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; prox

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Martin Lorenz
thanks, that one did the trick I think I kint of got ist up and running now. this ist how the site looks: https://list.poc.im/mailman3/lists/ I don't think, it should be like that. I already added ``` location /static/ { alias /opt/mailman/web/static; } ``` to my nginx config, b

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Mark Sapiro
On 10/14/22 13:59, Martin Lorenz wrote: OK thanks for the advice. I started installing following the path ... the first error I hit is: ``` ... File "/opt/mailman/venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py", line 6, in from mistune.plugins.extra import plugin_url Mo

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Martin Lorenz
OK thanks for the advice. I started installing following the path ... the first error I hit is: ``` (venv) mailman@arda:/etc/mailman3$ mailman-web migrate Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/django/template/utils.py", line 66, in __getitem__

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Mark Sapiro
On 10/14/22 09:56, Martin Lorenz wrote: Now I will start over ... First of all: do you recommend the debian package install or the manual one? ``` Package mailman3: p 3.3.3-1

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-14 Thread Martin Lorenz
Now I will start over ... First of all: do you recommend the debian package install or the manual one? ``` Package mailman3: p 3.3.3-1 stable

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-10 Thread Mark Dale via Mailman-Users
On 2022-10-10 23:14, Stephen J. Turnbull wrote: > so I had to switch to a new provider. The new v-server is > debian-based. the release is bullseye which does still provide ... ... browse both the "venv" installation described in our docs at https://docs.mailman3.org/en/lat

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-10 Thread Stephen J. Turnbull
Martin Lorenz writes: > so I had to switch to a new provider. The new v-server is > debian-based. the release is bullseye which does still provide > python2 but lacks a few packages that are necessery to install > mailman2.1 I would have to manually install dependencies via pip > instead of

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-09 Thread Martin Lorenz
Stephen J. Turnbull wrote: > Martin Lorenz writes: > > I am afraid, mailman3 needs far too much system resources for this > > virtual server. > > This whole story doesn't make much sense to me. You switched to a new > virtual server because Mailman 2 isn't supported but imply that > Mailman 3 is,

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-08 Thread Stephen J. Turnbull
Martin Lorenz writes: > I am afraid, mailman3 needs far too much system resources for this > virtual server. This whole story doesn't make much sense to me. You switched to a new virtual server because Mailman 2 isn't supported but imply that Mailman 3 is, but you can't get support from your v

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-08 Thread Martin Lorenz
Mark Sapiro wrote: > https://www.python.org/downloads/release/python-2718/ but it would be > much better to fix your Mailman 3 issues. I am afraid, mailman3 needs far too much system resources for this virtual server. I had it up and running but system load shoot up to values beyond 10 whenever

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-07 Thread Mark Sapiro
On 10/7/22 02:27, Martin Lorenz wrote: Greetings, after many years of smoothly running a mailman2 instance I had to migrate my virtual server to a new provider. There I found, that mailman2 was no longer supported and tried to migrate to mailman3 .. with much pain and no success. Mailman3 kee

[Mailman-Users] Re: Hevy resource footprint forces backdrop to mailman 2.1

2022-10-07 Thread Bruce Johnson via Mailman-Users
If you have root or sudo access on the vm host you will need to install Python2 support via whatever mechanism the OS uses for this ( such as yum, dnf or apt for various Linux flavors ) On Oct 7, 2022, at 2:27 AM, Martin Lorenz mailto:git...@member.holoclan.de>> wrote: Greetings, after many y