ankush grover wrote: > >I am running mailman 2.1.5 version on RHEL ES 4.1 with Postfix 2.1.5. >I am trying to configure mailman replication that is there will be a >primary mailman server and a secondary mailman server. The secondary >server will keep the lists and data in sync with the production and >will be brought up manually whenver primary server goes down. >Currently I am syncing the data b/w primary and secondary servers >through rsync utility, however there are some issues like mailman does >not shows the mailing lists on the secondary server. I would like to >know what is the best way to configure replica of mailman primary >server and what changes needs to be done for making secondary server >as live mailman server.
The lists do not show on the web interface of the backup server because VIRTUAL_HOST_OVERVIEW is On (the default) and the host name of the backup server is different from the primary server. If you set VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py, you'll see the lists on the backup, but if it is ever necessary to switch to the backup, presumably you'll do that by changing the primary name's IPs in DNS to point to the backup, in which case you'll be accessing the backup via the primary names and you'll see the lists anyway. >Data currently being sync is /usr/lib/mailman(full directory), >/var/lib/mailman/data and /var/lib/mailman/lists directories What about archives? Why not just rsync all of /var/lib/mailman? -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
