Please look into your merovingian.log file, it will contain more information why the database "does not allow connections".
The logs simply have this: error.log: TME 2008-06-17 16:06:43 ERR merovingian[941]: client error: database 'mydb' does not allow connections msg.log: TME 2008-06-17 16:06:43 MSG merovingian[941]: Merovingian 0.7 starting ... MSG merovingian[941]: monitoring dbfarm /mnt/MonetDB5/dbfarm MSG merovingian[941]: listening for TCP connections on xyz:50000 MSG bhtg[948]: executing '/usr/bin/mserver5' for database 'mydb' MSG merovingian[941]: listening for UDP messages on xyz:50000 MSG merovingian[941]: starting database mydb due to control signal MSG merovingian[941]: starting database 'mydb', up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (0-0=0) MSG merovingian[941]: database 'mydb' already running since 2008-06-17 16:06:43, up min/avg/max: 0/0/0, crash average: 0.00 0.00 0.00 (1-0=0) MSG bhtg[948]: !WARNING: BBPdir: initializing BBP. MSG bhtg[948]: # MonetDB server v5.6.0, based on kernel v1.24.0 MSG bhtg[948]: # Serving database 'mydb' MSG bhtg[948]: # Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs dynamically linked MSG bhtg[948]: # Copyright (c) 1993-2008 CWI, all rights reserved MSG bhtg[948]: # Visit http://monetdb.cwi.nl/ for further information MSG bhtg[948]: # Listening for connection requests on mapi:monetdb://xyz:50001/
Also, check with `monetdb status` if the database is online, and not under maintenance.
Yes the status if fine. The output just before the failure even says it was started successfully. And this is happening during boot up so there is no way for the db to be in maintenance mode. Any tips on where to go from here? Thanks.