Not able to connect mongo database

carrie shared this problem 10 months ago
Solved

I tried to use No SQL Booster to connect to a mongodb server, but i kept getting the following error. However, if i try with other GUI, I am able to connect. I am not sure why?


I am using windows 10, no sql booster version 5.2.7


Thanks in advance

              "at Socket.err (C:\\Users\\kawang\\AppData\\Local\\Programs\\nosqlbooster4mongo\\resources\\app.asar\\node_modules\\mongodb-core\\lib\\connection\\connect.js:286:7)" +
              "at Object.onceWrapper (events.js:273:13)" +
              "at Socket.emit (events.js:182:13)" +
              "at emitErrorNT (internal/streams/destroy.js:82:8)" +
              "at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)" +
              "at process._tickCallback (internal/process/next_tick.js:63:19)",
	"name" : "MongoNetworkError",
	"errorLabels" : [
		"TransientTransactionError"
	]
}

Comments (3)

photo
1

From the information you provided, I don't know what the problem is.Please click the "Test connection" button and report the full error log


/fc0a263ece3fbd875e919c8dd52b63af

photo
1

just attached the log

photo
photo
1

cd2b760d90250ef4b48b2684af4ceda6Hi, Qinghai, i have attached the test connection log, thanks!

photo
1

Did you try the "uri" with Mongo shell? (mongodb://readWriter:*****@xxxxx:20844....)

photo
1

still got the same issue

photo
1

If mongo shell doesn't work either, the problem is probably not NoSQLBooster. You need to check your MongoDB URI, connect successfully in mongo shell first, and then import the URI to NoSQLBooster.

photo
1

oh sorry, i meant i tried connect through URL on NoSQLBooster, but didnt work. I didn't try with mongoShell, but i had Java code do the connection and that works, plus if i use other GUI I had no problem with connection either.

photo
1

Qinghai, I ran across this issue and it is NoSQL Booster, but it is because you are using your own modified version of the mongo nodejs driver. It is this issue that happens in Windows 10. https://jira.mongodb.org/browse/NODE-1747

I unpacked your ASAR file and implemented the fix in your qh-mongodb module, then repacked and it worked for me. I also had several other people at my company have the problem and it fixed it for them.

I would recommend merging your custom changes with the latest version of the mongodb node driver.

If you have any questions let me know. Thanks.

photo
1

Thanks a lot.

We have worked out a new test build to fix the NODE-1747 issue, please download and give it a try.

Windows: https://nosqlbooster.com/s3/download/releasesv5/nosqlbooster4mongo-5.2.9-beta.1.exe

BTW, the reason we didn't merge the latest version of the driver is that one of the features we rely heavily on has bug (NODE-2144) and hasn't been fixed yet. https://jira.mongodb.org/browse/NODE-2144

photo