Hi David, On Fri, Aug 27, 2010 at 01:01:01PM +0200, David Verdin wrote:
Here is a copy of a report by N. Gibbs in sympa-users: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? Sympa is not supposed to crash if the database already exists.Is there any Debian specific process that makes it crash? What is it and why does it make Sympa crash?
Thanks for the bugreport.It seems to me that sympa does not crash, but the surrounding install routines fails.
The install routines should offer the choice of setting up database configuration, vut should also allow to skip that and instead do it manually. The ability to skip guided setup is exactly to make room for more advanced situations like multi-node setups.
If indeed it is possible to skip guided database configuration, then this is not really a bug, but a considerate limitation in the user-friendly wrapping: The administrator should then choose to skip, and instead customize configuration files and databases manually after package install.
If it is not possible to skip database configuration, then there is indeed a bug in the packaging routines, which we should fix.
Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
