monetdb start reports crash in merovingian.log

[monetdb-team]

Date: 2014-06-13 15:13:42 +0200
From: @bartscheers
To: Merovingian devs <>
Version: 11.17.17 (Jan2014-SP2)
CC: @hannesmuehleisen

Last updated: 2014-10-31 14:14:10 +0100

Comment 19842

Date: 2014-06-13 15:13:42 +0200
From: @bartscheers

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

creating, releasing and starting a new database prints a merovingian message in in the merovingian.log. Also for stopping destroying, creating, releasing and starting an existing database.
Everything seems to work fine, but the message assumes it isn't.

Reproducible: Always

Steps to Reproduce:

1. monetdb create mydb; monetdb release mydb; monetdb start mydb

Actual Results:

MSG merovingian[26144]: database 'mydb' has crashed after start on 1970-01-01 00:59:59, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0)

Expected Results:

No crash

Same results for the python monetdb.control module

Comment 20008

Date: 2014-08-07 14:43:40 +0200
From: @hannesmuehleisen

Confirmed, seeing these messages too.

Comment 20009

Date: 2014-08-07 15:25:04 +0200
From: MonetDB Mercurial Repository <>

Changeset 077f26b22108 made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

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

Changeset description:

Remove writing "bla:" to .gdk_lock file.
It doesn't seem to affect anything, despite the comment.
This fixes bug #3497.

Comment 20359

Date: 2014-10-31 14:14:10 +0100
From: @sjoerdmullender

Oct2014 has been released.