[Bug]: MongoDB will not start [5.15-chromium] #539
Assignees
Comments
|
Added some Mongo logs |
|
I have the same issue and I did |
|
Are you certain that there isn't another container running, accessing the same volume where the persistent data is? The logs from MongoDB seem to indicate there is another MongoDB process possibly: |
|
These are the MongoDB logs I get when I try to run a 2nd controller using the same persistent data: |
|
@mbentley There was no second service using Mongo and I found that odd, a restart did fix it my issue it seems. This server has not been restarted in a long time and the container was on 5.14 for quite some time too. |
|
After upgrading from 5.14.32.2 (where it started) I still get this error: ... but nothing more. It stops here. Mongodb logs seem normal. |
|
@watchingdogs - remove |
|
@mbentley my issue has now serviced again randomly. I have moved to 5.15 NONE chromium version, the container is just active and is running 24/7 and just stops working, I cannot start it unless I restart the service, there is only one version of omada running and has been that way for years. |
|
Running |
|
Service started. |
|
Odd. It seems like something is holding or locking the files. I'm wondering if the MongoDB is terminating suddenly for some reason. Could you share the entire MongoDB log? If you don't know how to get them, see: https://github.com/mbentley/docker-omada-controller/blob/master/SUPPORT_INFO.md |
It is working fine after a reboot, I am not sure if anything in there will help but if it does not and it fails again I will make sure to run that command. |
|
Thanks for the MongoDB log. It looks like it might have already been looping at the start of he log but I can see it exits with a few error codes: 100The odd thing is that is goes to clean up 48So I'm guessing that this is where it's failing to start because the socket file still exists at You'll want to update the name of the container to match whatever yours is though so keep that in mind. |
|
Thanks, I will try that once it fails again. |
|
I can start the container if I remove the environment variable: WORKAROUND_509=true Maybe this helps |
Removing this solved the issue, and now everything is working for me as well with the newest version. Thank you so much. |
|
I added a version check so |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Controller Version
5.15-chromium
Describe the Bug
Updated to latest and tried to go back to 5.14-chromium and getting the same issue now.
I tried with the workaround 509 true or false and same issue.
Expected Behavior
Container starts
Profit!
Steps to Reproduce
How You're Launching the Container
Container Logs
MongoDB Logs
Additional Context
No response
The text was updated successfully, but these errors were encountered: