Replies: 1 comment
-
In some cases, this is some sort of issue with MongoDB. Could you check the instructions here for how to get the MongoDB logs? If MongoDB is corrupt, then there is not much that can be done but we will have to see from the logs on what issues there may be. Did you try to upgrade to a newer version and then roll back to an older version by chance? That's probably the 2nd most common issue I've seen when the The "How You're Launching the Container" part is important but if you do not have the equivalent run command or docker compose, please check out item 2 in the above support info page to capture that information. When it comes to data inconsistency, that tends to be when the database doesn't get shut down cleanly. I would mostly be wanting to check to see if you have the wait configured to let the container shut down cleanly when portainer lifecycles the container. |
Beta Was this translation helpful? Give feedback.
-
Controller Version
v5.13
Describe Your Issue or Question
Hi
I have Omada in Portainer on a Ubuntu Server. It works for 6 month very well.
Yesterday it stoped working and i cant start the container anymore.
Here is the log:
Expected Behavior
i would like to recive help
Steps to Reproduce
Start the container
How You're Launching the Container
Container Logs
MongoDB Logs
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions