Mark Sapiro | 1 May 01:15 2012
Picon

Re: Mailman stuck : mailmanctl dead with messages in /qfiles/in

On 4/30/2012 3:43 PM, Jérôme wrote:
> 
> Mailman somtimes gets stuck on my installation. By stuck, I mean I get no
> mail and no subscription notification. Until I relaunch it.
[...]
> Troubleshooting
> ---------------
> 
> http://wiki.list.org/display/DOC/4.78+Troubleshooting-+No+mail+going+out+to+lists+members
> 
> 2/ Cron/mailmanctl
> 
> ps auxww| grep mailmanctl |grep -v grep
> -> Nothing.

How about

ps auxww| grep qrunner |grep -v grep

> 7/ Locks
> 
> /var/lib/mailman/locks -> /var/lock/mailman
> 
> ll /var/lock/mailman
> total 0

It appears that some process or person is stopping Mailman.

> 8/ Logs
> 
(Continue reading)

Jérôme | 1 May 02:19 2012
X-Face
Picon

Re: Mailman stuck : mailmanctl dead with messages in /qfiles/in

Hi.

Thanks for answering.

Mon, 30 Apr 2012 16:15:03 -0700
Mark Sapiro a écrit:

> > 2/ Cron/mailmanctl
> > 
> > ps auxww| grep mailmanctl |grep -v grep
> > -> Nothing.
> 
> How about
> 
> ps auxww| grep qrunner |grep -v grep

Nothing either.

> > 7/ Locks
> > 
> > /var/lib/mailman/locks -> /var/lock/mailman
> > 
> > ll /var/lock/mailman
> > total 0
> 
> It appears that some process or person is stopping Mailman.

OK. Need to figure out which.

> > 8/ Logs
(Continue reading)

Mark Sapiro | 1 May 04:14 2012
Picon

Re: Mailman stuck : mailmanctl dead with messages in /qfiles/in

On 4/30/2012 5:19 PM, Jérôme wrote:

> Mark Sapiro a écrit:
>>
>> How about /var/log/mailman/qrunner ?
> 
> Each day, I have something like this :
> Apr 28 03:16:33 2012 (17099) OutgoingRunner qrunner caught SIGHUP.  Reopening
> logs. Apr 28 03:16:33 2012 (17094) ArchRunner qrunner caught SIGHUP.
> Reopening logs. Apr 28 03:16:33 2012 (17097) IncomingRunner qrunner caught
> SIGHUP.  Reopening logs. Apr 28 03:16:33 2012 (17093) Master watcher caught
> SIGHUP.  Re-opening log files. Apr 28 03:16:34 2012 (17095) BounceRunner
> qrunner caught SIGHUP.  Reopening logs. Apr 28 03:16:34 2012 (17101)
> RetryRunner qrunner caught SIGHUP.  Reopening logs. Apr 28 03:16:34 2012
> (17096) CommandRunner qrunner caught SIGHUP.  Reopening logs. Apr 28 03:16:34
> 2012 (17098) NewsRunner qrunner caught SIGHUP.  Reopening logs. Apr 28
> 03:16:34 2012 (17100) VirginRunner qrunner caught SIGHUP.  Reopening logs.

That is presumably a logrotate process.

> The day it stopped, I got this :
> Apr 29 03:16:29 2012 (17099) OutgoingRunner qrunner caught SIGHUP.  Reopening
> logs. Apr 29 03:16:29 2012 (17094) ArchRunner qrunner caught SIGHUP.
> Reopening logs. Apr 29 03:16:29 2012 (17097) IncomingRunner qrunner caught
> SIGHUP.  Reopening logs. Apr 29 03:16:29 2012 (17093) Master watcher caught
> SIGHUP.  Re-opening log files. Apr 29 03:16:29 2012 (17097) IncomingRunner
> qrunner caught SIGTERM.  Stopping. Apr 29 03:16:29 2012 (17099)
> OutgoingRunner qrunner caught SIGTERM.  Stopping. Apr 29 03:16:29 2012
> (17097) IncomingRunner qrunner exiting. Apr 29 03:16:29 2012 (17094)
> ArchRunner qrunner caught SIGTERM.  Stopping. Apr 29 03:16:29 2012 (17099)
(Continue reading)

David | 1 May 04:33 2012

Re: options to change URL structure?

The last URL I want to change is for the public archives.

I want to use "archive" instead of "pipermail" in the URL.

I made the changes to
apache2/sites-enabled/000-default
and
/etc/mailman/apache.conf

Even though it was probably not needed, I ran:
/var/lib/mailman/bin/withlist -l -a -r fix_url -- -v

...and the new archive URL appears to work. For example, I can navigate to
the list's public archives with

http://server.example.com/archive/ourlist/

However, on the following admin page: Example mailing list administration,
General Options Section...
the link: *Go to list archives*
still points to http://server.example.com/pipermail/ourlist/

I restarted mailman:
sudo /etc/init.d/mailman restart

But the admin page still shows the old link.

What should I check next?

Thanks!
(Continue reading)

Mark Sapiro | 1 May 04:38 2012
Picon

Re: options to change URL structure?

David wrote:
>
>Even though it was probably not needed, I ran:
>/var/lib/mailman/bin/withlist -l -a -r fix_url -- -v

Yes, it wasn't needed.

>...and the new archive URL appears to work. For example, I can navigate to
>the list's public archives with
>
>http://server.example.com/archive/ourlist/
>
>However, on the following admin page: Example mailing list administration,
>General Options Section...
>the link: *Go to list archives*
>still points to http://server.example.com/pipermail/ourlist/
>
>I restarted mailman:
>sudo /etc/init.d/mailman restart
>
>But the admin page still shows the old link.
>
>What should I check next?

Read the documentation and default setting for PUBLIC_ARCHIVE_URL in
Defaults.py and that should tell you what you need to put in mm_cfg.py.

It should be effective without restarting Mailman.

--

-- 
(Continue reading)

David | 1 May 04:48 2012

Re: options to change URL structure?

On Mon, Apr 30, 2012 at 10:38 PM, Mark Sapiro <mark <at> msapiro.net> wrote:

> David wrote:
> >What should I check next?
>
> Read the documentation and default setting for PUBLIC_ARCHIVE_URL in
> Defaults.py and that should tell you what you need to put in mm_cfg.py.
>

I simply added this to mm_cfg.py
PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/archive/%(listname)s/'

> It should be effective without restarting Mailman.
>

Yes, it was. Thank you!
------------------------------------------------------
Mailman-Users mailing list Mailman-Users <at> python.org
http://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: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org

Jérôme | 1 May 14:16 2012
X-Face
Picon

Re: Mailman stuck : mailmanctl dead with messages in /qfiles/in

Mon, 30 Apr 2012 19:14:48 -0700
Mark Sapiro a écrit:

> So here in addition to the normal SIGHUPs, presumably from logrotate,
> you also have SIGTERMs possibly from a "bin/mailmanctl stop" although
> you don't show a "Master watcher caught SIGTERM" entry.
> 
> Check your system cron log to see what was running at the time.

cron log was not enabled...

I enabled it and relaunched mailman. I hope next time, the cron log will show
something useful.

> No. That isn't relevant to this issue. Apparently, something reversed
> the patch on April 22 which is just as well.

In fact, the patch is still applied. I see the line 
self.__conn.set_debuglevel(1)  
in 
/var/lib/mailman/Mailman/Handlers/SMTPDirect.py

Anyway. It seems to be working again.

> The curious thing is you are rotating logs weekly, but "reopening" them
> daily. Either this is two different processes or your logrotate script
> is a bit strange.

I'll try to figure that out.

(Continue reading)

Mark Sapiro | 1 May 19:06 2012
Picon

Re: The mailman has "log" of moderated messages?

madsonra <at> dcc.ufba.br wrote:
>
>excuse me I'm not very good with English. I wonder if the mailman
>stores "log" about moderation. Exactly I want to find out which
>moderator approved some messages that were sent to the list.

Mailman logs moderator actions in Mailman's 'vette' log, but Mailman
doesn't know which moderator took the action since all use the same
authentication.

You need to correlate the time stamps in the vette log with the MTA
logs (for emal approval) or the web server logs (for web approval).
This can usually get you at least an IP address for the moderator.

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
Mailman-Users mailing list Mailman-Users <at> python.org
http://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: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org

Dennis Putnam | 2 May 15:28 2012
Picon

Re: Dumb Me Tried to Update Mandriva (Again)

Of course I did not expect this to be easy. After restoring the Mailman
directory as suggested, mailman will not start:

Traceback (most recent call last):
  File "/usr/sbin/mailmanctl", line 106, in <module>
    from Mailman import mm_cfg
ImportError: Bad magic number in /usr/lib/mailman/Mailman/mm_cfg.pyc

On 4/28/2012 6:40 PM, Mark Sapiro wrote:
> On 4/28/2012 3:02 PM, Dennis Putnam wrote:
>> On 4/28/2012 4:57 PM, Mark Sapiro wrote:
>>> On 4/28/2012 1:24 PM, Dennis Putnam wrote:
>>>> As usual my attempt to update Mandriva has destroyed Mailman. This time
>>>> the update failed and rather than move forward, I reverted back to the
>>>> working version (2010.2). However, I must have missed something because
>>>> I am getting the following error when I try to access Mailman web:
>>>>
>>>> Apr 28 16:07:42 2012 admin(17726):
>>>>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  pr 28 16:07:42 2012
>>>> admin(17726):  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at>  <at> 
>>>> admin(17726): [----- Mailman Version: 2.1.13 -----]
>>>> admin(17726): [----- Traceback ------]
>>>> admin(17726): Traceback (most recent call last):
>>>> admin(17726):   File "/usr/lib/mailman/scripts/driver", line 97, in run_main
>>>> admin(17726):     pkg = __import__('Mailman.Cgi', globals(), locals(),
>>>> [scriptname])
>>>> admin(17726):   File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 35,
>>>> in <module>
>>>> admin(17726):     from Mailman import MailList
>>>> admin(17726):   File "/usr/lib/mailman/Mailman/MailList.py", line 64, in
(Continue reading)

Mark Sapiro | 2 May 15:48 2012
Picon

Re: Dumb Me Tried to Update Mandriva (Again)

Dennis Putnam wrote:
>
>Of course I did not expect this to be easy. After restoring the Mailman
>directory as suggested, mailman will not start:
>
>Traceback (most recent call last):
>  File "/usr/sbin/mailmanctl", line 106, in <module>
>    from Mailman import mm_cfg
>ImportError: Bad magic number in /usr/lib/mailman/Mailman/mm_cfg.pyc

It appears your system Python is now different from the one that
compiled all the .pyc files. Just do

  rm -r /path/to/Mailman/*.pyc

This will remove all the compiled Python modules and they will be
recompiled as needed.

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
Mailman-Users mailing list Mailman-Users <at> python.org
http://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: http://mail.python.org/mailman/options/mailman-users/gmmu-mailman-users%40m.gmane.org

(Continue reading)


Gmane