I am trying to start mongos using config file with YAML format. it is throwing error saying "Unrecognized option: sharding.configDB". I am running this on centos6.
Any help will be highly appreciated.
Config file:
systemLog:
destination: file
path: REPLACEWITHLOGPATH
quiet: true
processManagement:
fork: true
net:
bindIp: REPLACEWITHIP
port: REPLACEWITHPORT
storage:
dbPath: REPLACEWITHDBPATH
sharding:
clusterRole: shardsvr
configDB: "172.16.4.61:27019"
I believe you need to remove the clusterRole: shardsvr from your mongos configuration file
Related
I am new to mongodb.
I want to create a Shard Cluster with single Replica Set,In future, if I want to want to extend it will be easy.
Now, Have 4 Ubuntu machine, 1 will work as Router(mongos) and remaining 3 as used as replica set(Primary,Secondary,Secondary).
# mongod.conf
# for documentation of all options, see:
# http://docs.mongodb.org/manual/reference/configuration-options/
# Where and how to store data.
storage:
dbPath: /mnt/md0/data/mongodb/dbdata/
journal:
enabled: true
# engine:
# wiredTiger:
# where to write logging data.
systemLog:
destination: file
logAppend: true
path: /mnt/md0/data/mongodb/logs/mongod.log
# network interfaces
net:
port: 27017
bindIp: 127.0.0.1
#processManagement:
security:
keyFile: /opt/mongo/mongo-keyfile
#operationProfiling:
replication:
replSetName: rs0
sharding:
clusterRole: configsvr
## Enterprise-Only Options:
#auditLog:
#snmp:**strong text**
#mongos.conf
# where to write logging data.
systemLog:
destination: file
logAppend: true
path: /var/log/mongodb/mongos.log
# network interfaces
net:
port: 27017
#bindIp: 127.0.0.1,192.10.10.10
security:
keyFile: /opt/mongo/mongo-keyfile
sharding:
configDB: rs0/Primary_Rs:27017,Secondary1_Rs:27017,Secondary2_Rs:27017
When I am trying to add the Shard in mongos console, I am getting error
Please help me to resolve me the issue.
Thank you In Advance
See you have 2 sharding part in your conf file... and first one config clusterRole as configsvr => remove/comment this one, and retry
I am trying to restrict the mongodb to local ip, it is not working.
Using MongoDb 3.2 version.
Below is the configuration file for the service, which is located in "C:\Program Files\MongoDB\Server\3.2\mongod.cfg"
systemLog:
destination: file
path: c:\data\mongo.log
quiet: false
logAppend: true
storage:
dbPath: C:\data\db
directoryPerDB: true
wiredTiger:
engineConfig:
cacheSizeGB: 2
directoryForIndexes: true
net:
port: 27017
bindIp: [127.0.0.0, 10.64.87.231]
replication:
oplogSizeMB: 500
replSetName: "mongoDbRepSet"
setParameter:
enableLocalhostAuthBypass: false
processManagement:
windowsService:
serviceName: "MongoDB"
displayName: "MongoDB 3.2 Standard"
description: "This is the service for MongoDB 3.2 Standard version"
I am using below command
mongod --config "C:\Program Files\MongoDB\Server\3.2\mongod.cfg" --install
I am restarting the mongo service after installing it with the configuraiton.
Strange thing is, when I open in RoboMongo and try to connect using 127.0.0.0 and 10.64.87.231 it is not working.
Also noticed that, it is connecting with ip addresses 127.0.0.1 to 127.0.0.255 (so many loopback ips?)
I also checked by assigning enableLocalhostAuthBypass: true but still not working.
What is wrong happening no idea. Please help me to restrict mongo service to give ip address.
I am not able to start mongod servers with replication using config file.
when issue the command
mongod --config /etc/mongod1.conf
throws an error-
Unrecognized option: replSet
Unrecognized option: oplogSizeMB
MongoDB Version: 3.0
# mongod.conf
# for documentation of all options, see:
# http://docs.mongodb.org/manual/reference/configuration-options/
# where to write logging data.
systemLog:
destination: file
logAppend: true
path: /var/log/mongodb/mongod.log
# Where and how to store data.
storage:
dbPath: /var/lib/mongo/test
journal:
enabled: true
# engine:
# mmapv1:
# wiredTiger:
# how the process runs
processManagement:
fork: true # fork and run in background
pidFilePath: /var/run/mongodb/mongod.pid # location of pidfile
# network interfaces
net:
port: 27030
# bindIp: 127.0.0.1 # Listen to local interface only, comment to listen on all interfaces.
#security:
#operationProfiling:
replication:
replSet: testrep
oplogSizeMB: 1024
#sharding:
## Enterprise-Only Options
please help me.
Just ident replSet and oplogSizeMB lines two spaces to the right. That's the thing with yaml
My mongodb replica set server is failing on start. followin is my config file:
# mongod.conf
storage:
dbPath: /var/lib/mongodb
journal:
enabled: true
systemLog:
destination: file
logAppend: true
path: /var/log/mongodb/mongod.log
net:
port: 27017
# bindIp: 127.0.0.1
security:
authorization: enabled
keyFile: /home/gurbakhshish/dbKey/mongodb.key
replication:
replSetName: "nm-prd-dbs"
is this config correct. I dont have the issue if i comment security section of config file
We are trying to set up mongodb's remote access by using a config file, and are having trouble running the config file in the bin folder.
When we put our script through YAML Lint it says its valid, but when we run our file in command prompt it interchanges two errors 1) Unrecognized Option: Storage and 2) Unrecognized Option: SystemLog
This is our config file
storage:
dbPath: C:\\data\\db
enabled: true
systemLog:
destination: file
logAppend: true
logpath: C:\\data\\log\\mongo.log
net:
port: 27017
bindIp: 127.0.0.1
our command in command prompt is
mongod -f mongo.config.txt
Please Help <3
You have a couple of errors in your config (for MongoDB 3.2):
There is no storage.enabled option, I think you meant storage.journal.enabled
There is no systemLog.logpath option, this should be systemLog.path
This modified config file seems to work as expected:
storage:
dbPath: C:\\data\\db
journal:
enabled: true
systemLog:
destination: file
logAppend: true
path: C:\\data\\log\\mongo.log
net:
port: 27017
bindIp: 127.0.0.1
You can browse for more options in the Configuration File Options page
This happen due to invalid yaml syntax. In my case, i missed the space between dbPath and value
Incorrect
storage:
dbPath:"./data/db"
Correct
storage:
dbPath: "./data/db"
This happened with me because I deleted a space in the configuration file.
storage:
dbPath: /var/lib/mongo
journal:
enabled: true
I got this error, when the configuration file had the below state, note the gap before enabled:
storage:
dbPath: /var/lib/mongo
journal:
enabled: true