Date: 2013-11-15 17:11:36 +0100
From: Kostis Kyzirakos <<kostis.kyzirakos>>
To: Merovingian devs <>
Version: 11.15.17 (Feb2013-SP5)

Last updated: 2013-12-03 13:59:36 +0100

Comment 19338

Date: 2013-11-15 17:11:36 +0100
From: Kostis Kyzirakos <<kostis.kyzirakos>>

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0
Build Identifier:

The user is allowed to start monetdbd on a given dbfarm that may have not yet been initialized.

Reproducible: Always

Steps to Reproduce:

1. Create a new directory
   export TEMP_DB_FARM="/tmp/$(echo ${RANDOM})"
   mkdir ${TEMP_DB_FARM}

2. Start monetdbd without initializing the new directory
   monetdbd start ${TEMP_DB_FARM}

3. monetdbd will start without complaining about the fact that the dbfarm has not been initialized. The user is able to create/start/stop/... databases.

monetdb create sound
created database in maintenance mode: sound

monetdb start sound
starting database 'sound'... done

monetdb stop sound
stopping database 'sound'... done

4. However, the user is unable to stop or manage monetdbd.

monetdbd stop ${TEMP_DB_FARM}
unable to read properties from .: No such file or directory

monetdbd get all ${TEMP_DB_FARM}
unable to read properties from .: No such file or directory

Expected Results:

monetdbd should shamelessly refuse to start serving an uninitialized dbfarm

Comment 19339

Date: 2013-11-15 19:12:51 +0100
From: MonetDB Mercurial Repository <>

Changeset b215b05c5c79 made by Fabian Groffen fabian@monetdb.org in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b215b05c5c79

Changeset description:

merovingian: refuse to startup when properties are missing

dbfarms that we can't read .merovingian_properties from are either
messed up in terms of permissions, or created by a simple mkdir, such as
in bug #3398.  Refuse starting up since this affects any other
operations on monetdbd (although it functions just fine), such as
shutdown via monetdbd stop ....

Comment 19340

Date: 2013-11-15 19:13:21 +0100
From: @grobian

Fixed in Feb2013 branch. Should go in next release. Thanks!

Comment 19381

Date: 2013-12-03 13:59:36 +0100
From: @sjoerdmullender

Feb2013-SP6 has been released.