2016-02-05 101 views
1

我在Azure VPS上运行Ubuntu 15。我安装了MongoDB并启动并运行正常。于是,我停止了mongod服务,我改变了数据库路径和日志路径mongod.conf指向我一个附加的磁盘上创建的目录:Mongo无法连接

# Where and how to store data. 
storage: 
    dbPath: /datadrive/lib/mongodb 
    journal: 
    enabled: true 
# engine: 
# mmapv1: 
# wiredTiger: 

# where to write logging data. 
systemLog: 
    destination: file 
    logAppend: true 
    path: /datadrive/log/mongodb/mongod.log 

我重新启动整个VPS进行双重确认的新变化生效。现在,当我键入mongo我收到以下错误:如果我扭转我的变化,并使用原来的loglib位置

2016-02-05T14:49:41.004+0000 W NETWORK [thread1] Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused 
2016-02-05T14:49:41.018+0000 E QUERY [thread1] Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed : 
[email protected]/mongo/shell/mongo.js:224:14 
@(connect):1:6 

,它的工作原理。我能做些什么来确保使用新地点?

编辑

保留旧日志的位置和尝试上述步骤后,我得到了在日志中以下内容:

2016-02-05T15:19:47.049+0000 I CONTROL [main] ***** SERVER RESTARTED ***** 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten] MongoDB starting : pid=1158 port=27017 dbpath=/datadrive/lib/mongodb 64-bit host=CLIENTPROJECTS 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten] db version v3.2.1 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten] git version: a14d55980c2cdc565d4704a7e3ad37e4e535c1b2 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2d 9 Jul 2015 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten] allocator: tcmalloc 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten] modules: none 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten] build environment: 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten]  distmod: ubuntu1404 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten]  distarch: x86_64 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten]  target_arch: x86_64 
2016-02-05T15:19:47.146+0000 I CONTROL [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1", port: 27017 }, storage: { dbPath: "/datadrive/lib/mongodb", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } } 
2016-02-05T15:19:47.693+0000 I STORAGE [initandlisten] exception in initAndListen: 98 Unable to create/open lock file: /datadrive/lib/mongodb/mongod.lock errno:13 Permission denied Is a mongod instance already running?, terminating 
2016-02-05T15:19:47.693+0000 I CONTROL [initandlisten] dbexit: rc: 100 
+0

mongodb启动时的任何日志?看来运行mongod的帐户在新目录中没有保留。 – Peter

+0

@Peter没有日志。它没有使用新的日志位置。有任何想法吗? – Coop

+1

保持旧的日志位置,看看出了什么问题 – Peter

回答

1

首先,你可以检查是否mongod的开始:sudo lsof -i | grep 27017和然后检查日志/datadrive/log/mongodb/mongod.log中的内容。

编辑:

停止的mongod的所有实例(ps aux | grep mongod应该什么都不显示的运行),删除锁定文件rm /datadrive/lib/mongodb/mongod.lock,并重新启动服务。

EDIT2:从配置/datadrive/lib/mongodb//datadrive/log/mongodb/应该存在,属于MongoDB的用户

目录。默认情况下它是mongodb:mongodb,在/etc/init.d/mongodb中定义为DAEMONUSER

+0

在该位置没有创建日志,因为整个问题是lib和log的新路径。使用新路径并不开心,所以它不会记录到它。 – Coop

+0

我使用'sudo mkdir'创建了新的位置,以便它们拥有root用户和组。他们都有755个权限。 – Coop

+0

我创建的新的lib和日志是空的。旧的日志和文件在 – Coop