Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.
It looks like something is already running and listening on port 27017, most likely another instance of mongodb.
You can do a quick check:
netstat -plntu
Unfortunately the only other instance I could find of this online the problem was resolved by simply killing the existing mongodb instance:
killall -9 mongod
And then after re-trying mongodb started up correctly and the problem did not recur.
If this fixes it but the issue recurs it looks like you will need to do more digging to see what else is starting mongodb elsewhere. Ultimately you have a port conflict, where there is already a mongo instance running and listening on the same port that you are trying to start the new version on.