[Mailman-Users] multiple hosts mounting mailman nfs

[Troy Knabe]

On Dec 19, 2007, at 7:30 AM, Dennis Black wrote:

> Troy Knabe wrote:
>> I have two smtp servers that we use dns round robin for load
>> balancing.  I can run it one server at a time, but I am running into
>> some pid lock file issues when I try to run them simultaneously.
>>
>> Any suggestions?
>>
>> Thanks
>> -Troy
>>
>>
> Troy,
> My configuration:
>
> A carp machine answers "mailman.srv.ualberta.ca" and alternates  
> inbound
> messages
> to two machines behind the carp machine, "mailman1" and "mailman2",
> NFS-mounted to a third machine, "mailmandb".
>
> Mailman 2.1.9 and Postfix are installed on all three.
>
> Beginning at about line 119, change /usr/local/bin/mailmanctl, so it  
> reads:
>
> # Locking contantsa
> fname = socket.gethostname()
> partz = fname.split('.')
> hostnamez = partz.pop(0)
> lyst = ['master-qrunner', hostnamez]
> osmyname = "-".join(lyst)
> LOCKFILE = os.path.join(mm_cfg.LOCK_DIR, osmyname)
> # Since we wake up once per day and refresh the lock, the  
> LOCK_LIFETIME
>
> Mount /usr/local/mailman/locks on NFS.
>
> This creates lockfiles named by hosts:
>
> /usr/local/mailman/locks
>
> -rw-rw-r--  2 mailman  mailman  79 Dec 19 17:29 master-qrunner- 
> mailman1
> -rw-rw-r--  2 mailman  mailman  79 Dec 19 17:29
> master-qrunner-mailman1.mailman1.srv.ualberta.ca.13791
> -rw-rw-r--  2 mailman  mailman  78 Dec 19 15:45 master-qrunner- 
> mailman2
> -rw-rw-r--  2 mailman  mailman  78 Dec 19 15:45
> master-qrunner-mailman2.mailman2.srv.ualberta.ca.5476
> -rw-rw-r--  2 mailman  mailman  80 Dec 20 13:35 master-qrunner- 
> mailmandb
> -rw-rw-r--  2 mailman  mailman  80 Dec 20 13:35
> master-qrunner-mailmandb.mailmandb.srv.ualberta.ca.7897
>
> As Brad points out, each of the two machines has its own queue, but  
> the
> /lists and /archives
> are common NFS.
>
> -- 
> Dennis Black
> System Admin
> Academic Information and Communication Technologies (AICT)
> (780-)492-9329
> This communication is intended for the use of the recipient to which
> it is addressed, and may contain confidential, personal, and/or
> privileged information. Please contact us immediately if you are not
> the intended recipient of this communication. If you are not the
> intended recipient of this communication, do not copy, distribute,
> or take action on it. Any communication received in error, or
> subsequent reply, should be deleted or destroyed.
>
> ------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users at python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: http://mail.python.org/mailman/options/mailman-users/knabe%404j.lane.edu
>
> Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Thanks to Dennis and Brad.  It appears that I now have this working  
perfectly, your instructions for mailmanctl were very easy to follow,  
even for a non-programmer.  I already had created /usr/local/mailman  
so I took qfiles and sym linked it back to local disks (with the same  
path on both hosts).  Messages seem to flowing correctly now.

Thanks again!

-Troy