From deb0fd7e2bf3b524da50287d0ce5e9f766393fa3 Mon Sep 17 00:00:00 2001 From: Lauri Ojansivu Date: Wed, 26 Jan 2022 02:21:46 +0200 Subject: [PATCH] Updated Repair MongoDB (markdown) --- Repair-MongoDB.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Repair-MongoDB.md b/Repair-MongoDB.md index 5e2a0ea..93c1968 100644 --- a/Repair-MongoDB.md +++ b/Repair-MongoDB.md @@ -1,4 +1,8 @@ -Some customer of [WeKan Commercial Support](https://wekan.team/commercial-support/) ordered restore and repair of WeKan MongoDB database at UCS appliance. Docker containers were all the time crashing and restarting. Here are commands that were used while repairing. +Some customer of [WeKan Commercial Support](https://wekan.team/commercial-support/) ordered restore and repair of WeKan MongoDB database at UCS appliance. This was needed when changing back to previous UCS 4.x major version, when in new major UCS 5.x version Docker containers were all the time crashing and restarting, or something else got broken. Here are commands that were used while repairing. + +Similarly, MongoDB may require repair, if: +- MongoDB does not recover from sudden power failure cleanly +- Disk comes full, that is worst case. Recommended are daily backups, in this case sometimes repair does not work well enough. 1. SSH to UCS appliance as root: ```