[MM3-users]Installation issues
Hi folks
I was speaking to someone last night on the IRC chat room @ http://webchat.freenode.net/ who suggested sending an email to this address to try and find a solution to my issues.
I have been trying to get Mailman 3 installed on an Ubuntu 14.04 server.
I thought I had followed the instructions from https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Install%20on... and http://mailman-bundler.readthedocs.org/en/latest/ but am getting an error 500 when I try and browse to http://x.x.x.x:8000/mailman3. I can open http://x.x.x.x:8000/archives and the login button seems to work, but when I click manage lists I get an error 500 again.
The entire process I followed is below:
sudo apt-get updatesudo apt-get install git python3-dev python3-pip python-dev python-pip python-virtualenvsudo apt-get install nodejs npmsudo npm install -g lesssudo ln -s /usr/bin/nodejs /usr/bin/nodecreated new user 'mailmanuser''mkdir /opt/mailman''sudo chown mailmanuser:mailmanuser mailman''su mailman''cd /opt/mailman'git clone https://gitlab.com/mailman/mailman-bundler.gitvirtualenv -p /usr/lib/python2.7 venvsource venv/bin/activatechanged password in mailman_web/testing.pycd mailman-bundlerpip install zc.buildoutbuildoutsudo apt-get install ruby-sass./bin/mailman-post-update./bin/mailman-web-django-admin createsuperuser./bin/mailman start./bin/mailman-web-django-admin runserver 0.0.0.0:8000
I have attached the django and mailman logs and the top of the page I get back from the server
I must have missed something but I don't really know where to go from here... Please can you review and advise if there is anything that I have missed?
I look forward to hearing from you in due course. Any pointers greatly received.
Kind regards
Simon
This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful.
Thank you for your co-operation.
NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere
On 04/19/2016 07:37 AM, Hellings Simon (EAST KENT HOSPITALS UNIVERSITY NHS FOUNDATION TRUST) wrote:
I have attached the django and mailman logs and the top of the page I get back from the server
Content filtering removed the two .log files because your MUA gave their Content-Type as application/octet-stream instead of text/. I got to see them because your initial post was held for moderation and I have attached them here.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
The entire process I followed is below:
sudo apt-get updatesudo apt-get install git python3-dev python3-pip python-devpython-pip python-virtualenv
sudo apt-get install nodejs npmsudo npm install -g lessYou don't need {less,nodejs,npm} Hyperkitty switched from less to sass
sudo ln -s /usr/bin/nodejs /usr/bin/nodecreated new user 'mailmanuser''mkdir /opt/mailman''sudo chown mailmanuser:mailmanuser mailman''su mailman'This is inconsistent with your other instructions. I guess it's just a typo
'cd /opt/mailman'git clone https://gitlab.com/mailman/mailman-bundler.gitvirtualenv -p /usr/lib/python2.7 venvsource venv/bin/activatechanged password in mailman_web/testing.pycd mailman-bundlerpip install zc.buildoutbuildoutsudo apt-get install ruby-sass./bin/mailman-post-update./bin/mailman-web-django-admin createsuperuser./bin/mailman start./bin/mailman-web-django-admin runserver 0.0.0.0:8000I have attached the django and mailman logs and the top of the page I get back from the server
I must have missed something but I don't really know where to go from here... Please can you review and advise if there is anything that I have missed? You didn't miss anything. The mistake was on our side. mailman-bundler used to install mailman==3.0.2 which didn't limit the falcon version but is incompatible with the latest. mailman==3.0.3 was released to fix this issue but mailman-bundler wasn't updated until today.
You can either start fresh or activate the python3.4 virtualenv and run pip install --upgrade falcon==0.3.0
After that restart mailman and everything should be fine.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi guys,
I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow?
Thanks. Andrew.
On 04/19/2016 11:40 AM, Andrew Hodgson wrote:
I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow?
Sort of, but it's not (yet) public. The process I followed is very convoluted and not what I would recommend anyone follow. Part of the issue is I started with mailman-bundler not using a venv, but bundler still installs a lot of stuff in Python 2 and Python 3 venvs. I then proceeded to install the git master branches of mailman, mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their dependencies system wide and ripped out most of the venv stuff.
Then there were issues because I'm running django 1.9 only and that's not compatible with django_haystack 2.4.1, so I upgraded that to 2.5.dev0 from GitHub, but that now has a compatibility issue with HyperKitty which I have worked around.
As you can see this is not a clean process. If I were starting over with what I've learned, I'd probably let bundler install it all in venvs and then upgrade the venvs to the git master branches.
There would still be issues, but it would be cleaner.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
On 04/19/2016 11:40 AM, Andrew Hodgson wrote:
I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow?
Sort of, but it's not (yet) public. The process I followed is very convoluted and not what I would recommend anyone follow. Part of the issue is I started with mailman-bundler not using a venv, but bundler still installs a lot of stuff in Python 2 and Python 3 venvs. I then proceeded to install the git master branches of mailman, mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their dependencies system wide and ripped out most of the venv stuff.
I started off without using venvs and ran into several issues, though one of them I think was due to the bundler pulling down an outdated dependency. My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet.
My main thing when looking at this is how package managers are likely to package Mailman3, especially from a Debian point of view. I know I can't second guess what is going to be done, but would like to try to build using similar goals if possible.
Thanks. Andrew.
On Apr 20, 2016, at 08:11 AM, Andrew Hodgson wrote:
My main thing when looking at this is how package managers are likely to package Mailman3, especially from a Debian point of view. I know I can't second guess what is going to be done, but would like to try to build using similar goals if possible.
There have been ongoing discussions on mailman-developers and the relevant Debian mailing lists about packaging Mailman 3.
Pierre-Elliott Bécue has been leading the effort, e.g.
https://mail.python.org/pipermail/mailman-developers/2016-February/025395.ht...
Cheers, -Barry
On 04/20/2016 01:11 AM, Andrew Hodgson wrote:
My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet.
You should be aware that mailman-bundler uses two venvs, one for Python 2 and one for Python 3. The idea is you create the Python 2 venv and activate it when running mailman-bundler's buildout, but that process will also create a venv-3.x venv in the bundler directory.
I think what may make sense is to clone mailman-bundler directly into /opt/mailman rather than /opt/mailman/mailman-bundler. Then follow the docs from there. This should give you paths like /opt/mailman/venv/, /opt/mailman/venv3.x/, /opt/mailman/deployment/, /opt/mailman/mailman-web/, /opt/mailman/bin/, /opt/mailman/var/ and so on without the extra mailman-bundler/ level.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (5)
-
Andrew Hodgson -
Barry Warsaw -
Hellings Simon (EAST KENT HOSPITALS UNIVERSITY NHS FOUNDATION TRUST) -
Mark Sapiro -
Simon Hanna