Mailman would not start after upgrade to 2.1.26
Hi,
After upgrading to Mailman 2.1.26 via ports in FreeBSD 11.1 and a reboot of the server, I just could not start Mailman at all. It would not indicate any error. The Mailman logs here: /usr/local/mailman/logs did not record anything.
On second looks, I found that, after the upgrade, the write permissions for all logs under /usr/local/mailman/ logs had been removed. All log files had only read permissions for user and group. After adding write permissions (chmod 660 *) to all log files, I could restart Mailman again, and everything works again.
I am not sure this has happened before but just wanted to send this note to the list for the record just in case it is a problem no one had before. And I am sorry if I am reporting a solution to a well-known problem.
Does anyone have an idea what could have changed the write permissions for the logs during an upgrade? I use portmaster under FreeBSD.
Cheers, Amardeo P.S.: I was subscribed before and have resubscribed now.
Amardeo Sarma sarma@gwup.org @amardeo
On 02/12/2018 12:34 PM, Amardeo Sarma wrote:
Does anyone have an idea what could have changed the write permissions for the logs during an upgrade? I use portmaster under FreeBSD.
This would seem to be an issue with FreeBSD ports. You should report this to whoever is responsible for that.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2/13/2018 10:25 AM, Mark Sapiro wrote:
This would seem to be an issue with FreeBSD ports. You should report this to whoever is responsible for that
FWIW, while I like FreeBSD's ports & packages, I've found that installing mailman from the source generally is more reliable and updating is easier. YMMV.
z!
Carl Zwanzig cpz@tuunq.com writes:
On 2/13/2018 10:25 AM, Mark Sapiro wrote:
This would seem to be an issue with FreeBSD ports. You should report this to whoever is responsible for that
FWIW, while I like FreeBSD's ports & packages, I've found that installing mailman from the source generally is more reliable and updating is easier. YMMV.
If you're installing from ports, whether building from within the ports tree or using a port management tool like portupgrade or portmaster, you are installing from source.
package is meant to simplify the process by just installing a compiled binary and some necessary libraries, but I do have consistent problems with installs from pkg - not to mention the various things that aren't in pkg yet...
Keith
--
from my mac to yours...
Keith Seyffarth mailto:weif@weif.net http://www.weif.net/ - Home of the First Tank Guide! http://www.rpgcalendar.net/ - the Montana Role-Playing Calendar
http://www.miscon.org/ - Montana's Longest Running Science Fiction Convention
On 2/13/2018 12:29 PM, Keith Seyffarth wrote:
If you're installing from ports, whether building from within the ports tree or using a port management tool like portupgrade or portmaster, you are installing from source.
...installing using the source code of whatever version the port is configured for and with whatever patches the port maintainer decided to include. This as opposed to installing the version -you- want with the options that -you- want to use. For some software, the port (and pkg) can lag significantly behind the current released version (as it happens, the current pkg is .25 and the current port is .26 from about 4 days ago but there were some updates to that from less that 24 hours ago).
I'll stick with my preference of installing mailman from it's original code tarball and not from a port; it's served me well for years.
z!
Hi All,
I would like to report that I have resolved the problem. It was a problem I introduced, not the ports package, showing what unintended side effects some server changes cause.
I had introduced a new log rotation scheme using newsyslog in FreeBSD at around the same time I did the upgrade. This included, as an example, the following lines: # logfilename [owner:group] mode count size when flags [/pid_file] [sig_num] /usr/local/mailman/logs/bounce mailman:mailman 400 5 * $W2D1 X /usr/local/mailman/data/master-qrunner.pid /usr/local/mailman/logs/error mailman:mailman 400 5 * $W1D1 X /usr/local/mailman/data/master-qrunner.pid /usr/local/mailman/logs/locks mailman:mailman 400 5 * $W1D1 X /usr/local/mailman/data/master-qrunner.pid [..]
The mode 400, applied on the first Tuesday morning to all mailman logs, also made all the log files unwritable for mailman. Mailman stopped, probably with the next attempt to write a log, and would not start again. I have now changed the mode to 660, which has fixed the problem. A manual chmod for all log files was the immediate fix.
Amardeo
Amardeo Sarma @amardeo sarma@gwup.org
-----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+sarma=gwup.org@python.org] On Behalf Of Mark Sapiro Sent: Tuesday, February 13, 2018 7:25 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] Mailman would not start after upgrade to 2.1.26
On 02/12/2018 12:34 PM, Amardeo Sarma wrote:
Does anyone have an idea what could have changed the write permissions for the logs during an upgrade? I use portmaster under FreeBSD.
This would seem to be an issue with FreeBSD ports. You should report this to whoever is responsible for that.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/sarma%40gwup.org
participants (4)
-
Amardeo Sarma -
Carl Zwanzig -
Keith Seyffarth -
Mark Sapiro