Re: mongodump mongorestore to a new db but have a problem

[Jenna]

Can you restart the server with logging set to verbosity 5 and post
the output of shell session right before the disconnect as well as the
disconnect messages?

On Jul 18, 12:48 pm, Craig <craig.wh...@ttiltd.com> wrote:
> I have a database (rails and using mongoid but I don't think that is the
> issue) that I dumped and restored...
>
> mongodump -d tti_framework_development
> mongorestore -d tti_framework_production dump/tti_framework_development
>
> and mongo is replicated with another server
>
> I can use this new database fine until I try to make changes and then I am
> disconnected.
>
> PRIMARY> rs.status()
> {
>     "set" : "mongoReplData",
>     "date" : ISODate("2012-07-18T16:46:14Z"),
>     "myState" : 1,
>     "members" : [
>         {
>             "_id" : 0,
>             "name" : "main:27017",
>             "health" : 1,
>             "state" : 1,
>             "stateStr" : "PRIMARY",
>             "optime" : {
>                 "t" : 1342629620000,
>                 "i" : 1
>             },
>             "optimeDate" : ISODate("2012-07-18T16:40:20Z"),
>             "self" : true
>         },
>         {
>             "_id" : 1,
>             "name" : "not_main.ttinet:27017",
>             "health" : 1,
>             "state" : 2,
>             "stateStr" : "SECONDARY",
>             "uptime" : 3508,
>             "optime" : {
>                 "t" : 1342629620000,
>                 "i" : 1
>             },
>             "optimeDate" : ISODate("2012-07-18T16:40:20Z"),
>             "lastHeartbeat" : ISODate("2012-07-18T16:46:13Z"),
>             "pingMs" : 0
>         }
>     ],
>     "ok" : 1
>
> }
>
> /var/log/mongodb/mongodb.log shows connections accepted & ending but
> nothing out of the ordinary
>
> Was there another step I missed when adding the new db from the restore
> process?
>
> Craig