This has happened twice in two days so far. All I do is insert rows in a loop and eventually I hit a segmentation fault. [...] 160000 done - 2.1121% in 432.97 (0.0026 avg) 161000 done - 2.1253% in 435.68 (0.0027 avg) 162000 done - 2.1385% in 438.28 (0.0026 avg) 163000 done - 2.1517% in 442.37 (0.0041 avg) Segmentation fault monetdb@dev3:~$ MonetDB/bin/monetdb status name state uptime health last crash test running 2m 56s 34%, 0s 2009-10-06 15:45:01 Is there any way to recover from this? I tried stopping the db but it would just hang. I tried restarting monetdb/merovingian and starting the db again but it said this: starting database 'test'... FAILED: starting 'test' failed: database 'test' has inconsistent state (running but dead), review merovingian's logfile for any peculiarities This seems to be the log from when the crash occured: 2009-10-07 12:47:20 MSG merovingian[3081]: client localhost:40950 has disconnected from proxy 2009-10-07 12:47:20 MSG merovingian[3081]: client localhost:38976 has disconnected from proxy 2009-10-07 12:47:20 MSG merovingian[3081]: database 'test' (3865) was killed by signal 11 2009-10-07 14:03:29 MSG merovingian[3081]: database 'test' has crashed after start on 2009-10-06 15:45:01, attempting restart, up min/avg/max: 0s/0s/0s, crash average: 1.00 0.20 0.07 (2-0=2) 2009-10-07 14:03:30 MSG test[6042]: arguments: /home/guillaume/MonetDB/bin/mserver5 --config=/home/guillaume/MonetDB/etc/monetdb5.conf --dbnam e=test --dbinit=include sql; --set monet_daemon=yes --set mapi_open=false --set mapi_autosense=true --set mapi_port=50001 --set monet_vault_key=/home/guillaume/MonetDB/var/MonetDB5/dbfarm/test/.vaultkey And this is the log when I tried to start it: 2009-10-07 14:08:39 ERR merovingian[6059]: failed to fork mserver: database 'test' has inconsistent state (running but dead), review merovingian's logfile for any peculiarities If I recompile with debug mode enabled will it dump a stack trace somewhere when it segfaults? Thanks, Guillaume