Digital Ocean Server Reset, NodeJS Not Working!

  • Posted on February 15, 2014
  • kermankAsked by kermank

Hi there, So recently my DO droplet was reset due to some creation problem in the NYC1 area. My droplet was running (an analytics software) and now it gives me this error:

Express 500 Error: failed to connect to [localhost:27017] at null. (/root/countly/frontend/express/node_modules/mongoskin/node_modules/mongodb/lib/mongodb/connection/server.js:569:74) at EventEmitter.emit (events.js:106:17) at null. (/root/countly/frontend/express/node_modules/mongoskin/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:139:15) at EventEmitter.emit (events.js:98:17) at Socket. (/root/countly/frontend/express/node_modules/mongoskin/node_modules/mongodb/lib/mongodb/connection/connection.js:475:10) at Socket.EventEmitter.emit (events.js:95:17) at net.js:441:14 at process._tickCallback (node.js:415:13)

How can I fix this? Any help is appreciated!

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Looks like your mongodb is down. Probably mongodb had an unclean shutdown so you will need to start mongod with the repair option. Check this link for details: