[SERVER-44941] Collection does not have UUID in KVCatalog Created: 04/Dec/19  Updated: 04/Dec/19  Resolved: 04/Dec/19

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

Type: Bug Priority: Major - P3
Reporter: shawn nolan Assignee: Carl Champain (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-43132 Exception; Collection does not have U... Closed
Operating System: ALL
Steps To Reproduce:
Participants:

 Description   

Note: this is related to https://jira.mongodb.org/browse/SERVER-43132 I think

I'm also getting this error after uninstalling `mongodb` (old version) and used this new solution (https://github.com/mongodb/homebrew-brew#setup).

After running brew services start mongodb-community I open a new terminal window to run mongo as suggested, but I get the following error

 some-MacBook-Air:~ some$ mongo
 MongoDB shell version v4.2.1
 connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb
 2019-12-03T23:02:33.517-0800 E QUERY [js] Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27017 :: caused by :: Connection refused :
 connect@src/mongo/shell/mongo.js:341:17
 @(connect):2:6
 2019-12-03T23:02:33.522-0800 F - [main] exception: connect failed
 2019-12-03T23:02:33.522-0800 E - [main] exiting with code 1
 

Then after looking at the logs I noticed something to do with exception in initAndListen: MustDowngrade: Collection does not have UUID in KVCatalog. Collection: admin.users. Here's the full error:

 2019-12-03T23:02:28.801-0800 I CONTROL [main] ***** SERVER RESTARTED *****
 2019-12-03T23:02:28.810-0800 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
 2019-12-03T23:02:28.816-0800 I CONTROL [initandlisten] MongoDB starting : pid=10798 port=27017 dbpath=/usr/local/var/mongodb 64-bit host=some-MacBook-Air.local
 2019-12-03T23:02:28.816-0800 I CONTROL [initandlisten] db version v4.2.1
 2019-12-03T23:02:28.816-0800 I CONTROL [initandlisten] git version: edf6d45851c0b9ee15548f0f847df141764a317e
 2019-12-03T23:02:28.817-0800 I CONTROL [initandlisten] allocator: system
 2019-12-03T23:02:28.817-0800 I CONTROL [initandlisten] modules: none
 2019-12-03T23:02:28.817-0800 I CONTROL [initandlisten] build environment:
 2019-12-03T23:02:28.817-0800 I CONTROL [initandlisten] distarch: x86_64
 2019-12-03T23:02:28.817-0800 I CONTROL [initandlisten] target_arch: x86_64
 2019-12-03T23:02:28.817-0800 I CONTROL [initandlisten] options: { config: "/usr/local/etc/mongod.conf", net:
 
{ bindIp: "127.0.0.1" }
 
, storage: \{ dbPath: "/usr/local/var/mongodb" }, systemLog: \{ destination: "file", logAppend: true, path: "/usr/local/var/log/mongodb/mongo.log" } }
 2019-12-03T23:02:28.820-0800 I STORAGE [initandlisten] Detected data files in /usr/local/var/mongodb created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
 2019-12-03T23:02:28.821-0800 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3584M,cache_overflow=(file_max=0M),session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress],
 2019-12-03T23:02:29.523-0800 I STORAGE [initandlisten] WiredTiger message [1575442949:523943][10798:0x117c65dc0], txn-recover: Recovering log 357 through 358
 2019-12-03T23:02:29.611-0800 I STORAGE [initandlisten] WiredTiger message [1575442949:611119][10798:0x117c65dc0], txn-recover: Recovering log 358 through 358
 2019-12-03T23:02:29.787-0800 I STORAGE [initandlisten] WiredTiger message [1575442949:787170][10798:0x117c65dc0], txn-recover: Main recovery loop: starting at 357/768 to 358/256
 2019-12-03T23:02:29.932-0800 I STORAGE [initandlisten] WiredTiger message [1575442949:932236][10798:0x117c65dc0], txn-recover: Recovering log 357 through 358
 2019-12-03T23:02:30.014-0800 I STORAGE [initandlisten] WiredTiger message [1575442950:14279][10798:0x117c65dc0], txn-recover: Recovering log 358 through 358
 2019-12-03T23:02:30.074-0800 I STORAGE [initandlisten] WiredTiger message [1575442950:74863][10798:0x117c65dc0], txn-recover: Set global recovery timestamp: (0,0)
 2019-12-03T23:02:30.207-0800 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
 2019-12-03T23:02:30.236-0800 I STORAGE [initandlisten] WiredTigerKVEngine shutting down
 2019-12-03T23:02:30.236-0800 I STORAGE [initandlisten] Shutting down session sweeper thread
 2019-12-03T23:02:30.237-0800 I STORAGE [initandlisten] Finished shutting down session sweeper thread
 2019-12-03T23:02:30.237-0800 I STORAGE [initandlisten] Shutting down journal flusher thread
 2019-12-03T23:02:30.381-0800 I STORAGE [initandlisten] Finished shutting down journal flusher thread
 2019-12-03T23:02:30.381-0800 I STORAGE [initandlisten] Shutting down checkpoint thread
 2019-12-03T23:02:30.381-0800 I STORAGE [initandlisten] Finished shutting down checkpoint thread
 2019-12-03T23:02:30.382-0800 I STORAGE [initandlisten] Downgrading WiredTiger datafiles.
 2019-12-03T23:02:30.534-0800 I STORAGE [initandlisten] WiredTiger message [1575442950:534770][10798:0x117c65dc0], txn-recover: Recovering log 358 through 359
 2019-12-03T23:02:30.597-0800 I STORAGE [initandlisten] WiredTiger message [1575442950:597547][10798:0x117c65dc0], txn-recover: Recovering log 359 through 359
 2019-12-03T23:02:30.745-0800 I STORAGE [initandlisten] WiredTiger message [1575442950:745695][10798:0x117c65dc0], txn-recover: Main recovery loop: starting at 358/2048 to 359/256
 2019-12-03T23:02:30.872-0800 I STORAGE [initandlisten] WiredTiger message [1575442950:872000][10798:0x117c65dc0], txn-recover: Recovering log 358 through 359
 2019-12-03T23:02:30.960-0800 I STORAGE [initandlisten] WiredTiger message [1575442950:960059][10798:0x117c65dc0], txn-recover: Recovering log 359 through 359
 2019-12-03T23:02:31.022-0800 I STORAGE [initandlisten] WiredTiger message [1575442951:22257][10798:0x117c65dc0], txn-recover: Set global recovery timestamp: (0,0)
 2019-12-03T23:02:31.348-0800 I STORAGE [initandlisten] exception in initAndListen: MustDowngrade: Collection does not have UUID in KVCatalog. Collection: admin.users, terminating
 2019-12-03T23:02:31.348-0800 I NETWORK [initandlisten] shutdown: going to close listening sockets...
 2019-12-03T23:02:31.348-0800 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-27017.sock
 2019-12-03T23:02:31.348-0800 I - [initandlisten] Stopping further Flow Control ticket acquisitions.
 2019-12-03T23:02:31.348-0800 I CONTROL [initandlisten] now exiting
 2019-12-03T23:02:31.349-0800 I CONTROL [initandlisten] shutting down with code:100
 



 Comments   
Comment by Carl Champain (Inactive) [ 04/Dec/19 ]

Hi shawn@shawnnolan.com,

Thanks for the report.
It is indeed a duplicate of SERVER-43132, please follow the instructions in this comment and it should fix your issue.

That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag.

Kind regards,
Carl

Comment by shawn nolan [ 04/Dec/19 ]

Title should probably be more like `Collection does not have UUID in KVCatalog`

Generated at Thu Feb 08 05:07:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.