Macos When i upgrade mongodb6.0.0-build, connect refuse

mongodbapp

refuse

i upgrade mongodbapp@6.0.0-build, robo3T not connect. i’m not found problem;

connect refuse logs:

{"t":{"$date":"2022-11-01T17:34:36.384+08:00"},"s":"I",  "c":"CONTROL",  "id":23285,   "ctx":"-","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2022-11-01T17:34:36.419+08:00"},"s":"I",  "c":"NETWORK",  "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":17},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":17},"outgoing":{"minWireVersion":6,"maxWireVersion":17},"isInternalClient":true}}}
{"t":{"$date":"2022-11-01T17:34:36.423+08:00"},"s":"I",  "c":"NETWORK",  "id":4648602, "ctx":"main","msg":"Implicit TCP FastOpen in use."}
{"t":{"$date":"2022-11-01T17:34:36.430+08:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","namespace":"config.tenantMigrationDonors"}}
{"t":{"$date":"2022-11-01T17:34:36.430+08:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","namespace":"config.tenantMigrationRecipients"}}
{"t":{"$date":"2022-11-01T17:34:36.430+08:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"ShardSplitDonorService","namespace":"config.tenantSplitDonors"}}
{"t":{"$date":"2022-11-01T17:34:36.430+08:00"},"s":"I",  "c":"CONTROL",  "id":5945603, "ctx":"main","msg":"Multi threading initialized"}
{"t":{"$date":"2022-11-01T17:34:36.430+08:00"},"s":"I",  "c":"CONTROL",  "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1587,"port":27017,"dbPath":"/Users/labikemmy/Library/Application Support/MongoDB/Data","architecture":"64-bit","host":"LabikedeMacBook-Pro.local"}}
{"t":{"$date":"2022-11-01T17:34:36.431+08:00"},"s":"I",  "c":"CONTROL",  "id":23403,   "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"6.0.0","gitVersion":"e61bf27c2f6a83fed36e5a13c008a32d563babe2","modules":[],"allocator":"system","environment":{"distarch":"x86_64","target_arch":"x86_64"}}}}
{"t":{"$date":"2022-11-01T17:34:36.431+08:00"},"s":"I",  "c":"CONTROL",  "id":51765,   "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Mac OS X","version":"21.2.0"}}}
{"t":{"$date":"2022-11-01T17:34:36.431+08:00"},"s":"I",  "c":"CONTROL",  "id":21951,   "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"bindIp":"127.0.0.1","unixDomainSocket":{"enabled":false}},"storage":{"dbPath":"/Users/labikemmy/Library/Application Support/MongoDB/Data"},"systemLog":{"destination":"file","path":"/Users/labikemmy/Library/Application Support/MongoDB/Logs/mongo.log"}}}}
{"t":{"$date":"2022-11-01T17:34:36.433+08:00"},"s":"I",  "c":"NETWORK",  "id":5693100, "ctx":"initandlisten","msg":"Asio socket.set_option failed with std::system_error","attr":{"note":"acceptor TCP fast open","option":{"level":6,"name":261,"data":"00 04 00 00"},"error":{"what":"set_option: Invalid argument","message":"Invalid argument","category":"asio.system","value":22}}}
{"t":{"$date":"2022-11-01T17:34:36.448+08:00"},"s":"I",  "c":"STORAGE",  "id":22270,   "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"/Users/labikemmy/Library/Application Support/MongoDB/Data","storageEngine":"wiredTiger"}}
{"t":{"$date":"2022-11-01T17:34:36.455+08:00"},"s":"I",  "c":"STORAGE",  "id":22315,   "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=3584M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,remove=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=2000),statistics_log=(wait=0),json_output=(error,message),verbose=[recovery_progress:1,checkpoint_progress:1,compact_progress:1,backup:0,checkpoint:0,compact:0,evict:0,history_store:0,recovery:0,rts:0,salvage:0,tiered:0,timestamp:0,transaction:0,verify:0,log:0],"}}
{"t":{"$date":"2022-11-01T17:34:36.914+08:00"},"s":"W",  "c":"STORAGE",  "id":22347,   "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}
{"t":{"$date":"2022-11-01T17:34:36.914+08:00"},"s":"F",  "c":"STORAGE",  "id":28595,   "ctx":"initandlisten","msg":"Terminating.","attr":{"reason":"45: Operation not supported"}}
{"t":{"$date":"2022-11-01T17:34:36.914+08:00"},"s":"F",  "c":"ASSERT",   "id":23091,   "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":28595,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp","line":702}}
{"t":{"$date":"2022-11-01T17:34:36.914+08:00"},"s":"F",  "c":"ASSERT",   "id":23092,   "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}

Welcome to the MongoDB community @ohayo_mmy !

What version of MongoDB server were you running prior to upgrading to MongoDB 6.0?

In-place data file upgrades are only supported for adjacent major release series (eg 5.0 => 6.0). The error you encountered indicates you have skipped one or more major release upgrades and the existing data files are not compatible with the current version of MongoDB server you using.

Your options are:

  • Reinstall the original version of MongoDB server and follow the documented upgrade procedures for your deployment type (standalone, replica set, or sharded cluster). For example, if you were starting from MongoDB 4.4 standalone: Upgrade a Standalone to 5.0 then Upgrade a Standalone to 6.0.

  • iI your original server version requires several major version upgrades to get to your desired version (for example, if you are starting from 4.2 and need to go 4.2 => 4.4, 4.4 => 5.0, 5.0 =>6.0), you could use mongodump and mongorestore to recreate your deployment in a single step. You may encounter some (fixable) errors as the documented and tested upgrade path is via in-place upgrades through successive major releases.

  • If your existing data isn’t important, you could move (or remove) the contents of your current dbPath. When a MongoDB server restarts with an empty dbPath, it will initialise a fresh set of data files based on the current mongod version.

Regards,
Stennie

ok, i’m reinstall, thanks!