On 20-02-2008 02:26:30 +0100, Michael Schmidt wrote:
Hi Fabian,
thanks for your response. I tried to install the lates branch, but get a compile error. The latest nightly build works fine, but does not yet contain the changes, so I will probably wait until tomorrow evening.
Unfortunately I had to do a lot of cross work, so all fixes are in stable only, whereas the feature you want are in the current branch, which doesn't include the fixes (yet).
In meantime, I changed the script as follows:
=============== begin code // create database (I will replace the ugly sleeps as soon as your fixes are available to me)
monetdb create SchemaDBLP1000 sleep 2
The sleep here is already not necessary, as the tool already only returns once the necessary directories are created.
monetdb start SchemaDBLP1000 sleep 2
// load document
mclient -lsql -dSchemaDBLP1000 < document.sql
// stop the database again
monetdb stop SchemaDBLP1000 sleep 2 monetdb destroy -f SchemaDBLP1000 sleep 2
Same for destroy, if it returns before the database is really destroyed, then that is a bug.
=============== end code
The merovingian process is now started initially, from outside the script. Starting and stopping seems to work fine. First of all, do you agree that this is the intended way (except for the sleeps, which may fail)?
Yes, your script looks fine. You could add some monetdb create bla || die "Failed to create bla" kind of structures to catch problems, but if everything succeeds then you script should work.
However, also in the scenario above exactly every second run fails. The log for four consecutive runs is provided at the end of the mail.
Ok.
If so, could you please send me the merovingian.log file?
Here it is, for four consecutive runs of the script above. In run 2 and 4 (which fail), there is a "MSG merovingian[5790]: database 'SchemaDBLP1000' (5832) was killed by signal 11", which seems to reflect the problem. Unfortunately, I do not know what this message means?
signal 11 is SIGSEGV, so the database just segfaulted (crashed). Your log shows an interesting pattern. It just looks like the database on the even startups sees some left over garbage from the previous run (e.g. an logfile). However, that should not be possible, as destroy is supposed to throw that away as well. I'm affraid I can't answer this right away, we will have to reproduce this to see what's going on exactly.
=============== begin log ////////////////// INITIAL STARTUP TME 2008-02-20 03:12:30 MSG merovingian[5790]: Merovingian 0.6 starting ... MSG merovingian[5790]: monitoring dbfarm /usr/local/src/MonetDB/var/MonetDB5/dbfarm MSG merovingian[5790]: listening for connections on gemma:50000 ////////////////// RUN 1 MSG merovingian[5790]: starting database SchemaDBLP1000 due to control signal MSG SchemaDBLP1000[5801]: executing '/usr/local/src/MonetDB/bin/mserver5' for database 'SchemaDBLP1000' MSG merovingian[5790]: starting database 'SchemaDBLP1000', up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (0-0=0) MSG SchemaDBLP1000[5801]: !WARNING: BBPdir: initializing BBP. MSG SchemaDBLP1000[5801]: # MonetDB server v5.4.1, based on kernel v1.22.1 MSG SchemaDBLP1000[5801]: # Serving database 'SchemaDBLP1000' MSG SchemaDBLP1000[5801]: # Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs dynamically linked MSG SchemaDBLP1000[5801]: # Copyright (c) 1993-2008 CWI, all rights reserved MSG SchemaDBLP1000[5801]: # Visit http://monetdb.cwi.nl/ for further information MSG SchemaDBLP1000[5801]: # Listening for connection requests on mapi:monetdb://gemma:50001/ MSG merovingian[5790]: database 'SchemaDBLP1000' already running since 2008-02-20 03:12:41, up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (1-0=0) MSG merovingian[5790]: redirecting client 127.0.0.1:24780 for database 'SchemaDBLP1000' to mapi:monetdb://gemma:50001/ MSG merovingian[5790]: stopping database SchemaDBLP1000 due to control signal MSG SchemaDBLP1000[5801]: # MonetDB/SQL module v2.22.1 loaded MSG merovingian[5790]: database 'SchemaDBLP1000' (5801) has exited with exit status 0 ////////////////// RUN 2 MSG merovingian[5790]: starting database SchemaDBLP1000 due to control signal MSG SchemaDBLP1000[5832]: executing '/usr/local/src/MonetDB/bin/mserver5' for database 'SchemaDBLP1000' MSG merovingian[5790]: starting database 'SchemaDBLP1000', up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (0-0=0) MSG SchemaDBLP1000[5832]: !WARNING: BBPdir: initializing BBP. MSG SchemaDBLP1000[5832]: # MonetDB server v5.4.1, based on kernel v1.22.1 MSG SchemaDBLP1000[5832]: # Serving database 'SchemaDBLP1000' MSG SchemaDBLP1000[5832]: # Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs dynamically linked MSG SchemaDBLP1000[5832]: # Copyright (c) 1993-2008 CWI, all rights reserved MSG SchemaDBLP1000[5832]: # Visit http://monetdb.cwi.nl/ for further information MSG SchemaDBLP1000[5832]: # Listening for connection requests on mapi:monetdb://gemma:50001/ MSG merovingian[5790]: database 'SchemaDBLP1000' already running since 2008-02-20 03:12:51, up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (1-0=0) MSG merovingian[5790]: redirecting client 127.0.0.1:24782 for database 'SchemaDBLP1000' to mapi:monetdb://gemma:50001/ MSG merovingian[5790]: database 'SchemaDBLP1000' (5832) was killed by signal 11 ////////////////// RUN 3 MSG merovingian[5790]: starting database SchemaDBLP1000 due to control signal MSG SchemaDBLP1000[5868]: executing '/usr/local/src/MonetDB/bin/mserver5' for database 'SchemaDBLP1000' MSG merovingian[5790]: starting database 'SchemaDBLP1000', up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (0-0=0) MSG SchemaDBLP1000[5868]: !WARNING: BBPdir: initializing BBP. MSG SchemaDBLP1000[5868]: # MonetDB server v5.4.1, based on kernel v1.22.1 MSG SchemaDBLP1000[5868]: # Serving database 'SchemaDBLP1000' MSG SchemaDBLP1000[5868]: # Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs dynamically linked MSG SchemaDBLP1000[5868]: # Copyright (c) 1993-2008 CWI, all rights reserved MSG SchemaDBLP1000[5868]: # Visit http://monetdb.cwi.nl/ for further information MSG SchemaDBLP1000[5868]: # Listening for connection requests on mapi:monetdb://gemma:50001/ MSG merovingian[5790]: database 'SchemaDBLP1000' already running since 2008-02-20 03:12:59, up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (1-0=0) MSG merovingian[5790]: redirecting client 127.0.0.1:24784 for database 'SchemaDBLP1000' to mapi:monetdb://gemma:50001/ MSG merovingian[5790]: stopping database SchemaDBLP1000 due to control signal MSG SchemaDBLP1000[5868]: # MonetDB/SQL module v2.22.1 loaded MSG merovingian[5790]: database 'SchemaDBLP1000' (5868) has exited with exit status 0 ////////////////// RUN 4 MSG merovingian[5790]: starting database SchemaDBLP1000 due to control signal MSG SchemaDBLP1000[5911]: executing '/usr/local/src/MonetDB/bin/mserver5' for database 'SchemaDBLP1000' MSG merovingian[5790]: starting database 'SchemaDBLP1000', up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (0-0=0) MSG SchemaDBLP1000[5911]: !WARNING: BBPdir: initializing BBP. MSG SchemaDBLP1000[5911]: # MonetDB server v5.4.1, based on kernel v1.22.1 MSG SchemaDBLP1000[5911]: # Serving database 'SchemaDBLP1000' MSG SchemaDBLP1000[5911]: # Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs dynamically linked MSG SchemaDBLP1000[5911]: # Copyright (c) 1993-2008 CWI, all rights reserved MSG SchemaDBLP1000[5911]: # Visit http://monetdb.cwi.nl/ for further information MSG SchemaDBLP1000[5911]: # Listening for connection requests on mapi:monetdb://gemma:50001/ MSG merovingian[5790]: database 'SchemaDBLP1000' already running since 2008-02-20 03:13:09, up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (1-0=0) MSG merovingian[5790]: redirecting client 127.0.0.1:24786 for database 'SchemaDBLP1000' to mapi:monetdb://gemma:50001/ MSG merovingian[5790]: database 'SchemaDBLP1000' (5911) was killed by signal 11