Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

> It probably is permissions on the logs and others. Have you run > check_perms. If not run `check_perms -f` as root. Don't worry about > symlinks, they don't matter. that did it, finally! check_perms -f. thanks for your help. finally on 2.1.29 now. all seems to be working now. -- Fabian S.

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 10:41 AM, Fabian A. Santiago wrote: > On 5/23/19 1:29 PM, Fabian A. Santiago wrote: >> On 5/23/19 12:11 PM, Mark Sapiro wrote: >>> >>> What's in Mailman's error log? >>> >>> >> nothing. It probably is permissions on the logs and others. Have you run check_perms. If not run `check_perms

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 1:29 PM, Fabian A. Santiago wrote: > On 5/23/19 12:11 PM, Mark Sapiro wrote: >> On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote: >>> Ok making progress. Service started now but the www UI reports: >>> >>> Bug in Mailman version 2.1.29 >>> >>> >>> >>> We're sorry, we hit a bug! >>> >>> Ple

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 12:11 PM, Mark Sapiro wrote: > On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote: >> Ok making progress. Service started now but the www UI reports: >> >> Bug in Mailman version 2.1.29 >> >> >> >> We're sorry, we hit a bug! >> >> Please inform the webmaster for this site of this problem. Pr

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 8:50 AM, Fabian Aldo Santiago wrote: > Ok making progress. Service started now but the www UI reports: > > Bug in Mailman version 2.1.29 > > > > We're sorry, we hit a bug! > > Please inform the webmaster for this site of this problem. Printing of > traceback and other system inform

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

Ok making progress. Service started now but the www UI reports: Bug in Mailman version 2.1.29 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find thi

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 8:07 AM, Fabian Aldo Santiago wrote: > Service file: > > [Unit] > Description=Mailman Master Queue Runner > After=network.target > > [Service] > Type=forking > PIDFile=/var/run/mailman/mailman.pid You could try PIDFile=/var/lib/mailman/data/master-qrunner.pid which is where mailmanc

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

Service file: [Unit] Description=Mailman Master Queue Runner After=network.target [Service] Type=forking PIDFile=/var/run/mailman/mailman.pid ExecStart=/usr/lib/mailman/bin/mailmanctl -s start ExecStop=/usr/lib/mailman/bin/mailmanctl stop ExecReload=/usr/lib/mailman/bin/mailmanctl restart Restart

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 7:02 AM, Fabian A. Santiago wrote: > > ok, the issue occurred again with the same error. the complaint is (from > systemctl status ... -l): > > May 23 09:44:40 mail systemd[1]: mailman.service: Can't open PID file > /var/run/mailman/mailman. > > journalctl -xe reports: > > May 23 09:

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/23/19 9:04 AM, Fabian A. Santiago wrote: > On 5/22/19 11:42 AM, Mark Sapiro wrote: > >> >> Did you look at ? >> >> What was the exact complaint. It's probably easy to fix. > > Thank you Mark for this reference. I did not look at it. I also didn't > record th

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

also, that wiki page you sent me mention an error with missing dnspython and it states to run this: "sudo apt-get install python-dnspython" but that claims it's already installed, yet the error occurs. what i found you want to install is the package "python-dev". -- Fabian S. OpenPGP: 0xA125

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

On 5/22/19 11:42 AM, Mark Sapiro wrote: > > Did you look at ? > > What was the exact complaint. It's probably easy to fix. Thank you Mark for this reference. I did not look at it. I also didn't record the error. i needed this server / list back up asap so i sna