start: starting 'test' failed: database 'test' has crashed after starting, manual intervention needed, check merovingian's logfile for details
This is the error i get when i first tried to start a database, after a clean installation of the branch Mar2011, in MacOSX 10.6.6.
The log from merovingian is the following:
2011-02-18 12:46:14 MSG merovingian[21987]: Merovingian 1.3 (unreleased) starting
2011-02-18 12:46:14 MSG merovingian[21987]: monitoring dbfarm /Users/user/apps/MonetDB/var/monetdb5/dbfarm
2011-02-18 12:46:14 MSG merovingian[21987]: accepting connections on TCP socket 0.0.0.0:50000
2011-02-18 12:46:14 MSG merovingian[21987]: accepting connections on UNIX domain socket mapi_socket
2011-02-18 12:46:14 MSG discovery[21987]: listening for UDP messages on 0.0.0.0:50000
2011-02-18 12:46:14 MSG control[21987]: accepting connections on UNIX domain socket .merovingian_control
2011-02-18 12:46:14 MSG control[21987]: accepting connections on TCP socket 0.0.0.0:50001
2011-02-18 12:46:14 MSG discovery[21987]: new neighbour mydomain (mydomain)
2011-02-18 12:46:16 MSG discovery[21987]: registered neighbour mydomain:50001
2011-02-18 12:46:39 MSG control[21987]: (local): served status list
2011-02-18 12:46:43 MSG control[21987]: (local): created database 'test'
2011-02-18 12:46:48 MSG control[21987]: (local): served status list
2011-02-18 12:46:48 MSG control[21987]: (local): released database 'test'
2011-02-18 12:46:48 MSG discovery[21987]: new database mapi:monetdb://mydomain:50000/test (ttl=660s)
2011-02-18 12:46:54 MSG control[21987]: (local): served status list
2011-02-18 12:46:54 MSG merovingian[21987]: starting database 'test', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0)
2011-02-18 12:46:54 MSG test[22000]: arguments: /Users/user/apps/MonetDB/bin/mserver5 --config=/Users/user/apps/MonetDB/etc/monetdb5.conf --dbname=test --set merovingian_uri=mapi:monetdb://mydomain:50000/test --set mapi_open=false --set mapi_port=0 --set mapi_usock=/Users/user/apps/MonetDB/var/monetdb5/dbfarm/test/.mapi.sock --set monet_vault_key=/Users/user/apps/MonetDB/var/monetdb5/dbfarm/test/.vaultkey --set monet_daemon=yes
2011-02-18 12:46:54 MSG merovingian[21987]: database 'test' (22000) was killed by signal SIGSEGV
2011-02-18 12:47:04 ERR control[21987]: (local): failed to fork mserver: database 'test' has crashed after starting, manual intervention needed, check merovingian's logfile for details
Running mserver5 inside gdb as follows
run --dbname=test --dbinit='include tokenizer; include sql; include rdf;'
i get
Starting program: /Users/user/apps/MonetDB/bin/mserver5 --dbname=test --dbinit='include tokenizer; include sql; include rdf;'
Reading symbols for shared libraries .++++++++++++............ done
MonetDB 5 server v11.1.0
Not released
Serving database 'test', using 2 threads
Compiled for i386-apple-darwin10.6.0/64bit with 64bit OIDs dynamically linked
Found 1.637 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /Users/user/apps/MonetDB/etc/monetdb5.conf)
Reading symbols for shared libraries ... done
!TypeException:batcalc.rank_grp[3]:object code for command sql.rank_grp missing
!TypeException:batcalc.rank_grp[1]:object code for command sql.rank missing
!TypeException:batcalc.dense_rank_grp[3]:object code for command sql.dense_rank_grp missing
!TypeException:batcalc.dense_rank_grp[1]:object code for command sql.dense_rank missing
!TypeException:sql.zero_or_one[7]:object code for command calc.str missing
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x0000000000000000 in ?? ()
The same applies if i do not set the dbinit parameter.
Date: 2011-02-18 12:14:00 +0100
From: Babis <>
To: MonetDB5 devs <>
Version: 11.1.1 (Mar2011) [obsolete]
Last updated: 2011-03-28 17:31:36 +0200
Comment 15469
Date: 2011-02-18 12:14:00 +0100
From: Babis <>
start: starting 'test' failed: database 'test' has crashed after starting, manual intervention needed, check merovingian's logfile for details
This is the error i get when i first tried to start a database, after a clean installation of the branch Mar2011, in MacOSX 10.6.6.
The log from merovingian is the following:
2011-02-18 12:46:14 MSG merovingian[21987]: Merovingian 1.3 (unreleased) starting
2011-02-18 12:46:14 MSG merovingian[21987]: monitoring dbfarm /Users/user/apps/MonetDB/var/monetdb5/dbfarm
2011-02-18 12:46:14 MSG merovingian[21987]: accepting connections on TCP socket 0.0.0.0:50000
2011-02-18 12:46:14 MSG merovingian[21987]: accepting connections on UNIX domain socket mapi_socket
2011-02-18 12:46:14 MSG discovery[21987]: listening for UDP messages on 0.0.0.0:50000
2011-02-18 12:46:14 MSG control[21987]: accepting connections on UNIX domain socket .merovingian_control
2011-02-18 12:46:14 MSG control[21987]: accepting connections on TCP socket 0.0.0.0:50001
2011-02-18 12:46:14 MSG discovery[21987]: new neighbour mydomain (mydomain)
2011-02-18 12:46:16 MSG discovery[21987]: registered neighbour mydomain:50001
2011-02-18 12:46:39 MSG control[21987]: (local): served status list
2011-02-18 12:46:43 MSG control[21987]: (local): created database 'test'
2011-02-18 12:46:48 MSG control[21987]: (local): served status list
2011-02-18 12:46:48 MSG control[21987]: (local): released database 'test'
2011-02-18 12:46:48 MSG discovery[21987]: new database mapi:monetdb://mydomain:50000/test (ttl=660s)
2011-02-18 12:46:54 MSG control[21987]: (local): served status list
2011-02-18 12:46:54 MSG merovingian[21987]: starting database 'test', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0)
2011-02-18 12:46:54 MSG test[22000]: arguments: /Users/user/apps/MonetDB/bin/mserver5 --config=/Users/user/apps/MonetDB/etc/monetdb5.conf --dbname=test --set merovingian_uri=mapi:monetdb://mydomain:50000/test --set mapi_open=false --set mapi_port=0 --set mapi_usock=/Users/user/apps/MonetDB/var/monetdb5/dbfarm/test/.mapi.sock --set monet_vault_key=/Users/user/apps/MonetDB/var/monetdb5/dbfarm/test/.vaultkey --set monet_daemon=yes
2011-02-18 12:46:54 MSG merovingian[21987]: database 'test' (22000) was killed by signal SIGSEGV
2011-02-18 12:47:04 ERR control[21987]: (local): failed to fork mserver: database 'test' has crashed after starting, manual intervention needed, check merovingian's logfile for details
Running mserver5 inside gdb as follows
run --dbname=test --dbinit='include tokenizer; include sql; include rdf;'
i get
Starting program: /Users/user/apps/MonetDB/bin/mserver5 --dbname=test --dbinit='include tokenizer; include sql; include rdf;'
Reading symbols for shared libraries .++++++++++++............ done
MonetDB 5 server v11.1.0
Not released
Serving database 'test', using 2 threads
Compiled for i386-apple-darwin10.6.0/64bit with 64bit OIDs dynamically linked
Found 1.637 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /Users/user/apps/MonetDB/etc/monetdb5.conf)
Reading symbols for shared libraries ... done
!TypeException:batcalc.rank_grp[3]:object code for command sql.rank_grp missing
!TypeException:batcalc.rank_grp[1]:object code for command sql.rank missing
!TypeException:batcalc.dense_rank_grp[3]:object code for command sql.dense_rank_grp missing
!TypeException:batcalc.dense_rank_grp[1]:object code for command sql.dense_rank missing
!TypeException:sql.zero_or_one[7]:object code for command calc.str missing
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x0000000000000000 in ?? ()
The same applies if i do not set the dbinit parameter.
Comment 15560
Date: 2011-03-10 12:08:35 +0100
From: @grobian
I fixed this problem in this commit:
http://dev.monetdb.org/hg/MonetDB/rev/f85e828384eb
Thanks for your report
Comment 15640
Date: 2011-03-28 17:31:36 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
The text was updated successfully, but these errors were encountered: