Connection problem -- solved, bu the product could be improved

Jeff Breadner shared this question 7 months ago
Answered

Hi guys


I'm running dbKoda 0.81 app image on Linux Mint 18.1 64-bin, with /usr/bin/mongo version 2.6.10. My server is on a different host, 10.0.0.3, running Ubuntu 16.04.3, mongo 3.2.17. I can run 'mongo' from the command line and query this host without issues.

When I create a connection in dbKoda (host: 10.0.0.3, port 27017, database: mydatabase, no SSH tunnel / SSL / Authentication) the Test button shows success, but I cannot establish a connection. The error below comes up on the console.

As I was writing this, I think I discovered the problem; even though I could connect myself, this major version difference between my client and server wound up causing the problem. Once I upgraded both sides to 3.6, the connection was successful.

However, I'm posting this anyway to make the devs aware of this possible failure, and for people having the same problem as me to find some resolution. Devs: Perhaps do a --version kind of query on both sides, and throw a warning if the versions are not compatible?

thanks

Jeff


Mongo Version Cmd: mongoCmd=/usr/bin/mongo, mongoVersionCmd="/usr/bin/mongo" --version, mongodumpCmd=/usr/bin/mongodump, mongorestoreCmd=/usr/bin/mongorestore, mongoimportCmd=/usr/bin/mongoimport, mongoexportCmd=/usr/bin/mongoexport, dril

lCmd=, showWelcomePageAtStart=true, telemetryEnabled=true

2017-12-23T08:13:17-07:00 - info: Mongo Cmd: mongoCmd=/usr/bin/mongo, mongoVersionCmd="/usr/bin/mongo" --version, mongodumpCmd=/usr/bin/mongodump, mongorestoreCmd=/usr/bin/mongorestore, mongoimportCmd=/usr/bin/mongoimport, mongoexportCmd=/usr/bin/mongoexport, drillCmd=, s

howWelcomePageAtStart=true, telemetryEnabled=true

2017-12-23T08:13:17-07:00 - info: load pre defined scripts /tmp/.mount_zObrSw/usr/bin/resources/app.asar.unpacked/node_modules/@southbanksoftware/dbkoda-controller/lib/all-in-one.js

2017-12-23T08:13:17-07:00 - info: mongo shell exit 1 false

, id=446d2e30-e7f1-11e7-8f0b-6f025fe982aa, shellId=446d2e31-e7f1-11e7-8f0b-6f025fe982aa, output=exception: connect failed700 Error: assertion src/mongo/client/dbclientinterface.h:231 at src/mongo/shell/mongo.js:148x4fa7f1]x208) [0x5013b8]

., responseCode=FAILED_LAUNCH_MONGO_SHELLrtion src/mongo/client/dbclientinterface.h:231 at src/mongo/shell/mongo.js:148x4fa7f1]x208) [0x5013b8]

. <br/>ion: connect failed700 Error: assertion src/mongo/client/dbclientinterface.h:231 at src/mongo/shell/mongo.js:148x4fa7f1]x208) [0x5013b8]

at GeneralError (/tmp/.mount_zObrSw/usr/bin/resources/app.asar/node_modules/@southbanksoftware/dbkoda-controller/node_modules/feathers-errors/lib/index.js:177:17)

at /tmp/.mount_zObrSw/usr/bin/resources/app.asar/node_modules/@southbanksoftware/dbkoda-controller/lib/controllers/mongo-connection/index.js:205:19

at <anonymous>

Comments (1)

photo
1

This issue has been fixed in our latest release ( dbKoda v0.9 ), thanks for the support and notifying us to this problem.


Kind Regards,

Michael from dbKoda.