[SERVER-29744] After relocating, server does not start Created: 20/Jun/17  Updated: 14/Aug/18  Resolved: 20/Jun/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.11
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tarik Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: docker, envc, rfi, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: Linux
Steps To Reproduce:

scp you /data/db/ directory
mongod --dbpath /the/new/directory/ OR
mongod --dbpath /the/new/directory/ --repair

Participants:

 Description   

Hello, relocating data directory to a larger server collapsed out data base. Server does not start.

Here is the error:

root@8bc03f2a68dc:/data/db# mongod --repair
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] MongoDB starting : pid=23 port=27017 dbpath=/data/db 64-bit host=8bc03f2a68dc
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] db version v3.2.11
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] git version: 009580ad490190ba33d1c6253ebd8d91808923e4
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1t 3 May 2016
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] allocator: tcmalloc
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] modules: none
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] build environment:
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] distmod: debian81
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] distarch: x86_64
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] target_arch: x86_64
2017-06-20T13:42:12.174+0000 I CONTROL [initandlisten] options:

{ repair: true }

2017-06-20T13:42:12.198+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2017-06-20T13:42:12.198+0000 W - [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
2017-06-20T13:42:12.198+0000 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
2017-06-20T13:42:12.198+0000 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
2017-06-20T13:42:12.198+0000 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=150G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2017-06-20T13:42:12.369+0000 E STORAGE [initandlisten] WiredTiger (-31802) [1497966132:369501][23:0x7fa5935dfcc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2017-06-20T13:42:12.369+0000 E STORAGE [initandlisten] WiredTiger (0) [1497966132:369558][23:0x7fa5935dfcc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2017-06-20T13:42:12.369+0000 E STORAGE [initandlisten] WiredTiger (0) [1497966132:369564][23:0x7fa5935dfcc0], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
2017-06-20T13:42:12.369+0000 E STORAGE [initandlisten] WiredTiger (0) [1497966132:369571][23:0x7fa5935dfcc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2017-06-20T13:42:12.370+0000 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
2017-06-20T13:42:12.370+0000 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2017-06-20T13:42:12.370+0000 I CONTROL [initandlisten] dbexit: rc: 100
root@8bc03f2a68dc:/data/db#



 Comments   
Comment by Kelsey Schubert [ 20/Jun/17 ]

Hi tarikaltuncu,

Please note that mongod must be stopped while transferring data files using cp.

Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group.

Kind regards,
Thomas

Comment by Tarik [ 20/Jun/17 ]

Hi Thomas,

Yes, mongod was running on a Docker instance during the transfer (cp) of
data files.

Thanks,

Comment by Kelsey Schubert [ 20/Jun/17 ]

Hi tarikaltuncu,

This error suggests that some sort of disk corruption occurred while data files were being moved. Would you please clarify the steps you took to move these files? Was the mongod running while the files were being copied?

Thank you,
Thomas

Generated at Thu Feb 08 04:21:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.