-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node 7.7.2 MongoDB error #2759
Labels
Comments
We will push an update today to avoid this with pm2, still opened an issue over the responsible module : othiym23/async-listener#99 |
@vmarchaud @dnohr actually, it's bug on Node 7.7.2 and will be fixed by nodejs/node#11762 |
@vhain Sounds good, thanks for the details. |
The same problem! |
We released pmx |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure if it's PM2 or a MongoDB driver bug. After upgrading to Node 7.7.2, my applications connected to MongoDB failed with following error. I have full connection from my server to the database.
NODE: 7.7.2
PM2: 2.4.2
MongoDB: 2.2.24
Stack trace:
TypeError: "listener" argument must be a function
at Socket.once (events.js:307:11)
at Socket.connect (net.js:943:10)
at Socket.connect (/usr/lib/node_modules/pm2/node_modules/async-listener/index.js:76:27)
at Object.exports.connect.exports.createConnection (net.js:76:35)
at Connection.connect (/var/nodes/site.com/node_modules/mongodb-core/lib/connection/connection.js:397:11)
at Pool.connect (/var/nodes/site.com/node_modules/mongodb-core/lib/connection/pool.js:638:16)
at Server.connect (/var/nodes/site.com/node_modules/mongodb-core/lib/topologies/server.js:383:17)
at Server.connect (/var/nodes/site.com/node_modules/mongodb/lib/server.js:361:17)
at open (/var/nodes/site.com/node_modules/mongodb/lib/db.js:226:19)
at Db.open (/var/nodes/site.com/node_modules/mongodb/lib/db.js:249:44)
Solution:
After downgrading to Node 7.7.1, my applications through PM2 was able to connect to the DB again.
Just a heads up before upgrading your environment to the latest node release.
Thanks.
The text was updated successfully, but these errors were encountered: