Lack of mongo resilience after unplanned shutdown.

Using stable Docker and latest docker-compose, my laptop overheated and emergency shut down kicked in due to reasons unrelated to wekan. After cooling down and powering back on, the containers started without error messages, but with an unclean shutdown warning from mongo. The boards were usable, but login was not, I was getting “Login Forbidden”.

After some research (four hours divided in multiple days), I found the solution in Stack Overflow, apparently mongo doesn’t self-repair when starting unless it has journaling enabled. I do not know how to enable journaling in mongo, but a docker-compose down; docker-compose run wekandb mongod --repair; docker-compose up fixed my issues.

[ofekp]

For anyone interested, this is how I go about doing it:

version: "2"
services:
  mongo:
    container_name: mongo
    restart: on-failure:10
    image: mongo
    environment:
      - MONGO_INITDB_ROOT_USERNAME=<dbuser>
      - MONGO_INITDB_ROOT_PASSWORD=<dbpass>
      - MONGO_INITDB_DATABASE=db
    volumes:
      - ./data:/data/db
    ports:
      - "27017:27017"
    command: bash -c "mongod --repair && mongod"

mongod --repair will repair the issue with the lock file, then mongod will start mongo regularly, this is needed since the repair also shuts down mongo.

This way I do not change the docker-compose up command to start my service.

[xet7]

@ofekp

Thanks! I added to wiki link to this post. https://github.com/wekan/wekan/wiki#Repair