upgrade problem

[stever]

Hi,

I had 2.06 running on a minimal sharded replica set cluster of 4 servers.  It was inadvertently upgraded to 2.2 with Yum 

without following any of the recommended process.  The system isn't in heavy use, so no real harm done, but I do want

to get it working again.  The symptom I am seeing is that when I connect to MongoS (normal operation) I always get this

error:  

error: {

"$err" : "socket exception [CONNECT_ERROR] for sgm1/192.168.0.160:30000,192.168.0.165:30000",

"code" : 11002

}

If I connect right into the mongod on port 30000 I can do queries and it is working ok.

If I connect into the config server on port 20000 it also seems healthy.

I'm suspecting that something has gone wrong with the config, but I'm not really sure what to look at.

Any ideas for me?

[stever]

Well, one thing for sure happened, the /etc/init.d/mongod file was replaced on me and it is missing the

replica set flag.  Is there some place that should really be.  I don't see any example of how to set it

in the .conf file.

Steve

[Octavian Covalschi]

I believe you just have to add 

replSet = yourRsName

http://docs.mongodb.org/manual/tutorial/deploy-replica-set/

--
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com
To unsubscribe from this group, send email to
mongodb-user...@googlegroups.com
See also the IRC channel -- freenode.net#mongodb

[stever]

I'm running on CentOS... Is there a proper place that the --replSet value should be set in the startup

scripts and conf?  I've made init.d files for my main mongod, config server, and arbitrator so I would like

to more the replSet value to the "right" place instead of jammed in the init.d file itself.

[stever]

Thanks... I guess that should have been obvious ;-)