Note that there are some explanatory texts on larger screens.

plurals
  1. POTrouble connecting to Mongo Config Server from mongos
    text
    copied!<p>Folks,</p> <p>I am setting up a MongoDB Cluster. The problem is when I am starting up 'mongos' it fails to connect to Mongod Config Server. If I start 'mongos' from localhost with same server as Mongod Config Server it connects &amp; works.</p> <p>localhost-$ mongos --port 30000 --configdb server-02:20000 [<strong>Works</strong>]</p> <p>server-01-$ mongos --port 30000 --configdb server-02:20000 [<strong>Does Not Work</strong>]</p> <p>Since from localhost I am able to start mongos by connecting to mongo config server &amp; execute queries, it appears that config server is running fine.</p> <p>Not able to understand what prevents servers to connect to one of their peers. When I attemped to connect first time from localhost, I got a prompt from OS asking whether process 'mongos' should be allowed to accept incoming connections for which I clicked allow. Perhaps if server fails silently because of this permission issue, with no way to prompt.</p> <p><strong>Error I recieve:</strong></p> <p>Sun May 8 01:14:46 ./mongos db version v1.8.1, pdfile version 4.5 starting (--help for usage) Sun May 8 01:14:46 git version: a429cd4f535b2499cc4130b06ff7c26f41c00f04 Sun May 8 01:14:46 build sys info: Linux bs-linux64.10gen.cc 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41 uncaught exception in mongos main: 11002 socket exception [6] server [server-02:20000] mongos connectionpool error: couldn't connect to server server-02:20000</p> <hr> <p>Well I did try clean install yet the problem persisted, so I moved my mongos to a different server with new install &amp; it appears to connect to config server without any issue. Apparently there is some sort of socket contention issue with first server I tried to run mongos.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload