Thanks for the suggestion.
The database is running on my laptop (MAC), so identifying the host isn¹t the problem. It is the dbfarm that is on the external drive, viewable as a directory on /Volumes/Samsung_T1/alt-dbfarm
Is there some sort of additional setup that needs to be done?
From the log file, You can see that it found and started the data base,
but then died when it failed to bind the UNIX socket. I should have shown that more clearly. Here are the logs:
2016-01-14 16:35:23 MSG maizeFullGenomeDB[1442]: # MonetDB 5 server v11.21.11 "Jul2015-SP1" 2016-01-14 16:35:23 MSG maizeFullGenomeDB[1442]: # Serving database 'maizeFullGenomeDB', using 8 threads 2016-01-14 16:35:23 MSG maizeFullGenomeDB[1442]: # Compiled for x86_64-apple-darwin14/64bit with 64bit OIDs and 128bit integers dynamically linked 2016-01-14 16:35:23 MSG maizeFullGenomeDB[1442]: # Found 16.000 GiB available main-memory. 2016-01-14 16:35:23 MSG maizeFullGenomeDB[1442]: # Copyright (c) 1993-July 2008 CWI. 2016-01-14 16:35:23 MSG maizeFullGenomeDB[1442]: # Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved 2016-01-14 16:35:23 MSG maizeFullGenomeDB[1442]: # Visit http://www.monetdb.org/ for further information 2016-01-14 16:35:23 MSG maizeFullGenomeDB[1442]: !IOException:mal_mapi.listen:operation failed: binding to UNIX socket file /Volumes/Samsung_T1/alt-dbfarm/maizeFullGenomeDB/.mapi.sock failed: No such file or directory 2016-01-14 16:35:23 MSG merovingian[740]: database 'maizeFullGenomeDB' (1442) has exited with exit status 0 2016-01-14 16:35:23 MSG merovingian[740]: database 'maizeFullGenomeDB' has shut down 2016-01-14 16:35:28 ERR merovingian[740]: client error: database 'maizeFullGenomeDB' started up, but failed to open up a communication channel
On 1/14/16, 4:11 PM, "users-list on behalf of Sjoerd Mullender" <users-list-bounces+lcj34=cornell.edu@monetdb.org on behalf of sjoerd@monetdb.org> wrote:
Perhaps you need to -h option: mclient -u monetdb -d maizeFullGenomeDB -h HOST where HOST is the name of the machine the database runs on.
On 01/14/2016 04:48 PM, Lynn Carol Johnson wrote:
Hello -
I am running monetdb with the July2015 service pack on MAC OSX. I have no problem running and connecting to a dbfarm that lives on my MAC. But I want to test a very large data set so have created a dbfarm on a Samsung T1 SSD external drive that is USB connected to my MAC.
I have successfully started monetdbd server and have attached to my dbfarm. I created/released a new database. Yet when I attempt to run mClient it fails. Here is the ³get all² command:
rs-btlcj34lt:testMapiSock lcj34$ monetdbd get all /Volumes/Samsung_T1/alt-dbfarm
property value
hostname rs-btlcj34lt.maize.cornell.edu
dbfarm /Volumes/Samsung_T1/alt-dbfarm
status monetdbd[740] 1.7 (Jul2015-SP1) is serving this dbfarm
mserver /Users/lcj34/development/usr/local/monetdb/bin/mserver5
logfile /Volumes/Samsung_T1/alt-dbfarm/merovingian.log
pidfile /Volumes/Samsung_T1/alt-dbfarm/merovingian.pid
sockdir /tmp
port 50000
exittimeout 60
forward proxy
discovery true
discoveryttl 600
control no
passphrase <unknown>
mapisock /tmp/.s.monetdb.50000
controlsock /tmp/.s.merovingian.50000
rs-btlcj34lt:testMapiSock lcj34$
Here is the command line error:
rs-btlcj34lt:alt-dbfarm lcj34$ mclient -u monetdb -d maizeFullGenomeDB
password:
monetdbd: internal error while starting mserver, please refer to the logs
And here is the error from the log file.
2016-01-14 10:33:26 MSG maizeFullGenomeDB[749]: # Visit http://www.monetdb.org/ for further information
2016-01-14 10:33:26 MSG maizeFullGenomeDB[749]: !IOException:mal_mapi.listen:operation failed: binding to UNIX socket file /Volumes/Samsung_T1/alt-dbfarm/maizeFullGenomeDB/.mapi.sock failed: No such file or directory
If I switch back to a dbfarm local to the MAC, it works fine.
Any ideas why I can¹t connect to a dbfarm on the external drive? Is there something else that needs to be setup for the socket creation to work?
Thanks - Lynn
users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
-- Sjoerd Mullender