help for new installation.
Hello everyone. A few days ago, I am trying to install and configure mailman 3, in a Centos7. and the truth has not been achieved. I am already a little desperate.
I'll tell you First I install the hyperkitty-el.repo repository and install mailman 3, hyperkitty and postorius. Initially when reviewing and making some minor modifications to the mailman configuration file, the service apparently rises without major problems.
The problem occurs when I try to configure the web interfaces. Initially the apache server did not start, with a series of errors. Following the instructions of the document published here: http://www.admin-magazine.com/Archive/2015/29/Mailman-3.0-a-long-time-coming... I managed to eliminate the initial errors, which prevented to raise the Apache server. However, when trying to access the web pages, in the case of hyperkitty, I get an error 500 with an "internal server error". In the case of postorius, I get an error 403 forbidden.
In the mail, I receive a log, with the following content:
Traceback (most recent call last): File "/ usr / bin / django-admin", line 5, in <module> management.execute_from_command_line () File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line utility.execute () File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 303, in execute settings.INSTALLED_APPS File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 48, in __getattr__ self._setup (name) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 44, in _setup self._wrapped = Settings (settings_module) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 92, in __init__ mod = importlib.import_module (self.SETTINGS_MODULE) File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module __import __ (name) ImportError: No module named settings
In the Apache logs, it also shows the following: [Mon Dec 11 21: 48: 41.875069 2017] [authz_core: error] [pid 15333] [client my-client-ip: 33584] AH01630: client denied by server configuration: / etc / postorius / sites / default / srv
when I execute the command: django-admin check
throws me the following:
django.core.exceptions.ImproperlyConfigured: Requested setting DATABASES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.
checking the ports, I can see that python has open ports 8000 in 127.0.0.1, and 8001 in external ip,
for more than I have looked for information, documentation, etc, about the procedure of the installation. all the documentation I found, part of the premise of an installation, clean from git, by pip, but none from the yum and rpm. So it is difficult for me to determine what to apply, and what not. apparently no one has installed, or has had problems in the installation from repositories, or I am omitting some step (most likely) that I could not determine.
the bad thing, is that in postfix, I have everything configured, with digital signatures, so I would not like to lose all that work, as to start with an installation from 0.
If you can help me, it would be very helpful. since I made the request of help in another list, of dev, to which it is supposed that the consultations should be made, according to the historical mails, but I never received answer.
Of course, thank you very much for any help and guidance they can give me.
On 12/11/2017 05:16 PM, claudio.jofre@yandex.com wrote:
Hello everyone. A few days ago, I am trying to install and configure mailman 3, in a Centos7. and the truth has not been achieved. I am already a little desperate.
Have you tried Docker containers? Using docker sidesteps CentOS installation hassles and mismatch in library requirements and is a relatively straight-forward process.
if nothing else - it'll give you a sample of *working* mailman setup you can disect and use as a reference.
https://asynchronous.in/docker-mailman/
my group is rolling out MM3 using above Docker containers on CentOS7 for sr some of the reasons you cite.
-- Sr System and DevOps Engineer SoM IRT
On December 12, 2017 8:35:56 AM EST, Dmitry Makovey <dmakovey@stanford.edu> wrote:
On 12/11/2017 05:16 PM, claudio.jofre@yandex.com wrote:
Hello everyone. A few days ago, I am trying to install and configure mailman 3, in a Centos7. and the truth has not been achieved. I am already a little desperate.
Have you tried Docker containers? Using docker sidesteps CentOS installation hassles and mismatch in library requirements and is a relatively straight-forward process.
if nothing else - it'll give you a sample of *working* mailman setup you can disect and use as a reference.
https://asynchronous.in/docker-mailman/
my group is rolling out MM3 using above Docker containers on CentOS7 for sr some of the reasons you cite.
This is another mm3 docker I used to finally get my mm3 instance off the ground. Running on centos 7.4 just fine with Apache and postfix integration:
https://github.com/maxking/docker-mailman
And I believe this docker's maintainer is an active member of the mm3 Dev team. Check it out.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
On 12/12/2017 05:56 AM, Fabian A. Santiago wrote:
On December 12, 2017 8:35:56 AM EST, Dmitry Makovey <dmakovey@stanford.edu> wrote:
https://asynchronous.in/docker-mailman/
my group is rolling out MM3 using above Docker containers on CentOS7 for sr some of the reasons you cite.
This is another mm3 docker I used to finally get my mm3 instance off the ground. Running on centos 7.4 just fine with Apache and postfix integration:
https://github.com/maxking/docker-mailman
And I believe this docker's maintainer is an active member of the mm3 Dev team. Check it out.
actually it is the same docker deployment ;) check out github link from the main page of the https://asynchronous.in/docker-mailman/ . Abhilash Raj (maxking) did a great job putting those containers together.
-- Sr System and DevOps Engineer SoM IRT
December 12, 2017 9:03 AM, "Dmitry Makovey" <dmakovey@stanford.edu> wrote:
On 12/12/2017 05:56 AM, Fabian A. Santiago wrote:
On December 12, 2017 8:35:56 AM EST, Dmitry Makovey <dmakovey@stanford.edu> wrote:
https://asynchronous.in/docker-mailman
my group is rolling out MM3 using above Docker containers on CentOS7 for sr some of the reasons you cite.
This is another mm3 docker I used to finally get my mm3 instance off the ground. Running on centos 7.4 just fine with Apache and postfix integration:
https://github.com/maxking/docker-mailman
And I believe this docker's maintainer is an active member of the mm3 Dev team. Check it out.
actually it is the same docker deployment ;) check out github link from the main page of the https://asynchronous.in/docker-mailman . Abhilash Raj (maxking) did a great job putting those containers together.
-- Sr System and DevOps Engineer SoM IRT
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org
oh haha, sorry, silly me. i miss the details sometimes. yeh, it's great!
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
Hi: thanks for your help.
I find the docker proposal interesting. I'm trying to follow it, according to the documentation they sent. I only have two doubts left until now. First: where I find the file docker-compose.yaml, I could not find it anywhere. (Install the docker and docker-compose using yum and using the epel repositories. second: How do I access the mailman configuration files inside the docker? Is there any way to mount it? as a unit, to make the modifications?
On 12/12/2017 01:49 PM, claudio.jofre@yandex.com wrote:
I only have two doubts left until now. First: where I find the file docker-compose.yaml, I could not find it anywhere. (Install the docker and docker-compose using yum and using the epel repositories.
check out github repo:
https://github.com/maxking/docker-mailman
second: How do I access the mailman configuration files inside the docker? Is there any way to mount it? as a unit, to make the modifications?
this is quite the opposite - you mount directories with config files into your docker containers. Check out docker-compose.yaml in Git repo and follow the docs. You may need to re-adjust yaml file to your liking, but it's a reasonably good start
-- Sr System and DevOps Engineer SoM IRT
December 12, 2017 4:49 PM, claudio.jofre@yandex.com wrote:
Hi: thanks for your help.
I find the docker proposal interesting. I'm trying to follow it, according to the documentation they sent. I only have two doubts left until now. First: where I find the file docker-compose.yaml, I could not find it anywhere. (Install the docker and docker-compose using yum and using the epel repositories. second: How do I access the mailman configuration files inside the docker? Is there any way to mount it? as a unit, to make the modifications?
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org
You shouldn't have to modify the container files at all. the docker-compose.yaml file is where you specify the environment variables or config options needing to be passed.
you can also pass addt'l configs to mailman:
/opt/mailman/core/mailman-extra.cfg : This is the configuration for Mailman Core and anything that you add here will be added to Core's configuration. You need to restart your mailman-core container for the changes in this file to take effect.
/opt/mailman/web/settings_local.py : This is the Django configuration that is imported by the existing configuration provided by the mailman-web container. To change or override any settings in Django, you need to edit this file.read the docs for the docker. they're pretty straight forward. there's only a very small set of required parameters to get it up and running on a basic level.
**Tip: you need to make sure mailman_core is at version 3.1+ in order for the postfix aliases to be written correctly, if that's your mail server of choice. I believe maxking has addressed this by creating docker containers of the latest git committed versions in addition to the stable versions. before that i had to manually update my core container to get the fixes from git.
good luck. read the docs.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
participants (3)
-
claudio.jofre＠yandex.com -
Dmitry Makovey -
Fabian A. Santiago