Meaning if your server1 goes down, your SOL. Needs to have master master MySQL replication. You can either use the same broker, or cluster them.
-- Jeremy McSpadden Flux Labs, Inc | http://www.fluxlabs.net<http://www.fluxlabs.net/> | Endless Solutions Office : 850-250-5590x101<tel:850-250-5590;101> | Cell : 850-890-2543<tel:850-890-2543> | Fax : 850-254-2955<tel:850-254-2955> On Mar 20, 2013, at 8:57 AM, "Raymond Norton" <[email protected]<mailto:[email protected]>> wrote: The cluster setup was a bit of a mystery for some. Me being one of them. These are the steps I took to get it working on my 1.1.2 setup. For now, I am using scanner 1 to host the database and act as the broker for both scanners. Scanner 1: 1. Set up per docs (http://topdog-software.com/oss/baruwa/1.1.2/docs/baruwa.pdf) 2. Configure mysql for remote connections 3. Grant baruwa user from scanner 2 privileges to the baruwa database Scanner 2: 1. Set up per docs 2. Edit all /etc/postfix/mysql-x files and replace localhost with scanner 1 address. 3. Edit /etc/baruwa/settings.py, replacing localhost for mysql with scanner 1 address and change Broker_Host address to the same. 4. Edit database configuration in /etc/MailScanner/conf.d/baruwa.conf (point to scanner 1) I believe this is it.. No need to edit any other settings or files. I did initialize both boxes from the command line, but am told that is not necessary. With the above setup I am able to release or delete messages that were processed on scanner 2 from scanner 1 Feel free to correct my findings and post on the wiki. -- Raymond Norton LCTN 952.955.7766 _______________________________________________ Keep Baruwa FREE - http://pledgie.com/campaigns/12056
_______________________________________________ Keep Baruwa FREE - http://pledgie.com/campaigns/12056
