With the latest default branch (changeset ef9492865066) on Fedora 16 (optimized build):
$ cat ~/.monetdb
user=monetdb
password=monetdb
$ stethoscope
MAPI = monetdb@(null):50000
ACTION= mapi_reconnect
ERROR = !getaddrinfo failed: Name or service not known
-- connection with server mapi:monetdb://(null):50000/(null) closed
What do I need to do to get stethoscope to connect to mserver5 successfully?
Shell 1:
$ mserver5 --dbname=MyDB
MonetDB 5 server v11.9.0
This is an unreleased version
Serving database 'MyDB', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.629 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
Shell 2:
$ cat ~/.monetdb
user=monetdb
password=monetdb
$ stethoscope
MAPI = monetdb@(null):50000
ACTION= mapi_reconnect
ERROR = !getaddrinfo failed: Name or service not known
-- connection with server mapi:monetdb://(null):50000/(null) closed
$ stethoscope -h rome.ins.cwi.nl
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/(null) closed
$ stethoscope -h rome.ins.cwi.nl -u monetdb
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/(null) closed
$ stethoscope -h rome.ins.cwi.nl -u monetdb -P monetdb
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/(null) closed
$ stethoscope -h rome.ins.cwi.nl -u monetdb -P monetdb -d MyDB
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/MyDB closed
$ stethoscope -h rome.ins.cwi.nl -u monetdb -P monetdb -d MyDB -p 50000
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/MyDB closed
hm, it appears I have to start mserver5 with --set mapi_open=true, and provide stethoscope with both host name and database name --- mclient requires none of these ...
Shell 1:
$ mserver5 --dbname=MyDB --set mapi_open=true
MonetDB 5 server v11.9.0
This is an unreleased version
Serving database 'MyDB', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.629 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://rome.ins.cwi.nl:50000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
Shell 2:
$ stethoscope
MAPI = monetdb@(null):50000
ACTION= mapi_reconnect
ERROR = !getaddrinfo failed: Name or service not known
-- connection with server mapi:monetdb://(null):50000/(null) closed
$ stethoscope -h rome
MAPI = monetdb@rome:50000
ACTION= mapi_start_talking
ERROR = !request for database '(null)', but this is database 'MyDB', did you mean to connect to monetdbd instead?
-- connection with server mapi:monetdb://rome:50000/(null) closed
$ stethoscope -d MyDB
MAPI = monetdb@(null):50000
ACTION= mapi_reconnect
ERROR = !getaddrinfo failed: Name or service not known
-- connection with server mapi:monetdb://(null):50000/MyDB closed
$ stethoscope -h rome -d MyDB
-- connection with server mapi:monetdb://rome:50000/MyDB
-- profiler.activate("event");
-- profiler.activate("time");
-- profiler.activate("ticks");
-- profiler.activate("stmt");
-- profiler.activate("thread");
-- profiler.activate("start");
-- opened UDP profile stream rome.ins.cwi.nl:50010 for rome
-- profiler.setAll();
-- profiler.start();
stethoscope and mclient should/could share the same bit of connection "searching" magic to make it behave as expected when being spoiled with the (IMO luxurous) mclient behaviour
Alternatively, we could document prominently and clearly (via man stethoscope and stethoscope --help and the error messages`) that stethoscope requires
(1) -d
(2) -h
(3) mserver5 allowing "remote" connection (--set mapi_open-true)
Alternatively, we could document prominently and clearly (via man stethoscope
and stethoscope --help and the error messages`) that stethoscope requires
(1) -d
(2) -h
(3) mserver5 allowing "remote" connection (--set mapi_open-true)
would be happy with that for the time being (perhaps fix tomograph at the same time)
Since changesets 46250:26622b43db44 - 46262:5a1b55f4e88a (on Feb2013 branch), stethoscope (& tomograph) behave just like client to find the server (& database) to connect to. This solved this bug. Thanks go to Fabian!
Date: 2012-02-20 20:38:08 +0100
From: @drstmane
To: clients devs <>
Version: 11.15.1 (Feb2013)
CC: duc, mrunal.gawade, y.kargin
Last updated: 2013-02-19 13:17:58 +0100
Comment 16957
Date: 2012-02-20 20:38:08 +0100
From: @drstmane
With the latest default branch (changeset ef9492865066) on Fedora 16 (optimized build):
$ cat ~/.monetdb
user=monetdb
password=monetdb
$ stethoscope
MAPI = monetdb@(null):50000
ACTION= mapi_reconnect
ERROR = !getaddrinfo failed: Name or service not known
-- connection with server mapi:monetdb://(null):50000/(null) closed
Comment 17167
Date: 2012-04-26 23:21:30 +0200
From: @drstmane
This problem is also present in Apr2012.
What do I need to do to get stethoscope to connect to mserver5 successfully?
Shell 1:
$ mserver5 --dbname=MyDB
MonetDB 5 server v11.9.0
This is an unreleased version
Serving database 'MyDB', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.629 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
Shell 2:
$ cat ~/.monetdb
user=monetdb
password=monetdb
$ stethoscope
MAPI = monetdb@(null):50000
ACTION= mapi_reconnect
ERROR = !getaddrinfo failed: Name or service not known
-- connection with server mapi:monetdb://(null):50000/(null) closed
$ stethoscope -h rome.ins.cwi.nl
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/(null) closed
$ stethoscope -h rome.ins.cwi.nl -u monetdb
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/(null) closed
$ stethoscope -h rome.ins.cwi.nl -u monetdb -P monetdb
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/(null) closed
$ stethoscope -h rome.ins.cwi.nl -u monetdb -P monetdb -d MyDB
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/MyDB closed
$ stethoscope -h rome.ins.cwi.nl -u monetdb -P monetdb -d MyDB -p 50000
MAPI = monetdb@rome.ins.cwi.nl:50000
ACTION= mapi_reconnect
ERROR = !could not connect to rome.ins.cwi.nl:50000: Connection refused
-- connection with server mapi:monetdb://rome.ins.cwi.nl:50000/MyDB closed
Comment 17168
Date: 2012-04-26 23:32:30 +0200
From: @drstmane
hm, it appears I have to start mserver5 with --set mapi_open=true, and provide stethoscope with both host name and database name --- mclient requires none of these ...
Shell 1:
$ mserver5 --dbname=MyDB --set mapi_open=true
MonetDB 5 server v11.9.0
This is an unreleased version
Serving database 'MyDB', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.629 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2012 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://rome.ins.cwi.nl:50000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
Shell 2:
$ stethoscope
MAPI = monetdb@(null):50000
ACTION= mapi_reconnect
ERROR = !getaddrinfo failed: Name or service not known
-- connection with server mapi:monetdb://(null):50000/(null) closed
$ stethoscope -h rome
MAPI = monetdb@rome:50000
ACTION= mapi_start_talking
ERROR = !request for database '(null)', but this is database 'MyDB', did you mean to connect to monetdbd instead?
-- connection with server mapi:monetdb://rome:50000/(null) closed
$ stethoscope -d MyDB
MAPI = monetdb@(null):50000
ACTION= mapi_reconnect
ERROR = !getaddrinfo failed: Name or service not known
-- connection with server mapi:monetdb://(null):50000/MyDB closed
$ stethoscope -h rome -d MyDB
-- connection with server mapi:monetdb://rome:50000/MyDB
-- profiler.activate("event");
-- profiler.activate("time");
-- profiler.activate("ticks");
-- profiler.activate("stmt");
-- profiler.activate("thread");
-- profiler.activate("start");
-- opened UDP profile stream rome.ins.cwi.nl:50010 for rome
-- profiler.setAll();
-- profiler.start();
Comment 17177
Date: 2012-04-27 08:31:47 +0200
From: @grobian
stethoscope and mclient should/could share the same bit of connection "searching" magic to make it behave as expected when being spoiled with the (IMO luxurous) mclient behaviour
Comment 17178
Date: 2012-04-27 08:41:09 +0200
From: @drstmane
Alternatively, we could document prominently and clearly (via
man stethoscopeandstethoscope --helpand the error messages`) that stethoscope requires(1) -d
(2) -h
(3) mserver5 allowing "remote" connection (--set mapi_open-true)
Comment 17658
Date: 2012-08-24 14:50:26 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
Comment 17903
Date: 2012-11-07 19:28:53 +0100
From: @grobian
(In reply to comment 4)
would be happy with that for the time being (perhaps fix tomograph at the same time)
Comment 18465
Date: 2013-02-11 23:20:17 +0100
From: @drstmane
Since changesets 46250:26622b43db44 - 46262:5a1b55f4e88a (on Feb2013 branch), stethoscope (& tomograph) behave just like client to find the server (& database) to connect to. This solved this bug. Thanks go to Fabian!
Closing.
Comment 18511
Date: 2013-02-19 13:17:58 +0100
From: @sjoerdmullender
Feb2013 has been released.
The text was updated successfully, but these errors were encountered: