Hi Michael, On 19-02-2008 20:22:12 +0100, Michael Schmidt wrote:
Hi,
I'm trying to run a benchmark using the latest February stable (on an Ubuntu 7.04 - Feisty Fawn), and want to cleanup the database entirely between two single runs. Basically, my benchmark script is as follows:
//////////////////// START CODE // kill all processes and remove databases) // (I know this is not the intended way, but using // > monetdb stop test // > monetdb destroy -f test // while not restarting merovingian basically results in // in the same error)
killall -9 merovingian killall -9 mserver5 killall -9 mclient rm -Rf /usr/local/src/MonetDB/var/MonetDB5/dbfarm/*
I fixed a couple of bugs in merovingian/monetdb tonight, and added a feature in the current branch for monetdb stop to have a -w flag that waits for the action to complete. I don't understand yet why you need the kill -KILL on merovingian (it whould kill all mservers in a much nicer way for you than with -KILL when you just normally kill merovingian), but I from what I understand merovingian is just not stopping the databases? If so, could you please send me the merovingian.log file?
// start the merovingian server
merovingian sleep 2
// wait until ports 50000 and 50001 are free, // as they might still be blocked (I inserted this piece // of code because I thought busy port allocation might // be the cause of failure)
[code works fine (ommited)]
// create and start the database
monetdb create test; sleep 2; monetdb start test; sleep 2;
with the new code in the HEAD you could do monetdb start -w test instead avoid the sleep, and also cover cases where 2 secs is not enough ;) I just realise that I forgot to make monetdb have an appropriate exit code when it detects the started server crashes, but that shouldn't spoil the fun for now.