Closed ahohnsen closed 1 year ago
I've investigated that problem.
It seems that the problem that is linked in the article is not related to our problem. And it is not an article, by the way, it is a normal forum entry in the mongo community ;-) with an unfortunately misleading title. <- And this sentence reads meaner than intended. But I don't know how I could have put it differently in the language.
And it seems, that the problem in there is solved as well. They tried to install mongo community 6.0.1
what was recently updated to mongo-community 6.0.3
and everything seems to work now.
The root of our problem might be, that an instance of mongo is already running after the installation. Why? I don't know, there are a lot of possibilities here.
I would suggest, before downgrading the version and having two scripts, trying installing mongo version 6.0.3
again and try to fix the problem by:
I'm very happy to help and get mongo 6.0.3
up and running. Feel free to contact me.
Might be a shot, to work with the latest version of mongo, instead of installing the old one.
Thank you @mpagels. You found the real root cause of my problem.
We fixed this as Martin already described with the following steps:
Might be interesting for others how you did it. Because I did not remember the commands, you did. I was really impressed.
List the software via brew
brew list
delete mongo software via brew command
brew delete mongodb-community
brew delete mongodb-database-tools
brew delete mongodb-compass
And to stop the mongo server services:
brew services stop mongodb-community
I tried the MongoDB setup script on my Macbook (M1, macOS Ventura 13.1) and got the following error:
Afterwards I got the following error connecting to
mongodb://localhost:27017
via MongoDB Compass:@JessicaLoers found this article, which states that MongoDB 6.x does not longer run on macOS Ventura Version 13.1.
We fixed this issue by uninstalling
mongodb-community
and installingmongodb-community@5.0
instead. As our students might update to Ventura, I think it would be good to address this issue in the MongoDB setup script.