run mongos due to .conf

[Tim]

hello,

my .conf file looks like this:


port = myport               
fork = true               
dbpath = /data/db/           
configdb = ip1:port1,ip2:port2,ip3:port3
logpath = /var/log/mongodb/mongodb.log


it's stores at /etc/mongos.conf


then I would like to execute something like this:
mongos --config /etc/mongos.conf
but that doesn't work

[Dwight Merriman]

what is the error message?

if you get "ERROR: could not read from config file" the problem is permissions on that file i would guess

[Tim]

the error code is:


error command line: unknown option dbpath
use --help for help

[Tim]

Is it possible to run mongos due to a .conf file?

[Tim]

by executing

mongos --configdb ip1:port1, ip2:port2, ip3:port3 --port 25001

I get the error:



Thu Nov  8 21:00:38 [Balancer] SyncClusterConnection connecting to [ip1:port1]
Thu Nov  8 21:00:38 [Balancer] SyncClusterConnection connecting to [ip2:port2]
Thu Nov  8 21:00:38 [Balancer] SyncClusterConnection connecting to [ip3:port3]
Thu Nov  8 21:00:38 [Balancer] scoped connection to ip1:port1, ip2:port2, ip3:port3 not being returned to the pool
Thu Nov  8 21:00:38 [Balancer] caught exception while doing balance: error checking clock skew of cluster  ip1:port1, ip2:port2, ip3:port3 :: caused by :: 13650 clock skew of the cluster  ip2:port2, ip3:port3 is too far out of bounds to allow distributed locking.

[Sam Helman]

This is a completely different error, and it has to do with clock skew among the nodes.   The original error is because "dbpath" is not a valid parameter for mongos (the config file was indeed being read correctly, it just contained the incorrect parameter "dbpath").