The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

Hi Nathan,

It *looks like* (I may be mistaken) a Debian issue. As far as I remeber, Sympa is not supposed to cry if the database exists when it is installed.
A suggestion from a collegue of mine (that I fully endorse): give another name to the database for the second instance, so that it install correctly. Then drop this second database and change the sympa.conf of the second instance to match the name of the actual database.
Good to go.

Regards,

David

Le 23/08/2010 22:37, Nathan Gibbs a écrit :

address@concealed">

Are there any guidelines / howtos for setting up a sympa cluster.

My initial attempt using the debian packages didn't work out so well.

I initially asked for help in the linux.debian.user newsgroup.
SNIP

What I'd like to end up with is a 2 node sympa cluster that sits behind a
server doing IPVS to load balance between them.

To the users of the web interface it would appear like one server.

Both installs need to reference the same sympa DB on the DB server, for
obvious reasons.

When trying to install on the second node the package tries to
create the DB then the sympa install fails completely because the DB already
exists due to the successful install on the first node.

Is what I'm trying to do even possible with the debian package?
If so, how do I get it to do it?

End SNIP

After looking around in the list archives it appears that this may involve a
bit more than just a common back end DB.  So I think I'd better ask around
before trying again.

Thanks

  

--
David Verdin
Comité réseau des universités

Due to the limitations of human brain, I fail to remember all the mails.
So if you want your bug reports or feature requests for Sympa to be processed, please post them to the Sympa tracker