-
Type:
Question
-
Resolution: Done
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We were on 2.4.9 in a non-sharded 3-node cluster.I upgraded it to 2.6.7 by simply replacing the needfuls in /usr/bin.Everything worked fine, but it flagged me for --rest.So I tried flipping to YAML, but I had to flip back.
Here is our working configuration file:
logpath=/var/log/mongo/mongod.log logappend=true fork = true dbpath=/data/db/mongo replSet=Mongo-Radioedit-qa1-cloud port=37017 rest=true journal=true pidfilepath=/var/run/mongod/mongod.pid oplogSize=23552
Here is what I converted it to:
storage: dbPath: "/data/db/mongo" directoryPerDB: true journal: enabled: true systemLog: destination: file path: "/var/log/mongo/mongod.log" logAppend: true timeStampFormat: iso8601-utc processManagement: fork: true pidFilePath: "/var/run/mongod/mongod.pid" net: bindIp: 127.0.0.1 port: 37017 http: enabled: true RESTInterfaceEnabled: true #wireObjectCheck : false #unixDomainSocket: #enabled : true replication: oplogSizeMB: 23552 replSetName: "Mongo-Radioedit-qa1-cloud"
When I start up, the repl set is gone and the databases don't show up. I think the problem is that net:bindIP is where I was expecting to place the domain name of the server, but I can only use 127.0.0.1?
Anyway, when I put the old config file back in place, it works fine.