簡體   English   中英

Mongod錯誤(與自制軟件一起安裝)

[英]Mongod error (installed with homebrew)

我安裝了mongodb

brew install mongodb

創建文件夾

mkdir -p /data/db

處理權限

sudo chown -R `id -un` /data/db

mongod    

錯誤日志

2018-01-06T14:28:51.450+0100 I CONTROL  [initandlisten] MongoDB starting : pid=6120 port=27017 dbpath=/data/db 64-bit host=Zigas-MBP-2
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten] db version v3.6.1
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten] git version: 025d4f4fe61efd1fb6f0005be20cb45a004093d1
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2n  7 Dec 2017
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten] allocator: system
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten] modules: none
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten] build environment:
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten]     distarch: x86_64
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten]     target_arch: x86_64
2018-01-06T14:28:51.451+0100 I CONTROL  [initandlisten] options: {}
2018-01-06T14:28:51.452+0100 I -        [initandlisten] Detected data files in /data/db created by the 'mmapv1' storage engine, so setting the active storage engine to 'mmapv1'.
2018-01-06T14:28:51.470+0100 I JOURNAL  [initandlisten] journal dir=/data/db/journal
2018-01-06T14:28:51.471+0100 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
2018-01-06T14:28:51.494+0100 I JOURNAL  [durability] Durability thread started
2018-01-06T14:28:51.494+0100 I JOURNAL  [journal writer] Journal writer thread started
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten]
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten]
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten] ** WARNING: This server is bound to localhost.
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten] **          Remote systems will be unable toconnect to this server.
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten] **          Start the server with --bind_ip <address> to specify which IP
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten] **          addresses it should serve responses from, or with --bind_ip_all to
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten] **          bind to all interfaces. If this behavior is desired, start the
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten] **          server with --bind_ip 127.0.0.1 to disable this warning.
2018-01-06T14:28:51.495+0100 I CONTROL  [initandlisten]
2018-01-06T14:28:51.762+0100 F CONTROL  [initandlisten] ** IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.4 before attempting an upgrade to 3.6; see http://dochub.mongodb.org/core/3.6-upgrade-fcv for more details.
2018-01-06T14:28:51.762+0100 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2018-01-06T14:28:51.763+0100 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2018-01-06T14:28:51.763+0100 I REPL     [initandlisten] shutdown: removing all drop-pending collections...
2018-01-06T14:28:51.763+0100 I REPL     [initandlisten] shutdown: removing checkpointTimestamp collection...
2018-01-06T14:28:51.763+0100 I STORAGE  [initandlisten] shutdown: waiting for fs preallocator...
2018-01-06T14:28:51.763+0100 I STORAGE  [initandlisten] shutdown: final commit...
2018-01-06T14:28:51.770+0100 I JOURNAL  [initandlisten] journalCleanup...
2018-01-06T14:28:51.770+0100 I JOURNAL  [initandlisten] removeJournalFiles
2018-01-06T14:28:51.770+0100 I JOURNAL  [initandlisten] old journal file will be removed: /data/db/journal/j._0
2018-01-06T14:28:51.771+0100 I JOURNAL  [initandlisten] Terminating durability thread ...
2018-01-06T14:28:51.870+0100 I JOURNAL  [journal writer] Journal writer thread stopped
2018-01-06T14:28:51.870+0100 I JOURNAL  [durability] Durability thread stopped
2018-01-06T14:28:51.870+0100 I STORAGE  [initandlisten] shutdown: closing all files...
2018-01-06T14:28:51.883+0100 I STORAGE  [initandlisten] closeAllFiles() finished
2018-01-06T14:28:51.883+0100 I STORAGE  [initandlisten] shutdown: removing fs lock...
2018-01-06T14:28:51.883+0100 I CONTROL  [initandlisten] now exiting
2018-01-06T14:28:51.883+0100 I CONTROL  [initandlisten] shutting down with code:62

任何幫助都會被強化。

2018-01-06T14:28:51.762 + 0100 F CONTROL [initandlisten] **重要提示:升級問題:在嘗試升級到3.6之前,需要將數據文件完全升級到3.4版; 有關詳細信息,請參閱http://dochub.mongodb.org/core/3.6-upgrade-fcv

這是您日志中的錯誤錯誤。

所以我猜你的/data/db有3.4個數據。

  1. 如果要進行全新安裝,只需刪除/data/db的內容並重新啟動mongod

要么

  1. 獲得3.4 mongod

參考: https//docs.mongodb.com/manual/release-notes/3.6-upgrade-standalone/

該錯誤告訴您在/ data / db中有mongo 3.4數據但是安裝了3.6版本的Mongo。

要解決此問題,您可以使用下面列出的選項之一...

  1. 刪除/data/db的內容並重啟mongod 這可能應該備份,否則您將丟失數據。
  2. 安裝mongodb 3.4你可以檢查你以前是否使用brew list --versions mongodb安裝它,然后如果3.4。*版本出現,3.4.10例如使用brew switch mongodb 3.4.10移回到那個版本。 如果您從未安裝過該版本,請參閱此答案以安裝舊版本的Homebrew安裝特定版本的公式?
  3. 使用#2移回3.4然后使用mongo進入mongo shell並運行db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } ) 退出mongo shell並使用brew switch命令切換回3.6。

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM