On 9/14/2020 9:11 PM, Mark Sapiro wrote:
On 9/14/20 9:59 AM, Dennis Putnam wrote:
On 8/29/2020 2:11 PM, Dennis Putnam wrote:
Since Centos 7 is way behind on mailman rpm (2.1.15 is the only available rpm) and mailman is currently at 2.1.34 I need to do a manual update. While I know how to install software, I am concerned that just doing a manual install from the tarball will mess up current settings, lists and members. Does anyone have experience doing this that can advise about pitfalls or has a cookbook document to do a safe update? TIA.
After additional attempts and some research I am stuck upgrading mailman 2.1.5 to 2.1.34 and get the same results I had reported here earlier. I followed these instructions:
https://wiki.list.org/DOC/How%20do%20I%20upgrade%20a%20Debian/Ubuntu%20Mailm....
This FAQ (note period is part of URL) is not relevant.
The relevant FAQ is https://wiki.list.org/x/8486953> which references the post at <https://mail.python.org/pipermail/mailman-developers/2004-October/017343.htm...> (also now at <https://mail.python.org/archives/list/mailman-developers@python.org/message/...> which contains a patch which enables Mailman to install in the RHEL/Centos way.
(more below)
And made, what I thought were, the appropriate changes to the configure parameters:
./configure --prefix=/usr/lib/mailman --with-username=mailman --with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman
If anyone sees anything wrong please point it out. Anyway, after doing the make and install, I start mailman and get this status:
● mailman.service - GNU Mailing List Manager Loaded: loaded (/usr/lib/systemd/system/mailman.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2020-09-14 10:31:12 MDT; 20min ago Process: 20030 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start (code=exited, status=1/FAILURE) Process: 20028 ExecStartPre=/bin/chmod 660 /var/log/mailman/error (code=exited, status=0/SUCCESS) Process: 20024 ExecStartPre=/bin/chown mailman:mailman /var/log/mailman/error (code=exited, status=0/SUCCESS) Process: 20021 ExecStartPre=/bin/touch /var/log/mailman/error (code=exited, status=0/SUCCESS) Process: 20018 ExecStartPre=/usr/bin/install -m644 -o root -g root /usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited, status=0/SUCCESS) Process: 20014 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg (code=exited, status=0/SUCCESS)
Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: File "/usr/lib64/python2.7/codecs.py", line 881, in open Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: file = __builtin__.open(filename, mode, buffering) Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: IOError: [Errno 13] Permission denied: '/usr/lib/mailman/logs/error' Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: Original log message: Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: [Errno 13] Permission denied: '/usr/lib/mailman/logs/error' Sep 14 10:31:12 harmonia.csd.net mailmanctl[20030]: Sep 14 10:31:12 2020 (20030) Site list is missing: mailman Sep 14 10:31:12 harmonia.csd.net systemd[1]: mailman.service: control process exited, code=exited status=1 Sep 14 10:31:12 harmonia.csd.net systemd[1]: Failed to start GNU Mailing List Manager. Sep 14 10:31:12 harmonia.csd.net systemd[1]: Unit mailman.service entered failed state. Sep 14 10:31:12 harmonia.csd.net systemd[1]: mailman.service failed.
I don't understand the permissions denied error.
I suspect this is a SELinux issue. That's what the RHEL FHS patch is for. Is SELinux enabled? If yoiu disable it does Mailman start?
Hi Mark,
Thanks for the reply. Your article is not much help as I am already at 2.1.15 so the paths are already correct. I turned off SELinux to see if that helps but there is another issue after the reboot. I'll let you know when I get the machine back online. That may fix the permission problem but probably not the missing site list.