Mongo client keeps waiting, like it cannot connect
Opened this issue · 1 comments
bitliner commented
I have an instance of tokumx up, iside a docker container.
When I try to connect with mongo
client, using mongo --verbose...
, the result is
MongoDB shell version: 2.4.9
Thu Apr 9 12:39:15.607 versionArrayTest passed
connecting to: 127.0.0.1:27018/test
Thu Apr 9 12:39:15.630 creating new connection to:127.0.0.1:27018
Thu Apr 9 12:39:15.630 BackgroundJob starting: ConnectBG
Thu Apr 9 12:39:15.630 connected connection!
and then it keeps waiting without showing the prompt.
It can connect though to other tokumx remote instances (that are from the same docker image)
bitliner commented
After reboot of the computer, now it throws the following error message
MongoDB shell version: 2.4.9
Thu Apr 9 15:27:17.514 versionArrayTest passed
connecting to: 127.0.0.1:27018/test
Thu Apr 9 15:27:17.536 creating new connection to:127.0.0.1:27018
Thu Apr 9 15:27:17.536 BackgroundJob starting: ConnectBG
Thu Apr 9 15:27:17.536 connected connection!
Thu Apr 9 15:27:17.536 Socket recv() errno:104 Connection reset by peer 127.0.0.1:27018
Thu Apr 9 15:27:17.536 SocketException: remote: 127.0.0.1:27018 error: 9001 socket exception [RECV_ERROR] server [127.0.0.1:27018]
Thu Apr 9 15:27:17.536 DBClientCursor::init call() failed
Thu Apr 9 15:27:17.536 User Assertion: 10276:DBClientBase::findN: transport error: 127.0.0.1:27018 ns: admin.$cmd query: { whatsmyuri: 1 }
Thu Apr 9 15:27:17.537 Error: DBClientBase::findN: transport error: 127.0.0.1:27018 ns: admin.$cmd query: { whatsmyuri: 1 } at src/mongo/shell/mongo.js:147
Thu Apr 9 15:27:17.537 User Assertion: 12513:connect failed
Thu Apr 9 15:27:17.537 freeing 1 uncollected N5mongo20DBClientWithCommandsE objects
exception: connect failed
PS: I am using mongo
version 2.4.9 and tokumx version 2.0.0