You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if you want to reproduce just start and then restart a licode docker container. MongoDb will crash with: ERROR: child process failed, exited with error number 100
this is caused by the owner of the DB folder.
If you insert: mongod --repair --dbpath $DB_DIR
infront of the startcommand at licode/extras/docker/initDockerLicode.sh: mongod --nojournal --dbpath $DB_DIR --logpath $BUILD_DIR/mongo.log --fork
all is working fine again. On every, and not just the first start.
The text was updated successfully, but these errors were encountered:
cracker0dks
changed the title
Mongo db not starting on second start and everything crashs
Docker - Mongo db not starting on second start. And then everything crashs
Jun 12, 2017
if you want to reproduce just start and then restart a licode docker container. MongoDb will crash with:
ERROR: child process failed, exited with error number 100
this is caused by the owner of the DB folder.
If you insert:
mongod --repair --dbpath $DB_DIR
infront of the startcommand at licode/extras/docker/initDockerLicode.sh:
mongod --nojournal --dbpath $DB_DIR --logpath $BUILD_DIR/mongo.log --fork
all is working fine again. On every, and not just the first start.
The text was updated successfully, but these errors were encountered: