Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Brian Carpenter

On 7/14/20 1:06 PM, Mark Sapiro wrote: > It's confusing, but after adjusting that setting, you need to restart > Mailman core, not gunicorn. > > If you are running a gunicorn service, that is what is providing WSGI > support for Django (Postorius and/or HyperKitty). You may be using > gunicorn for this or uWSGI or Apache mod_wsgi, but is any case, that is > not the gunicorn we are considering here. > > Regardless of what you use to provide WSGI support for Django, Mailman > core uses gunicorn to support the REST API, and that is the gunicorn > affected by the settings in the gunicorn.cfg pointed to by > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > If, with the above configuration, you do `ps -fwwA|grep runner=rest` you > will see something like: > > mailman 20582 20561 0 01:21 ? 00:00:16 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20722 20582 0 01:21 ? 00:01:19 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20725 20582 0 01:21 ? 00:01:18 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20726 20582 0 01:21 ? 00:01:18 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > mailman 20727 20582 0 01:21 ? 00:01:50 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C > /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 > > The first of these, pid 20582, is Mailman's actual REST runner. The > other 4 with parent pid 20582 are the 4 gunicorn worker processes forked > from the REST runner. > > It's the REST runner or Mailman core that needs to be restarted to pick > up that change. Thanks Mark. I knew that once but forgot it. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 2 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Odhiambo Washington

On Mon, Aug 5, 2024 at 11:55 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/5/24 12:45, Odhiambo Washington via Mailman-users wrote: > > > > Yes, those are Cloudflare IPs and I don't know why 2! > > All I know is that in DNS, I created an A record for the hostname and > chose > > the "proxy" option in the cloudflare DNS management interface. > > OK, I know nothing about how cloudflare proxying works, so ignoring that > and assuming it's OK, ... > ... > > I don't know. However, those IPs you see in the Nginx logs, none belong > to > > me! I have two possible IPs - one domiciled in KE and another domiciled > in > > the US (when I use VPN). > > I think I've misunderstood. Is it the case that the messages you report > like /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed > (2: No such file or directory) ... are in the nginx log on the mailman > server. That's correct. > If so, see > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura…. > > Is that what you have? > Yes. > If not, post your nginx configuration. > In any case, here is my virtualhost config: ``` server { if ($host = mm3-lists.kictanet.or.ke) { return 301 https://$host$request_uri; listen 80; server_name mm3-lists.kictanet.or.ke; return 301 https://mm3-lists.kictanet.or.ke$request_uri; include snippets/letsencrypt.conf; } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name mm3-lists.kictanet.or.ke; ssl_certificate /etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/privkey.pem; ssl_trusted_certificate /etc/letsencrypt/live/ mm3-lists.kictanet.or.ke/chain.pem; include snippets/ssl.conf; include snippets/letsencrypt.conf; access_log /var/log/nginx/mm3-lists_access.log; error_log /var/log/nginx/mm3-lists_error.log; location = /favicon.ico { log_not_found off; access_log off; } location = /robots.txt { allow all; log_not_found off; access_log off; } location /static/ { alias /opt/mailman/mm/static/; } location / { proxy_pass http://127.0.0.1:8010; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 1 month

[MM3-users] Re: Hyperkitty list overview error: thread matching query does not exist

by Darren Hart

On Wed, May 25, 2022 at 08:10:39AM -0700, Mark Sapiro wrote: > On 5/23/22 11:11, Darren Hart via Mailman-users wrote: > > When attempting to visit the hyperkitty archives list overview for one of my two lists: > > > > Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/ > > > > The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load). > > > > The following appears in /var/log/mailman3/web/mailman-web.log: > > > > > > ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist(a)mydomain.com/posted-to > > Traceback (most recent call last): > ... > > File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get > > raise self.model.DoesNotExist( > > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. > > > > Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads. > > > > The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views. > > > > The hyper kitty archives for a second list on this Mailman3 instance is working correctly. > > > > How can I fix this view of the archives? Or how can I get more information on what might be failing? > > > I'm not sure if this will help, but try running your django management > command with arguments `runjob recent_threads_cache`. Note that this will be > run daily if you are running the Cron Jobs for Mailman Web. See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=perio… Thank you Mark. These are in cron, but I ran this (and all the runjobs hourly,daily, etc. options), checking after each. The failure persisted until I restarted mailman3-web, and then it started working again. I'm not sure what combination of cron jobs and restarting resolved the issue, but it's running again. Thanks again. -- Darren Hart Ampere Computing / OS and Kernel

3 years, 3 months

[MM3-users] Re: new list not working

by Christian

See below please... -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, March 10, 2023 7:02 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/10/23 05:07, Christian via Mailman-users wrote: > There are no such messages as you describe. > > After turning on debugging I got this from a test message sent to the > new > list: > > Mar 10 04:39:51 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Mar 10 04:39:51 2023 (1005) Peer: ('127.0.0.1', 51982) Mar 10 04:39:51 > 2023 (1005) ('127.0.0.1', 51982) handling connection Mar 10 04:39:51 > 2023 (1005) ('127.0.0.1', 51982) >> b'LHLO > zarathustra.ccalternatives.org' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'MAIL > FROM:<christian(a)naturalintelligence.us> SIZE=3499' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) sender: > christian(a)naturalintelligence.us > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'RCPT > TO:<redlatinleg(a)lists.ccalternatives.org>' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) recip: > redlatinleg(a)lists.ccalternatives.org > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'DATA' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'QUIT' > Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) connection lost Mar > 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) Connection lost during > _handle_client() Again, that's only the post being delivered to Mailman. What comes after that in the log? Mar 10 08:39:28 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:39:28 2023 (1005) Peer: ('127.0.0.1', 55662) Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) handling connection Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'MAIL FROM:<christian(a)naturalintelligence.us> SIZE=3498' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) sender: christian(a)naturalintelligence.us Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) recip: redlatinleg(a)lists.ccalternatives.org Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'DATA' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'QUIT' Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) connection lost Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) Connection lost during _handle_client() Mar 10 08:44:05 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:44:05 2023 (1005) Peer: ('127.0.0.1', 54800) Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) handling connection Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'MAIL FROM:<> SIZE=1139191' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) sender: <> Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'RCPT TO:<medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org>' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) recip: medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'DATA' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'QUIT' Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) connection lost Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) Connection lost during _handle_client() Mar 10 08:45:15 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 08:45:15 2023 (1005) Peer: ('127.0.0.1', 38820) Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) handling connection Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'MAIL FROM:<> SIZE=1155595' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) sender: <> Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'RCPT TO:<medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org> ' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) recip: medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'DATA' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'QUIT' Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) connection lost Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) Connection lost during _handle_client() And have you checked if Mailman's out runner is running? Note that if it died for some reason and wasn't restarted or used up its restarts, restarting Mailman core won't start it. You need to stop Mailman core and then start it. OK I DID THAT Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories? root@zarathustra:/opt/mailman/mm/var# ls -la queue/out total 4416 drwxrwx--- 2 mailman mailman 4096 Mar 10 04:44 . drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. -rw-rw---- 1 mailman mailman 1126829 Mar 10 04:39 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak -rw-rw---- 1 mailman mailman 1083682 Mar 8 20:00 1678334445.1113052+b43224b03f1ba2aa2610301331195b0cbaa151b7.pck -rw-rw---- 1 mailman mailman 1083744 Mar 8 20:00 1678334445.1324928+10c5ec711b7a4364407685b7899a9e8ea25a1a8b.pck -rw-rw---- 1 mailman mailman 1083680 Mar 8 20:00 1678334445.1501603+f2d2895ae7fa80ad387df77ffa17361294fe781c.pck -rw-rw---- 1 mailman mailman 2922 Mar 9 07:49 1678376944.9032273+9923c3da8724cff6ff71b585d1971a90a0ae65cb.pck -rw-rw---- 1 mailman mailman 2862 Mar 9 07:49 1678376944.9125621+2635b96fc6cd2ebb98a2c60a269d07517c1f5046.pck -rw-rw---- 1 mailman mailman 2886 Mar 9 07:57 1678377458.4585488+73f68f6f05d6ee64020e05c8ba2569378e4238f0.pck -rw-rw---- 1 mailman mailman 6600 Mar 9 07:59 1678377564.335885+63793d373c7668947ce4ef2c4a89644ba288d775.pck -rw-rw---- 1 mailman mailman 8290 Mar 9 08:25 1678379122.8619912+bfba87ac1c5e97473ea9c9645a99719d11179308.pck -rw-rw---- 1 mailman mailman 5966 Mar 9 08:48 1678380525.743866+d6f70271750015293a249f9ffae8200367eee509.pck -rw-rw---- 1 mailman mailman 6124 Mar 9 13:01 1678395691.1910245+9e087862cd317d77af8586d5390d60d483af8123.pck -rw-rw---- 1 mailman mailman 2789 Mar 9 13:31 1678397516.4386168+14bb385ad36166aef4a23e1d2b9dd92b50af254d.pck -rw-rw---- 1 mailman mailman 2752 Mar 9 13:31 1678397516.4514658+00546161e5310c988ca3b4d0be4c4a96d3295969.pck -rw-rw---- 1 mailman mailman 2321 Mar 9 13:58 1678399097.1614358+b7b3bfa9cdef9ada94045eed945862664aff065e.pck -rw-rw---- 1 mailman mailman 2390 Mar 9 13:58 1678399097.172284+7188ab4729863b3781c0890ec3b1be7de642454a.pck -rw-rw---- 1 mailman mailman 6031 Mar 9 14:07 1678399672.4968731+2caeb7c82672c9051be407b1cdb7a8b21a87d348.pck -rw-rw---- 1 mailman mailman 2095 Mar 9 14:08 1678399689.8167183+199b2da6cd1f8a00d10c1cd79ccc6cbcb4bdd503.pck -rw-rw---- 1 mailman mailman 7179 Mar 9 14:08 1678399689.8327854+a8d1dc73e5979bde43dccf48caa9bc58de575f41.pck -rw-rw---- 1 mailman mailman 8357 Mar 9 14:19 1678400356.5360696+62b6dce2428e420d6cb53c337c61db69a6fe4d44.pck -rw-rw---- 1 mailman mailman 5939 Mar 9 14:28 1678400903.3894706+d3f5dad6c67057edd0f2888e193dd71de14d2bf9.pck -rw-rw---- 1 mailman mailman 2096 Mar 10 04:43 1678452191.4875023+2e00a89aa5454f965d35a7b8be6a4f620944b8a1.pck -rw-rw---- 1 mailman mailman 7181 Mar 10 04:43 1678452191.4984088+1fd6f3aff9ef79aff269f4edc920f2424a8b35b7.pck -rw-rw---- 1 mailman mailman 6036 Mar 10 04:44 1678452252.847286+552f758b7fca32c2f082bd922f68de1f850dec2d.pck root@zarathustra:/opt/mailman/mm/var# ls -la queue/shunt total 12 drwxrwx--- 2 mailman mailman 4096 Mar 8 12:07 . drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. -rw-rw---- 1 mailman mailman 447 Apr 26 2021 1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck You say that only the new list and one other have this issue, but I wonder if the issue is not with specific lists, but rather with posts after a certain time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ JNZIPCHBZIUUAO5KAQEWQX3UPZ7CZYPV/ This message sent to csa(a)web-analysts.net

2 years, 6 months

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Florian Schulze

On 2 Jul 2020, at 8:38, Florian Schulze wrote: > On 30 Jun 2020, at 8:22, Florian Schulze wrote: > >> On 29 Jun 2020, at 23:40, Mark Sapiro wrote: >> >>> On 6/29/20 1:38 AM, Florian Schulze wrote: >>>> Hi! >>>> >>>> After upgrading to HyperKitty 1.3.x I get the following error for >>>> qcluster: >>>> >>>> File ".../lib/python3.7/site-packages/django_q/cluster.py", line >>>> 300, >>>> in pusher >>>> task = SignedPackage.loads(task[1]) >>>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>>> 31, >>>> in loads >>>> serializer=PickleSerializer) >>>> File ".../lib/python3.7/site-packages/django_q/core_signing.py", >>>> line >>>> 38, in loads >>>> return serializer().loads(data) >>>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>>> 44, >>>> in loads >>>> return pickle.loads(data) >>>> AttributeError: Can't get attribute 'process_task_result' on >>>> <module >>>> 'hyperkitty.tasks' from >>>> '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> >>>> >>>> How do I recover from that? It seems like there are still persisted >>>> tasks in the qcluster queue using the old code from 1.2.x with the >>>> old >>>> locking implementation. >>> >>> Have you stopped ans started qcluster since upgrading? >> >> Yes >> >>> Are you running the Django periodic jobs? >> >> They were disabled because of the errors (someone else did the >> upgrade). I have enabled them again and will watch it and report >> back. > > The cronjobs seem to work fine, no errors so far. > > The queue doesn't seem to change at all. In "qmonitor" there is > nothing listed and the statusline remains the same at > ORM default Queued 303(118) > Success 100 Failures > 0 I managed to figure out how to inspect the queue in the admin interface. I just deleted all the repeatedly failing tasks and ran all cron jobs. I hope it is fine now. Regards, Florian Schulze

5 years, 2 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Abhilash Raj

On 12/14/22 03:31, Mark Sapiro wrote: > On 12/13/22 10:38, Dan Caballero wrote: >> Hi Mark, >> >> I ran the commands and it took about 35 seconds for the loop to run. >> >> Here's the result. >> >>>>> count >> 4168 > > > So that's at least part of the issue. How does 35 seconds compare to the > length of time to process one moderated message through Postorius? > Probably should've read more of the thread before previous reply ;-) So, the issue _could_ be due to latency to the remote database vs local database that we have on m.p.o. Mailman3 is not very efficient when it comes to total no. of database queries done per operation, which is something I have been (very slowly) tracking and fixing on a case-by-case basis. So, for example, handling 1 held message in m.p.o made 1.1k postgres database calls in total and even though they were each only few hundred micro-seconds each, the total added up to roughly ~2sec avg response time on the handle message API endpoint. If you handle more than 1, it scales linearly. My suspicion is that in your case Dan, due to a remote instance, the latency per call is higher (maybe in the order of few or 10s of milliseconds is my guess?) and then depending on the total no. of entries you have in pendings and pendedkeyvalue tables (with some filters, not _all_ entries), it adds up to a high value. The no. of database calls here is of order n^2, where n is the entries in pendings of type "held message" and "data" and their respective linked relationships in pendedkeyvalue table. My MR makes it such that we don't need to scan all entries of "type"="data", so that part will become constant time. And the pending of type "held message" will be limited to no. of held messages in a single MailingList(compared to all mailing lists like today), so it will help depending on the distribution of held messages in various lists. I am also exploring ways to make that 2nd query also constant time. -- thanks, Abhilash Raj (maxking)

2 years, 9 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

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(a)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(a)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(a)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(a)msapiro.net> The highway is for gamblers, > > >> San Francisco Bay Area, California better use your sense - B. > > >Dylan > > >> _______________________________________________ > > >> Mailman-users mailing list -- mailman-users(a)mailman3.org > > >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >> > > >_______________________________________________ > > >Mailman-users mailing list -- mailman-users(a)mailman3.org > > >To unsubscribe send an email to mailman-users-leave(a)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) >

6 years, 6 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Sun, 23 Oct 2022 08:00:19 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/22/22 21:29, Onyeibo Oku wrote: > > > > Now Mailman starts, and stops as desired when running as mailman > > user (both in virtual and non-virtual environments). However, > > running the service via systemd still fails. I now get a different > > traceback: > > > > Oct 23 03:43:00 mail.server.tld mailman[19410]: Traceback (most > > recent call last): > ... > > Oct 23 03:43:00 mail.server.tld mailman[19410]: with > > open(self._claimfile, 'w') as fp: Oct 23 03:43:00 mail.server.tld > > mailman[19410]: PermissionError: [Errno 13] Permission denied: > > '/opt/mailman/mm/var/locks/mailman-cfg.lck|server.tld|19410|619270043958240354' > > Oct 23 03:43:00 mail.server.tld systemd[1]: mailman3.service: > > Control process exited, code=exited, status=1/FAILURE > > What are ownership and permissions on /opt/mailman/mm/var/locks/ > > Assuming they are > > drwxr-xr-x mailman mailman > > it must be the case that systemd is not running the > `/opt/mailman/venv/bin/mailman start` command as the `mailman` user. > I suspect this is a Fedora issue. I note that > https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administe… > does not mention User or Group. You might try replacing > ``` > ExecStart=/opt/mailman/venv/bin/mailman start > ExecReload=/opt/mailman/venv/bin/mailman restart > ExecStop=/opt/mailman/venv/bin/mailman stop > > with > > ExecStart=sudo -u mailman /opt/mailman/venv/bin/mailman start > ExecReload=sudo -u mailman /opt/mailman/venv/bin/mailman restart > ExecStop=sudo -u mailman /opt/mailman/venv/bin/mailman stop > ``` > This does not work. Systemd says it cannot find sudo (file). After updating in the commands "sudo" to "/bin/sudo" afterwards Systemd throws a different error message: PermissionError on /bin/sudo This is tiring. At this moment I am left with the possibility that SELinux may be in the way. I cannot think of a way to prove this hypothesis. This is speculation. Perhaps I should try another installation method other than Virtual. I found Mailman3 in Fedora repository. Yes, it is packaged. May be I should try that or perhaps I should try the git version. I'd be happy to have a functioning Mailman before Friday. Regards Onyeibo

2 years, 10 months

[MM3-users] Re: Archive search failing on one list

by Mark

On Sat, 2023-09-23 at 20:28 -0700, Mark Sapiro wrote: > > What if you do something like the following where django-admin is > whatever command you use for the Django admin command. > ``` > $ django-admin shell > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more > information. > (InteractiveConsole) > >>> from hyperkitty.models.mailinglist import MailingList > >>> mlist_name = 'listname(a)domain.com' > >>> mlist = MailingList.objects.get(name=mlist_name) > >>> mlist > <MailingList listname(a)domain.com (listname.domain.com)> > >>> > ``` Hi Mark, I'm still on this problem of one list's archive-search not returning any results. I created a new list today and it also has the same problem. In short, the older lists all seem fine -- their search results are up- to-date so that tells me the cron is okay. It's just these 2 newer lists that have the problem. It's taken me while to get my head around the Django admin command you have suggested, as I kept getting an error when starting: #django-admin shell >>> from hyperkitty.models.mailinglist import MailingList ... django.core.exceptions.ImproperlyConfigured ... That sent me down a rabbit hole which I haven't emerged from yet. But instead, starting with # python3 manage.py shell ... # python3 manage.py shell Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models.mailinglist import MailingList >>> mlist_name = 'thepost(a)example.com' >>> mlist = MailingList.objects.get(name=mlist_name) >>> mlist <MailingList: <MailingList thepost(a)example.com>> >>> The format of my final line is different to yours ... Mine: <MailingList: <MailingList thepost(a)example.com>> Yours: <MailingList listname(a)domain.com (listname.domain.com)> Does this (missing list_id) give any clue as to why the archive-search isn't working, or is just that starting with "# python3 manage.py shell" is the wrong thing to do? By the way, the list_id shows correctly in the SQL query result. select * from hyperkitty_mailinglist where name like 'thepost(a)example.com'; ... name | thepost(a)example.com | list_id | thepost.example.com ... Any ideas appreciated. Mark

1 year, 11 months

[MM3-users] Re: Templates

by David Krantz

On Sat, Sep 23, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > Have you tried restarting/reloading whatever dbm (MySQL, PostgreSQL, ?) > you are using? No, that would have been strange to me; the table in the database was up to date. But now I tried that, I got no effect this time but I probably could set up a better test. I also had another problem [solved]: I get the error message "Multiple rows were found for one_or_none" when I try TemplateManager.get(name, context) for the list. There is only one matching row in the templates table so something is fishy with the ORM. This occured when I changed to the previous uri value. As the database does not have any duplicates in the templates table I suspect either a broken join or that the cache retains the old value. The traceback looks like this in the mailman shell: >>> tm.get('list:member:regular:footer', 'test.example.com') Traceback (most recent call last): File "<console>", line 1, in <module> File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/template.py", line 98, in get contents = cache_mgr.get(actual_uri) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/cache.py", line 125, in get CacheEntry.key == key).one_or_none() File ".../venv-3.5/lib/python3.5/site-packages/SQLAlchemy-1.2.0b2-py3.5-linux-x86_64.egg/sqlalchemy/orm/query.py", line 2814, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Workaround: Delete cached files in .../var/cache and run delete from file_cache in postgresql. Then that works again. The culprit was that the file got cached twice so there is a bug in the cache function. I used the ITemplateManager-util in the shell to cause the problem. >> 2. the $user_delivered_to and $user_email do not expand for some >> reason. Known problem? > > > These require that the list delivery be personalized. See > <http://mailman.readthedocs.io/en/latest/src/mailman/runners/docs/outgoing.h…>. > That explains things. Thank you! Now I got two footers, first one without personalisation and one personalised. Interesting. best regards // David

7 years, 11 months

Search results for query "sapiro"