Mongod错误(与自制软件一起安装)

时间:2018-01-06 13:34:21

标签: mongodb

我已经安装了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

任何帮助都会有所帮助。

2 个答案:

答案 0 :(得分:22)

  

2018-01-06T14:28:51.762 + 0100 F CONTROL [initandlisten] **重要提示:升级问题:在尝试升级到3.6之前,需要将数据文件完全升级到3.4版;有关详细信息,请参阅http://dochub.mongodb.org/core/3.6-upgrade-fcv

这是您日志中的错误错误。

所以我猜你的@Override protected void onDraw(Canvas canvas){ if(scrollAdjustTries > 2){ return; } scrollAdjustTries++; mScrollView.scrollTo(0, mModel.scrollLine()); } 中有3.4个数据。

  1. 如果您想进行全新安装,只需删除/data/db的内容并重新启动/data/db
    1. 获得3.4 mongod
    2. 参考:https://docs.mongodb.com/manual/release-notes/3.6-upgrade-standalone/

答案 1 :(得分:9)

错误告诉您在/ 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 install specific version of formula?
  3. 使用#2返回3.4然后使用mongo进入mongo shell并运行db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )。退出mongo shell并使用brew switch命令切换回3.6。