Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
upgrade problem
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  5 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
stever  
View profile  
 More options Sep 27 2012, 10:48 am
From: stever <sritacc...@gmail.com>
Date: Thu, 27 Sep 2012 07:48:57 -0700 (PDT)
Local: Thurs, Sep 27 2012 10:48 am
Subject: upgrade problem

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?


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
stever  
View profile  
 More options Sep 27 2012, 11:10 am
From: stever <sritacc...@gmail.com>
Date: Thu, 27 Sep 2012 08:10:21 -0700 (PDT)
Local: Thurs, Sep 27 2012 11:10 am
Subject: Re: upgrade problem

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Octavian Covalschi  
View profile  
 More options Sep 27 2012, 11:12 am
From: Octavian Covalschi <octavian.covals...@gmail.com>
Date: Thu, 27 Sep 2012 10:12:08 -0500
Local: Thurs, Sep 27 2012 11:12 am
Subject: Re: [mongodb-user] Re: upgrade problem

I believe you just have to add

replSet = yourRsName

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
stever  
View profile  
 More options Sep 27 2012, 11:27 am
From: stever <sritacc...@gmail.com>
Date: Thu, 27 Sep 2012 08:27:21 -0700 (PDT)
Local: Thurs, Sep 27 2012 11:27 am
Subject: Re: upgrade problem

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.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
stever  
View profile  
 More options Sep 27 2012, 11:52 am
From: stever <sritacc...@gmail.com>
Date: Thu, 27 Sep 2012 08:52:04 -0700 (PDT)
Local: Thurs, Sep 27 2012 11:52 am
Subject: Re: [mongodb-user] Re: upgrade problem

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »