[Mailman-Users] problem e.g. with subscription of new members

[Mark Sapiro]

Werner Spirk wrote:
>
>I have installed mailman-2.1.14 on NFS.
>We use NFS as the common platform between mailman server and
>WWW server.
>
>The problem is that it could happen that
>the subscription of new members ether via the add-members cmd
>or via the WWW surface as an admin did not do:
>the members have got welcome messages, there are log entries
>in the subscribe log but the members aren't in the list
>(no changes/mail addresses in the pck-file).
>
>If you repeat the subscription directly after the first trail
>it will normally do.
>
>There were no activities on the mailman server at that times.


There is an issue that can cause this behavior, but it only occurs if
two parallel processes, e.g. the member add and another member add or
a post to the same list, occur within the same second.


>In the locks log there can be an entry - not always
>when  subsrcriptions fails:
><list>.lock lifetime has expired, breaking
>But there are no lock/unlock entries.


You can get more information including lock/unlock entries in the locks
log by putting

LIST_LOCK_DEBUGGING = On

in mm_cfg.py and restarting Mailman.

Is there anything in Mailman's error log?

I have attached a patch (list_reload.patch.txt) that addresses the
issue I mention above. It may help, but I suspect some kind of NFS
delays are involved. Try setting LIST_LOCK_DEBUGGING = On and report
what's in the locks log.

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

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: list_reload.patch.txt
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20110106/34b1c955/attachment.txt>