MacOS Sequoia 15.7.3环境下MongoDB-community@8.2启动后立即崩溃,无法连接的问题求助
MacOS Sequoia 15.7.3环境下MongoDB-community@8.2启动后立即崩溃,无法连接的问题求助
大家好,最近碰到个特别头疼的问题,想请各位帮忙分析下:
在我的MacOS Sequoia 15.7.3上,MongoDB-community@8.2每次启动后都会立刻崩溃,导致mongosh根本连不上服务。3周前我的系统还是15.6.2的时候一切正常,今天突然出问题后我特意升级到了15.7.3,结果情况完全没改善。
我已经尝试过完全卸载并重新安装MongoDB-community@8.2,但问题依旧存在。
我的mongod.conf配置
systemLog: destination: file path: /opt/homebrew/var/log/mongodb/mongo.log logAppend: true storage: dbPath: /opt/homebrew/var/mongodb net: bindIp: 127.0.0.1 port: 27017
终端操作流程
% brew services start mongodb/brew/mongodb-community ==> Successfully started `mongodb-community` (label: homebrew.mxcl.mongodb-community) % mongosh Current Mongosh Log ID: 69465e67e358526f1e91467b Connecting to: mongodb://127.0.0.1:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.5.10 MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017
日志尾部关键内容
{"t":{"$date":"2025-12-20T11:26:16.721+03:00"},"s":"I", "c":"WTEVICT", "id":22430, "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":{"ts_sec":1766219176,"ts_usec":721259,"thread":"10540:0x1f92fe240","session_name":"WT_CONNECTION.close","category":"WT_VERB_EVICTION","log_id":1000000,"category_id":15,"verbose_level":"INFO","verbose_level_id":0,"msg":"stopping eviction threads"}}} {"t":{"$date":"2025-12-20T11:26:16.721+03:00"},"s":"I", "c":"WTEVICT", "id":22430, "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":{"ts_sec":1766219176,"ts_usec":721297,"thread":"10540:0x1f92fe240","session_name":"WT_CONNECTION.close","category":"WT_VERB_EVICTION","log_id":1000000,"category_id":15,"verbose_level":"INFO","verbose_level_id":0,"msg":"waiting for eviction threads to stop"}}} {"t":{"$date":"2025-12-20T11:26:16.721+03:00"},"s":"I", "c":"WTEVICT", "id":22430, "ctx":"thread13","msg":"WiredTiger message","attr":{"message":{"ts_sec":1766219176,"ts_usec":721349,"thread":"10540:0x16d63f000","session_name":"eviction-server","category":"WT_VERB_EVICTION","log_id":1000000,"category_id":15,"verbose_level":"INFO","verbose_level_id":0,"msg":"eviction thread exiting"}}} {"t":{"$date":"2025-12-20T11:26:16.739+03:00"},"s":"I", "c":"STORAGE", "id":4795901, "ctx":"initandlisten","msg":"WiredTiger closed","attr":{"durationMillis":48}} {"t":{"$date":"2025-12-20T11:26:16.739+03:00"},"s":"I", "c":"STORAGE", "id":22279, "ctx":"initandlisten","msg":"shutdown: removing fs lock..."} {"t":{"$date":"2025-12-20T11:26:16.739+03:00"},"s":"I", "c":"-", "id":4784931, "ctx":"initandlisten","msg":"Dropping the scope cache for shutdown"} {"t":{"$date":"2025-12-20T11:26:16.739+03:00"},"s":"I", "c":"-", "id":10175800,"ctx":"initandlisten","msg":"Shutting down the standalone executor"} {"t":{"$date":"2025-12-20T11:26:16.739+03:00"},"s":"I", "c":"CONTROL", "id":20565, "ctx":"initandlisten","msg":"Now exiting"} {"t":{"$date":"2025-12-20T11:26:16.739+03:00"},"s":"I", "c":"CONTROL", "id":8423404, "ctx":"initandlisten","msg":"mongod shutdown complete","attr":{"Summary of time elapsed":{"Statistics":{"enterTerminalShutdownMillis":0,"stepDownReplCoordMillis":0,"quiesceModeMillis":0,"stopFLECrudMillis":0,"shutDownMirrorMaestroMillis":0,"shutDownWaitForMajorityServiceMillis":0,"shutDownGlobalConnectionPoolMillis":0,"shutDownSearchTaskExecutorsMillis":0,"shutDownFlowControlTicketHolderMillis":0,"shutDownAbortExpiredTransactionsThreadMillis":0,"shutDownRollbackUnderCachePressureThreadMillis":0,"killAllOperationsMillis":0,"shutDownOpenTransactionsMillis":0,"acquireRSTLMillis":0,"shutDownIndexBuildsCoordinatorMillis":0,"shutDownReplicaSetMonitorMillis":0,"shutDownTransportLayerMillis":0,"shutDownTTLMonitorMillis":0,"shutDownExpiredDocumentRemoverMillis":0,"shutDownStorageEngineMillis":80,"shutDownOtelMetricsMillis":0,"shutDownFTDCMillis":0,"shutDownReplicaSetNodeExecutorMillis":0,"shutDownOCSPMillis":0,"shutdownTaskTotalMillis":81}}}} {"t":{"$date":"2025-12-20T11:26:16.739+03:00"},"s":"I", "c":"CONTROL", "id":23138, "ctx":"initandlisten","msg":"Shutting down","attr":{"exitCode":62}}
我注意到日志最后显示exitCode:62,而且特别奇怪的是,brew明明提示“Successfully started”,但实际上服务启动后立刻就终止了。有没有朋友遇到过类似的情况,或者能帮我解读下这个退出码对应的问题,以及可能的解决方向?万分感谢!




