Can not connect to Mongo Shell

[yosaba]

Hi,

I am trying out dbKoda -- the description looks fabulous. I'm running on an up-to-date Debian system and have configured a basic profile with defaults:

mongodb://localhost:27017/myDb

The test button on the configuration page reports "Connection success!" but when I use the Connect button there or, use "Open a connection" on the Editor page, I get the following message:

Error: Error: Failed to create Mongo shell, which exited with code 1 and output message at MongoShell. (/tmp/.mount_dbkodagXpuv1/app/resources/app.asar/assets/controller/lib/controllers/mongo-connection/index.js:615:27) at emitOne (events.js:115:13) at MongoShell.emit (events.js:210:7) at PipeSocket.MongoShell._this._onShellExit (/tmp/.mount_dbkodagXpuv1/app/resources/app.asar/assets/controller/lib/controllers/mongo-shell/index.js:155:15) at emitTwo (events.js:125:13) at PipeSocket.emit (events.js:213:7) at UnixTerminal.Terminal.emit (/tmp/.mount_dbkodagXpuv1/app/resources/app.asar/assets/controller/node_modules/node-pty/lib/terminal.js:79:34) at PipeSocket. (/tmp/.mount_dbkodagXpuv1/app/resources/app.asar/assets/controller/node_modules/node-pty/lib/unixTerminal.js:70:27) at Object.onceWrapper (events.js:316:30) at emitOne (events.js:120:20) at PipeSocket.emit (events.js:210:7) at Pipe._handle.close [as _onclose] (net.js:5...

The mongosh executable in on my path (putting it in /usr/bin does not change anything).

I am just running standalone on my laptop, not in Docker (as was the person in this post
#64
who reported the same error). I'd appreciate any insights.

Thanks,

P.S. The Support button on your home page gets a 404 response and the support@dbkoda.com email bounces with a long message from Office 365

[gharriso]

Hi Yosaba,

Thanks for trying dbKoda. You say the mongosh shell is in your path, but what we use is the classic mongo shell. So from a command prompt, does this work?

mongo mongodb://localhost:27017/myDb

Thanks,
Guy

[yosaba]

Hi Guy,

Thanks for your quick reply! I responded to the email immediately but apparently have to come back to the forum here as I never got a response.

You are correct, "mongo" was not in my path. Some of the documentation claims it is installed with the server but it was not in my case. I haven't installed or used Mongo for a couple years so I did what appeared to be the obvious thing and downloaded what they called the Mongo shell which was not the classic version.

So I downloaded a "Shell (tgz)" package from
https://www.mongodb.com/try/download/community?tck=docs_server
which has a "mongo" executable. Now I can get into a shell using
mongo mongodb://localhost:27017/m
from the command line as you asked. However, when trying to connect through dbKoba, I still get what looks like the same error message:

Error: Error: Failed to create Mongo shell, which exited with code 1 and output message at MongoShell.(/tmp/.mount_dbkodaWTul1k/app/resources/app.asar/assets/controller/lib/controllers/mongo-connection/index.js:615:27) at emitOne (events.js:115:13) at MongoShell.emit (events.js:210:7) at PipeSocket.MongoShell._this._onShellExit (/tmp/.mount_dbkodaWTul1k/app/resources/app.asar/assets/controller/lib/controllers/mongo-shell/index.js:155:15) at emitTwo (events.js:125:13) at PipeSocket.emit (events.js:213:7) at UnixTerminal.Terminal.emit (/tmp/.mount_dbkodaWTul1k/app/resources/app.asar/assets/controller/node_modules/node-pty/lib/terminal.js:79:34) at PipeSocket.(/tmp/.mount_dbkodaWTul1k/app/resources/app.asar/assets/controller/node_modules/node-pty/lib/unixTerminal.js:70:27) at Object.onceWrapper (events.js:316:30) at emitOne (events.js:120:20) at PipeSocket.emit (events.js:210:7) at Pipe._handle.close [as _onclose] (net.js:5...

Do I need to configure something beyond having "mongo" in my path?

Thanks

[MEGAMES]

same error in May 2022.
Is this product still supported?
I purchased the MongoDB performance and tuning book and wanted to use dbKoda along with it....

[benmathews]

The classic mongo shell is deprecated in Mongo v5.0 and removed in v6.0. Because of dependencies that the classic shell is compiled against one can't run the classic shell in a recent version of Ubuntu. Dbkoda needs to support mongosh or it is a dead product.

[michaeljharrison]

Hi there,

Unfortunately official support for DBKoda has ceased and it's now a deprecated application.

If you wish to continue using it you'll have to fork the repo and add support yourself.

Sorry!

[benmathews]

If so, a prominent statement should be put at the top of the read me stating that

• the project is not supported
• the maximum version of mongo that it is expected to work against.

[gharriso]

Hi Rick, Although this project is not under active maintenance, I think it is still functional for modern distributions of MongoDB. However, it requires the mongo shell, not the mongosh shell to be present in the path. In Debian, the mongo client program is provided by the mongodb-clients package. Thanks, Guy Guy Harrison CTO, ProvenDB ***@***.*** http://provendb.com <https://www.facebook.com/provendb> <https://www.linkedin.com/in/guy-harrison> <https://twitter.com/provendb> <https://medium.com/provendb> <https://github.com/Southbanksoftware> <https://wa.me/+61418533988> On 28 January 2021 at 3:57:12 am, yosaba ***@***.***) wrote: Hi, I am trying out dbKoda -- the description looks fabulous. I'm running on an up-to-date Debian system and have configured a basic profile with defaults: mongodb://localhost:27017/myDb The test button on the configuration page reports "Connection success!" but when I use the Connect button there or, use "Open a connection" on the Editor page, I get the following message: Error: Error: Failed to create Mongo shell, which exited with code 1 and output message at MongoShell. (/tmp/.mount_dbkodagXpuv1/app/resources/app.asar/assets/controller/lib/controllers/mongo-connection/index.js:615:27) at emitOne (events.js:115:13) at MongoShell.emit (events.js:210:7) at PipeSocket.MongoShell._this._onShellExit (/tmp/.mount_dbkodagXpuv1/app/resources/app.asar/assets/controller/lib/controllers/mongo-shell/index.js:155:15) at emitTwo (events.js:125:13) at PipeSocket.emit (events.js:213:7) at UnixTerminal.Terminal.emit (/tmp/.mount_dbkodagXpuv1/app/resources/app.asar/assets/controller/node_modules/node-pty/lib/terminal.js:79:34) at PipeSocket. (/tmp/.mount_dbkodagXpuv1/app/resources/app.asar/assets/controller/node_modules/node-pty/lib/unixTerminal.js:70:27) at Object.onceWrapper (events.js:316:30) at emitOne (events.js:120:20) at PipeSocket.emit (events.js:210:7) at Pipe._handle.close [as _onclose] (net.js:5... The mongosh executable in on my path (putting it in /usr/bin does not change anything). I am just running standalone on my laptop, not in Docker (as was the person in this post #64 <#64> who reported the same error). I'd appreciate any insights. Thanks, Rick P.S. The Support button on your home page gets a 404 response and the ***@***.*** email bounces with a long message from Office 365 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#76>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACZ3QNQRSVV2YPYWCLG6J3S4BAWPANCNFSM4WVS6NKQ> .

[benmathews]

I am not aware of any way to install mongo in a recent version of Ubuntu.

❯ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy
➜ sudo apt install mongodb-clients
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package mongodb-clients is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'mongodb-clients' has no installation candidate

[southbanksoftwaredeveloper]

Hi, Sorry for the delay in replying. Amazingly, it looks like MongoDB do not support Ubuntu 22.04 yet, though it would seem that support is due any time now: https://jira.mongodb.org/browse/SERVER-62300 Unfortunately, they will only support the version 6.0 release that release doesn’t seem to include the older mongo shell. dbKoda could be reworked to support the mongosh shell, but it’s not likely any time soon, the work is significant and although the project is open sourced, there are no active developers at the moment. The only solution then would be to run the mongo shell in a docker container. In the paths section of dbKoda you can specify the location of docker binaries and the image you want to use: Regards, Guy On 3 October 2022 at 11:39:17 pm, Ben Mathews ***@***.***) wrote: I am not aware of any way to install mongo in a recent version of Ubuntu. ❯ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy ➜ sudo apt install mongodb-clients Reading package lists... Done Building dependency tree... Done Reading state information... Done Package mongodb-clients is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'mongodb-clients' has no installation candidate — Reply to this email directly, view it on GitHub <#76 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFU4UAAVIB7PQEVNRM6YBGDWBLHXLANCNFSM4WVS6NKQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[gharriso]

Hi, dbKoda is open source, but not under current commercial development. However, we use it regularly so it should work. Do you have a “mongo” executable in your path? Thanks Guy —————————————————————————————————————————————————————————————————————— Guy Harrison | guyharrison.net | @GuyHarrison <http://twitter.com/guyharrison> ***@***.*** | +61 418 533 988 | https://www.linkedin.com/in/guy-harrison/ On 22 May 2022 at 8:25:08 pm, MEGAMES ***@***.***) wrote: same error in May 2022. Is this product still supported? I purchased the MongoDB performance and tuning book and wanted to use dbKoda along with it.... — Reply to this email directly, view it on GitHub <#76 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACZ3QN2TUVDNC7ZEKWNKGTVLIDQHANCNFSM4WVS6NKQ> . You are receiving this because you commented.Message ID: ***@***.***>