Broken web interface Ubuntu 20.04
Hello,
Whilst I wasn't looking something has broken the web interface to mailman on our list server. On the list index page I get the Postorius header, but no list index, instead a Page not found error. Curiously the Postorius header is also broken, the links point to https://host/mailman/(postorius/lists|hyperkitty) not https://host/mailman3/(postorius/lists|hyperkitty) like it should
I've poked around and I can't find any useful errors and I don't know exactly when this happened, but I think it was this week. Mailman itself is running happily underneath.
Any suggestions as to what might have gone wrong?
Simon
P.S. Hopefully I've got the right list this time.
Simon Brown System Engineer EISCAT Scientific Association P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown@eiscat.se
On Thursday, 30 September 2021 11:43:00 CEST Simon Brown wrote:
Whilst I wasn't looking something has broken the web interface to mailman on our list server. On the list index page I get the Postorius header, but no list index, instead a Page not found error. Curiously the Postorius header is also broken, the links point to https://host/mailman/(postorius/lists|hyperkitty) not https://host/mailman3/(postorius/lists|hyperkitty) like it should
I've poked around and I can't find any useful errors and I don't know exactly when this happened, but I think it was this week. Mailman itself is running happily underneath.
I've managed to get things working again with help from a colleague familiar with Django. The bug seems to be in the Debian/Ubuntu packaging. In the apache.conf file there is the line:
ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/
and the problem was caused by the final trailing slash. Changing it to
ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost
fixed the problem.
I presume something has changed with Apache in Ubuntu 20.04, as this used to work. I expect others will also hit this problem.
Simon
Simon Brown System Engineer EISCAT Scientific Association P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown@eiscat.se
Hi Simon
I'm running mm3 on ubuntu 20.04 as well. I don't recall if I saw exactly what you're seeing but it sounds similar. I found that after bootup, mailmain3 would be running fine, but similar to you, I'd get a postorius header but no lists shown on the web UI. I had to restart mailman3-web and it would come up. I assumed it was a startup timing issue and something it needed just wasn't up yet.
I don't run production mailing lists so I added a restart post-boot to my startup scripts and this seems to have gone away. Try and restart the service?
Matt
Sep 30, 2021 06:07:20 Simon Brown <simon.brown@eiscat.se>:
Hello,
Whilst I wasn't looking something has broken the web interface to mailman on our list server. On the list index page I get the Postorius header, but no list index, instead a Page not found error. Curiously the Postorius header is also broken, the links point to https://host/mailman/(postorius/lists|hyperkitty) not https://host/mailman3/(postorius/lists|hyperkitty) like it should
I've poked around and I can't find any useful errors and I don't know exactly when this happened, but I think it was this week. Mailman itself is running happily underneath.
Any suggestions as to what might have gone wrong?
Simon
P.S. Hopefully I've got the right list this time.
Simon Brown System Engineer EISCAT Scientific Association P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown@eiscat.se
Mine is doing the same thing. It happened yesterday morning, when some packages were upgraded by the system. I'm glad it's not just me this has happened to.
It looks like someone pushed an apache2 package which broke things on the 28th September, and another has been pushed yesterday, but it's still broken. From my logs, these packages got updated the first time:
Start-Date: 2021-09-29 06:38:15 Commandline: /usr/bin/unattended-upgrade Upgrade: libapache2-mod-proxy-uwsgi:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5), apache2-data:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5), apache2-bin:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5), apache2:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5), apache2-utils:amd64 (2.4.41-4ubuntu3.4, 2.4.41-4ubuntu3.5) End-Date: 2021-09-29 06:38:52
and then the next day:
Start-Date: 2021-09-30 06:33:46 Commandline: /usr/bin/unattended-upgrade Upgrade: libapache2-mod-proxy-uwsgi:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6), apache2-data:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6), apache2-bin:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6), apache2:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6), apache2-utils:amd64 (2.4.41-4ubuntu3.5, 2.4.41-4ubuntu3.6) End-Date: 2021-09-30 06:34:32
So clearly something's gone wrong with Ubuntu's apache2 packages, and it's broken something quite badly for Django and/or Postorious. But I don't know enough about how Django or WSGI work to be able to debug this.
When I look at the mailman-web-logs, the urls that postorious puts into the page don't honour the POSTORIOUS_TEMPLATE_BASE_URL variable in the mailman-web.py file any more.
Tim
The cause is a security update to apache2, which was released on the 28th. It's got regression problems. There's been another update today, which doesn't fix it. I've reported the bug to Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1945710
You can work around the issue by force downgrading your apache2 packages to previous versions, but then you won't have any of the apache2 security fixes on your system:
aptitude install apache2=2.4.41-4ubuntu3 libapache2-mod-proxy-uwsgi=2.4.41-4ubuntu3 apache2-bin=2.4.41-4ubuntu3 apache2-utils=2.4.41-4ubuntu3 apache2-data=2.4.41-4ubuntu3
Doing that brought mailman3 back to life again, but I'm not very comfortable running an insecure apache2 package
Tim
On 9/30/21 2:30 PM, tim@thecutts.org wrote:
When I look at the mailman-web-logs, the urls that postorious puts into the page don't honour the POSTORIOUS_TEMPLATE_BASE_URL variable in the mailman-web.py file any more.
I'm not saying there isn't an issue in Postorius, but I don't think it has anything to do with POSTORIUS_TEMPLATE_BASE_URL which is only used for templates and has nothing to do with the rendering of the list pages and shouldn't contain anything beyond the host and port in any case.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hello, many thanks Simon. We got the same problem, delete the final trailing slash fixed the problem for us also. We are running mailman3 on ubuntu20.04 (apache2) too. Thanks to your tip we were able to save time.
Kind regards
participants (5)
-
Mark Sapiro -
matt＠efs.org -
r.woithe＠callassoftware.com -
Simon Brown -
tim＠thecutts.org