-
Controller Versionunknown, as the controller doesnt start, but latest version Describe Your Issue or QuestionMongoDB refuses to start. I used an empty data and log folder, so it's basically a brand new, blank installation. Expected BehaviorMongoDB has to start normally Steps to Reproduce
How You're Launching the Container
Container Logs
MongoDB Logs
Additional Context[core@docker-main logs]$ docker exec -ti omada-controller /bin/sh netstat -a -nActive Internet connections (servers and established) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
So first let's look at the failure of it to start. I took your compose file, updated the persistent data paths for my system, set permissions to 1000:1000 for Let's try to stop the controller and just run MongoDB by itself with a lot of verbose logging and see if there is anything helpful as to why MongoDB is dying:
And then as a secondary issue, there are some ports that are actually supposed to be UDP which isn't going to prevent MongoDB from starting but will prevent the controller from functioning as expected. The below is just taken from the docker run command in the readme:
Specifically, |
Beta Was this translation helpful? Give feedback.
-
I may have found the problem. I noticed that the initial database requested is over 7 Gb, but I don't have that much space left on my device.
It's a test partition, RAID1, with an EXT4 partition of 10Gb (of which 2.3 Gb was already taken). I tried it on a different partition, and there MongoDB is starting (although the actual disk space usage there is only 300Mb, so I'm a bit puzzled still). And thank you for the hint about the ports. The example docker-compose file used network_mode host. I wanted to use specific ports to I just copied what I thought I saw in the environment variables, but hadn't paid too much attention to it :-) |
Beta Was this translation helpful? Give feedback.
Okay, I swapped out my old WD Green disks (which were there for testing only), and used my new WD Gold disks, and now it works flawlessly.
So I guess it was all a side effect of slow WD Green disks.