[SERVER-36577] Upgrade and cannot read /data/db Created: 10/Aug/18  Updated: 27/Oct/23  Resolved: 01/Oct/18

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

Type: Question Priority: Major - P3
Reporter: Marc Schwarzschild Assignee: Nick Brewer
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu


Participants:

 Description   

I upgraded Mongo on my Ubuntu computer.  Got this message.  I tried a whole lot of things.  Please advise.

 

```

mongod

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten] MongoDB starting : pid=26219 port=27017 dbpath=/data/db 64-bit host=risksheet

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten] db version v3.6.6

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten] git version: 6405d65b1d6432e138b44c13085d0c2fe235d6bd

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten] allocator: tcmalloc

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten] modules: none

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten] build environment:

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten]     distmod: ubuntu1604

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten]     distarch: x86_64

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten]     target_arch: x86_64

2018-08-09T21:53:20.537-0400 I CONTROL  [initandlisten] options: {}

2018-08-09T21:53:20.537-0400 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.

2018-08-09T21:53:20.537-0400 I STORAGE  [initandlisten]

2018-08-09T21:53:20.538-0400 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine

2018-08-09T21:53:20.538-0400 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem

2018-08-09T21:53:20.538-0400 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=991M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),cache_cursors=false,compatibility=(release="3.0",require_max="3.0"),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),

2018-08-09T21:53:21.472-0400 E STORAGE  [initandlisten] WiredTiger error (-31802) [1533866001:472274][26219:0x7fbb7b8b19c0], connection: Version incompatibility detected: unsupported WiredTiger file version: this build requires a maximum version of 2, and the file is version 3: WT_ERROR: non-specific WiredTiger error

2018-08-09T21:53:21.477-0400 E -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 421

2018-08-09T21:53:21.478-0400 I STORAGE  [initandlisten] exception in initAndListen: Location28595: -31802: WT_ERROR: non-specific WiredTiger error, terminating

2018-08-09T21:53:21.478-0400 I NETWORK  [initandlisten] shutdown: going to close listening sockets...

2018-08-09T21:53:21.478-0400 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock

2018-08-09T21:53:21.478-0400 I CONTROL  [initandlisten] now exiting

2018-08-09T21:53:21.478-0400 I CONTROL  [initandlisten] shutting down with code:100

root@risksheet:/opt/marc#```



 Comments   
Comment by Nick Brewer [ 01/Oct/18 ]

ms@thebrookhavengroup.com Since there's been no activity on this ticket in some time, I'm going to close it. Feel free to update this ticket with the requested information, and we'll reopen it for you.

-Nick

Comment by Nick Brewer [ 14/Sep/18 ]

ms@thebrookhavengroup.com We still need additional information to diagnose the problem. If this is still an issue for you, can you let us know:

  • what was the MongoDB version before and after the upgrade? 
  • what process did you follow to perform the upgrade?

Thanks,
Nick

Comment by Nick Brewer [ 10/Aug/18 ]

ms@thebrookhavengroup.com Thanks for your report. I'd like to confirm:

  • what was the MongoDB version before and after the upgrade? 
  • what process did you follow to perform the upgrade?

Thanks,
Nick

Comment by Marc Schwarzschild [ 10/Aug/18 ]

My long long night actually started on my Mac.  The brew upgrade there caused my mac to freeze up because of too many files open.  I tried some things there and got scared I'd ruin my mac.  Backed out of that and tried on my ubuntu computer.

 

M.

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