McKennirey.Matthew wrote:

We are running multiple mserver5 processes under a single merovingian daemon. Our start up script looks like this:

 # start the merovingian daemon, the port for the daemon is defined in

$MDB_HOME/etc/monetdb5.conf startproc -s -u $MDB_USER -g $MDB_GROUP $MDB_BINDIR/merovingian

echo "Starting DATABASE1."
startproc -f -t  5 -u $MDB_USER -g $MDB_GROUP $MDB_BINDIR/mserver5

--dbname=DATABASE1 --dbinit="include sql;" --set mapi_port=50010 &

echo "Starting DATABASE2"
startproc -f -t  5 -u $MDB_USER -g $MDB_GROUP $MDB_BINDIR/mserver5

--dbname=DATABASE2 --dbinit="include sql;" --set mapi_port=50011 &

echo "Starting DATABASE3."
startproc -f -t  5 -u $MDB_USER -g $MDB_GROUP $MDB_BINDIR/mserver5

--dbname=DATABASE3 --dbinit="include sql;" --set mapi_port=50012 &

echo -e "Done"

This is not how merovingian is meant to be used. If you start mservers yourself next to merovingian, merovingian cannot control those mservers. The result you see is that merovingian starts to assign the databases to other ports after they have crashed.

If you want to have merovingian start those databases immediately upon startup, give the database names to the merovingian startup:

startproc -s -u $MDB_USER -g $MDB_GROUP $MDB_BINDIR/merovingian DATABASE1 DATABASE2 DATABASE3

merovingian will never retain port numbers, as it simply looks for a free port, which is enough given that you should always connect through merovingian (port 50000).

I hope this helps.