Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

MongoDB empty after upgrading docker-compose?

See original GitHub issue

I’m not sure what happened but all my data is gone somehow. I started Wekan as usual running docker-compose up and noticed some unusual lines in the output:

wekandb_1  | 2016-04-23T12:59:37.721+0000 I INDEX    [initandlisten] allocating new ns file /data/db/local.ns, filling with zeroes...
wekandb_1  | 2016-04-23T12:59:37.852+0000 I STORAGE  [FileAllocator] allocating new datafile /data/db/local.0, filling with zeroes...
wekandb_1  | 2016-04-23T12:59:37.852+0000 I STORAGE  [FileAllocator] creating directory /data/db/_tmp
wekandb_1  | 2016-04-23T12:59:37.859+0000 I STORAGE  [FileAllocator] done allocating datafile /data/db/local.0, size: 64MB,  took 0.004 secs
[...]
wekandb_1  | 2016-04-23T12:59:38.524+0000 I INDEX    [conn5] allocating new ns file /data/db/wekan.ns, filling with zeroes...
wekandb_1  | 2016-04-23T12:59:38.598+0000 I STORAGE  [FileAllocator] allocating new datafile /data/db/wekan.0, filling with zeroes...
wekandb_1  | 2016-04-23T12:59:38.601+0000 I STORAGE  [FileAllocator] done allocating datafile /data/db/wekan.0, size: 64MB,  took 0.002 secs
wekandb_1  | 2016-04-23T12:59:38.605+0000 I INDEX    [conn5] build index on: wekan.users properties: { v: 1, unique: true, key: { username: 1 }, name: "username_1", ns: "wekan.users", safe: true, sparse: 1 }

I tried to run mongodump and indeed all collections are empty. The only change I can think of is upgrading docker-compose from 1.6.2 to 1.7.0 but I can’t find anything related in their changelog. Any ideas what might have gone wrong and how to recover my data? Thanks a lot!

Issue Analytics

State:
Created 7 years ago
Comments:6

Top GitHub Comments

1reaction

spaasiscommented, Jun 8, 2016

@infertux It worked!

The new install had created a new ‘data’ directory to my wekan install directory. By your directions I did mv data /tmp/ a little digging to find the volume (turned out to be the first in …/docker/volumes) mv /var/lib/docker/volumes/$OLD_VOLUME_ID/_data data

Thanks again a thousand times!

1reaction

infertuxcommented, Jun 7, 2016

@simopaasisalo I found the right volume with tree /var/lib/docker/volumes/ and saw some .bson files (MongoDB file format). Hope that helps.