nodebb MongoError: topology was destroyed

Technical Support
  • #1

    Please help me for below error.

    translateKey (/opt/NodeBB-0.9.0/public/src/modules/translator.js:175:14)
    11/12 02:20 [23370] - error: /forum/auth/facebook
    MongoError: topology was destroyed
    at Server.update (/opt/NodeBB-0.9.0/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:979:49)
    at Server.update (/opt/NodeBB-0.9.0/node_modules/mongodb/lib/server.js:331:17)
    at updateDocuments (/opt/NodeBB-0.9.0/node_modules/mongodb/lib/collection.js:980:19)
    at Collection.update (/opt/NodeBB-0.9.0/node_modules/mongodb/lib/collection.js:1018:44)
    at /opt/NodeBB-0.9.0/node_modules/connect-mongo/lib/connect-mongo.js:360:18
    at MongoStore.getCollection (/opt/NodeBB-0.9.0/node_modules/connect-mongo/lib/connect-mongo.js:216:11)
    at MongoStore.set (/opt/NodeBB-0.9.0/node_modules/connect-mongo/lib/connect-mongo.js:358:10)
    at Session.save (/opt/NodeBB-0.9.0/node_modules/express-session/session/session.js:71:25)
    at Session.save (/opt/NodeBB-0.9.0/node_modules/express-session/index.js:331:15)
    at ServerResponse.end (/opt/NodeBB-0.9.0/node_modules/express-session/index.js:289:21)
    Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (http.js:690:11)
    at ServerResponse.header (/opt/NodeBB-0.9.0/node_modules/express/lib/response.js:718:10)
    at ServerResponse.contentType (/opt/NodeBB-0.9.0/node_modules/express/lib/response.js:551:15)
    at ServerResponse.send (/opt/NodeBB-0.9.0/node_modules/express/lib/response.js:138:14)
    at defaultFn (/opt/NodeBB-0.9.0/src/middleware/render.js:19:11)
    at /opt/NodeBB-0.9.0/src/middleware/render.js:73:8
    at /opt/NodeBB-0.9.0/public/src/modules/translator.js:156:6
    at /opt/NodeBB-0.9.0/public/src/modules/translator.js:177:4
    at Object.translator.load (/opt/NodeBB-0.9.0/public/src/modules/translator.js:206:5)

  • GNU/Linux
    #2

    having exact same error, the problem is server just becomes unresponsive. process does not exit so forever does not restart it. just hangs there. scratching my head for past few days what does the error means? Please help

    MongoError: topology was destroyed
    at Server.update (/home/latest-nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:966:49)
    at Server.update (/home/latest-nodebb/node_modules/mongodb/lib/server.js:331:17)
    at updateDocuments (/home/latest-nodebb/node_modules/mongodb/lib/collection.js:967:19)
    at Collection.update (/home/latest-nodebb/node_modules/mongodb/lib/collection.js:1005:44)
    at /home/latest-nodebb/node_modules/connect-mongo/lib/connect-mongo.js:360:18
    at MongoStore.getCollection (/home/latest-nodebb/node_modules/connect-mongo/lib/connect-mongo.js:216:11)
    at MongoStore.set (/home/latest-nodebb/node_modules/connect-mongo/lib/connect-mongo.js:358:10)
    at Session.save (/home/latest-nodebb/node_modules/express-session/session/session.js:71:25)
    at Session.save (/home/latest-nodebb/node_modules/express-session/index.js:331:15)
    at ServerResponse.end (/home/latest-nodebb/node_modules/express-session/index.js:289:21)
    Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (http.js:724:11)
    at ServerResponse.header (/home/latest-nodebb/node_modules/express/lib/response.js:718:10)
    at ServerResponse.send (/home/latest-nodebb/node_modules/express/lib/response.js:163:12)
    at defaultFn (/home/latest-nodebb/src/middleware/render.js:19:11)
    at /home/latest-nodebb/src/middleware/render.js:78:8
    at /home/latest-nodebb/public/src/modules/translator.js:156:6
    at /home/latest-nodebb/public/src/modules/translator.js:177:4
    at Object.translator.load (/home/latest-nodebb/public/src/modules/translator.js:206:5)
    at translateKey (/home/latest-nodebb/public/src/modules/translator.js:175:14)
    at /home/latest-nodebb/public/src/modules/translator.js:153:4

  • GNU/Linux
    #3

    @manan Odd... seems it just means the connection to Mongo was lost... have you tried force-killing Mongo and restarting it?

  • GNU/Linux
    #4

    @julian the issue was different mongodb versions on different servers, when the database migrated on the different version of mongodb it failed with that error periodically. The odd thing is it did not crash, just hung threre.


Suggested Topics


  • 0 Votes
    2 Posts
    191 Views

  • NodeBB AWS auto scaling

    Technical Support
    2 Votes
    14 Posts
    2181 Views

  • 0 Votes
    7 Posts
    1716 Views

  • 0 Votes
    3 Posts
    1425 Views

  • 0 Votes
    5 Posts
    2219 Views

| | | |