Hello Stefan, Answers are inline.
When could you last successfully start (the server on) this database? The night before. I have been working on automating our start up and shutdown.
What happened / did you do since the last successful start? Rebooted the machine.
Did you shutdown the server cleanly? The database is running on a VirtualBox VM and it appears that Ubuntu is shutting down the VM hard and monetdb5-sql scripts is not be run with the stop parameter.
Did the server crash? If so, how? Described above.
Did you manually change any of the directories/files in your dbfarm, in particular <dbfarm>/sql_logs/sql/log ? No.
Is the file systems where your dbfarm resides "sane", i.e., not corrupted? No I checked the file system with fsck.
We are in the process of setting up our production runtime environment in which MonetDb is central. From reading the documentation, it is not clear whether or not monetdbd will start and stop unlocked databases at system start up and shutdown after they have been started once with the Monetdb command. Is this correct, or do we need to run the "monetdb start db" command each time after monetdbd starts and "monetdb stop db" before monetdbd shutsdown? If so where do you recommend add the commands? To the /etc/init.d/monetdb5-sql file? Our server is running with a UPS and we are working to get the VM to shutdown cleanly; however, things can still go wrong at some point and result in an unclean hard shutdown. If that happens and we see an error like this, is it possible to fix the corruption? Thanks Doug Service On 03/01/2015 01:23 PM, Stefan Manegold wrote:
Hi,
these are the crucial lines in your log:
2015-03-01 16:11:36 MSG dbprod[5743]: !SQLException:SQLinit:Catalogue initialization failed 2015-03-01 16:11:36 MSG dbprod[5743]: !ERROR: Could not read the version number from the file 'sql_logs/sql//log'.
When could you last successfully start (the server on) this database?
What happened / did you do since the last successful start?
Did you shutdown the server cleanly?
Did the server crash? If so, how?
Did you manually change any of the directories/files in your dbfarm, in particular <dbfarm>/sql_logs/sql/log ?
Is the file systems where your dbfarm resides "sane", i.e., not corrupted?
Best, Stefan
----- Original Message -----
A monet database we have created will not start with the following error:
sudo monetdb start dbprod starting database 'dbprod'... FAILED start: starting 'dbprod' failed: database 'dbprod' did not initialise the sql scenario
Is it possible to recover from an error like this?
Here is the relevant log file portion.
2015-03-01 16:11:36 MSG dbprod[5743]: arguments: /usr/bin/mserver5 --dbpath=/var/lib/monetdb/dbprod --set merovingian_uri=mapi:monetdb://qbdata:42000/dbprod --set mapi_open=false --set mapi_port=0 --set mapi_usock=/var/lib/monetdb/dbprod/.mapi.sock --set monet_vault_key=/var/lib/monetdb/dbprod/.vaultkey --set gdk_nr_threads=2 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2015-03-01 16:11:36 ERR dbprod[5743]: !mvc_init: unable to create system tables 2015-03-01 16:11:36 MSG dbprod[5743]: # MonetDB 5 server v11.19.7 "Oct2014-SP1" 2015-03-01 16:11:36 MSG dbprod[5743]: # Serving database 'dbprod', using 2 threads 2015-03-01 16:11:36 MSG dbprod[5743]: # Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked 2015-03-01 16:11:36 MSG dbprod[5743]: # Found 1.955 GiB available main-memory. 2015-03-01 16:11:36 MSG dbprod[5743]: # Copyright (c) 1993-July 2008 CWI. 2015-03-01 16:11:36 MSG dbprod[5743]: # Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved 2015-03-01 16:11:36 MSG dbprod[5743]: # Visithttp://www.monetdb.org/ for further information 2015-03-01 16:11:36 MSG dbprod[5743]: # Listening for UNIX domain connection requests on mapi:monetdb:///var/lib/monetdb/dbprod/.mapi.sock 2015-03-01 16:11:36 MSG dbprod[5743]: !SQLException:SQLinit:Catalogue initialization failed 2015-03-01 16:11:36 MSG dbprod[5743]: !ERROR: Could not read the version number from the file 'sql_logs/sql//log'. 2015-03-01 16:11:36 MSG merovingian[1568]: database 'dbprod' (5743) has exited with exit status 0 2015-03-01 16:11:36 MSG merovingian[1568]: database 'dbprod' has shut down 2015-03-01 16:11:36 ERR control[1568]: (local): failed to fork mserver: database 'dbprod' did not initialise the sql scenario 2015-03-01 16:12:45 MSG control[1568]: (local): served status list 2015-03-01 16:12:45 MSG control[1568]: (local): locked database 'dbprod' 2015-03-01 16:13:09 MSG control[1568]: (local): served status list 2015-03-01 16:13:09 MSG control[1568]: (local): released database 'dbprod' 2015-03-01 16:13:19 MSG control[1568]: (local): served status list 2015-03-01 16:13:19 MSG merovingian[1568]: starting database 'dbprod', up min/avg/max: 0s/2d/1w, crash average: 0.00 0.50 0.17 (15-10=5) 2015-03-01 16:13:20 MSG merovingian[1568]: sending process 5769 (database 'dbprod') the TERM signal
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list