Info
I'm using mongodb 2.6.1 on Windows 64bit.
I use the mongodb native node driver.
The connection works, however, with some of the queries, I get the following exception:
—
C:\wamp\www\poker-tell\server\node_modules\mongodb\lib\mongodb\connection\base.js:245
throw message;
^
Error: failed to connect to [127.0.0.1:27017]
at null. (C:\wamp\www\poker-tell\server\node_modules\mongodb\lib\mongodb\connecti
on\server.js:536:74)
at EventEmitter.emit (events.js:106:17)
at null. (C:\wamp\www\poker-tell\server\node_modules\mongodb\lib\mongodb\connecti
on\connection_pool.js:150:15)
at EventEmitter.emit (events.js:98:17)
at Socket. (C:\wamp\www\poker-tell\server\node_modules\mongodb\lib\mongodb\connec
tion\connection.js:516:10)
at Socket.EventEmitter.emit (events.js:95:17)
at onwriteError (_stream_writable.js:233:10)
at onwrite (_stream_writable.js:251:5)
at WritableState.onwrite (_stream_writable.js:97:5)
at fireErrorCallbacks (net.js:438:13)
npm ERR! weird error 8
npm ERR! not ok code 0
—
When I look into the mongod.exe output, I have the following:
—
2014-05-09T21:29:07.315+0200 [conn10] AssertionException handling request, closing client connec
tion: 17133 SSL handshake requested, SSL feature not available in this build
—
I'm not initializing a ssl connection in node.
Top User Comments
edi9999 commented on Fri, 9 May 2014 21:53:41 +0000:
Somehow I found out that the problem was something completely unrelated to SSL. I used a syntax for selections that apparently did work before but now doesn't, eg I wrote:
selection=
{'name',id'}
but you should write:
selection=
{'name':true,id':true}
Steps to Reproduce
Install mongodb on windows 64bit (with the installer from the website from 5/9/2014).
Use the latest mongodb driver for node.
Write a query inside the nodejs that uses selection, condition, sort and limit, and call toArray.
