Discussion:
MMS Setup/Deploy
(too old to reply)
Jon Petitta
2014-11-20 00:07:12 UTC
Permalink
I created a shard configuration with 6 nodes using MMS, the first time this
worked like a charm.

But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.

Ran through the setup wizard again, get all the way to the end, then it
states.

TypeError: a is undefined

So I attempted to configure the cluster manually, which works for the most
part, but once it is fully deployed, the view mode looks nothing like it
used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Asya Kamsky
2014-11-20 23:11:47 UTC
Permalink
You should have been able to just upgrade the cluster to a new version
without unmanaging it.

Have you checked the agent logs? Usually if there was an error you would
find it there (it might not be an obvious explanation but it will help the
MMS folks figure out what went wrong).

Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first time
this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end, then it
states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for the most
part, but once it is fully deployed, the view mode looks nothing like it
used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups
"mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CAOe6dJA4s663DPNyPpWuqgCSL6n6W0wb%3DGw-xv8eg%2B6e0rjG%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Jon Petitta
2014-11-21 04:34:04 UTC
Permalink
I didn't know how to go about doing it, I found the versions later on...

The logs are showing in goal/computing state for everything except.

mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Cannot call FindOne(null)
in coll (local.clustermanager) on a non-running Mongo instance or otherwise
nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error reading from local
db: <Clust28_SNP_1_36> [23:30:17.865] Error querying local.clustermanager
collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot call FindOne(null) in
coll (local.clustermanager) on a non-running Mongo instance or otherwise
nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36error getting nextVersion
for (mongodb1:27000): <Clust28_SNP_1_36> [23:30:17.865] Error reading from
local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
As a note I'm running local Ubuntu Server vm's.
Post by Asya Kamsky
You should have been able to just upgrade the cluster to a new version
without unmanaging it.
Have you checked the agent logs? Usually if there was an error you would
find it there (it might not be an obvious explanation but it will help the
MMS folks figure out what went wrong).
Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first time
this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end, then it
states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for the
most part, but once it is fully deployed, the view mode looks nothing like
it used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups
"mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/1b7a7c10-77a7-42a3-b925-aed8928296b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jon Petitta
2014-11-21 05:09:18 UTC
Permalink
I blew away the /data dir for a few nodes, they rebuilt, no more errors.

I am getting some errors for the monitoring agent.

mongodb111/21/14 - 00:07:46info
Done. Sleeping for 54s...
mongodb111/21/14 - 00:07:46error
Failed to post ping Failure posting ping. Op: Post Err: read tcp
54.221.213.229:443: connection reset by peer at
monitoring-agent/components/conf.go:314 at
monitoring-agent/components/agent.go:348 at
monitoring-agent/components/agent.go:373 at
monitoring-agent/components/agent.go:386 at
mongodb.com/monitoring-agent/monitoring-agent.go:174 at
pkg/runtime/proc.c:247 at pkg/runtime/proc.c:1445
mongodb111/21/14 - 00:07:46info
Posting final ping payload containing 11/11 hosts
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure `replStatus`.
Err: `Failed command to mongodb3:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure `replStatus`.
Err: `Failed command to mongodb2:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure `replStatus`.
Err: `Failed command to mongodb4:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure `serverStatus`.
Err: `Failed command to mongodb3:27019 running [{serverStatus 1} {oplog 1}]
against DB admin. Err: `exception: Problem reading earliest entry from
oplog` at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure `serverStatus`.
Err: `Failed command to mongodb4:27019 running [{serverStatus 1} {oplog 1}]
against DB admin. Err: `exception: Problem reading earliest entry from
oplog` at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure `serverStatus`.
Err: `Failed command to mongodb2:27019 running [{serverStatus 1} {oplog 1}]
against DB admin. Err: `exception: Problem reading earliest entry from
oplog` at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46info
Sent all 11 host requests to channel. Awaiting responses...
Post by Jon Petitta
I didn't know how to go about doing it, I found the versions later on...
The logs are showing in goal/computing state for everything except.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Cannot call FindOne(null)
in coll (local.clustermanager) on a non-running Mongo instance or otherwise
nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error reading from local
db: <Clust28_SNP_1_36> [23:30:17.865] Error querying local.clustermanager
collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot call FindOne(null) in
coll (local.clustermanager) on a non-running Mongo instance or otherwise
nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36error getting nextVersion
for (mongodb1:27000): <Clust28_SNP_1_36> [23:30:17.865] Error reading from
local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
As a note I'm running local Ubuntu Server vm's.
Post by Asya Kamsky
You should have been able to just upgrade the cluster to a new version
without unmanaging it.
Have you checked the agent logs? Usually if there was an error you would
find it there (it might not be an obvious explanation but it will help the
MMS folks figure out what went wrong).
Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first time
this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end, then it
states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for the
most part, but once it is fully deployed, the view mode looks nothing like
it used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google
Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/8a30d493-ad14-4854-88d1-9ca1b6c04f7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jon Petitta
2014-11-22 03:58:41 UTC
Permalink
I am no longer getting automation agent error, just monitoring agent errors
as outlined below.

One thing I did notice though, even though I specified a shard deployment,
the nodes are spawning as stand alone instances...

This may be why the UI in MMS portal no longer looks like it used to...

I still can't deploy using the wizard, and doing manual appears to cause
the nodes to go stand alone, any help would be greatly appreciated!
Post by Jon Petitta
I blew away the /data dir for a few nodes, they rebuilt, no more errors.
I am getting some errors for the monitoring agent.
mongodb111/21/14 - 00:07:46info
Done. Sleeping for 54s...
mongodb111/21/14 - 00:07:46error
Failed to post ping Failure posting ping. Op: Post Err: read tcp
54.221.213.229:443: connection reset by peer at
monitoring-agent/components/conf.go:314 at
monitoring-agent/components/agent.go:348 at
monitoring-agent/components/agent.go:373 at
monitoring-agent/components/agent.go:386 at
mongodb.com/monitoring-agent/monitoring-agent.go:174 at
pkg/runtime/proc.c:247 at pkg/runtime/proc.c:1445
mongodb111/21/14 - 00:07:46info
Posting final ping payload containing 11/11 hosts
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure `replStatus`.
Err: `Failed command to mongodb3:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure `replStatus`.
Err: `Failed command to mongodb2:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure `replStatus`.
Err: `Failed command to mongodb4:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`serverStatus`. Err: `Failed command to mongodb3:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`serverStatus`. Err: `Failed command to mongodb4:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`serverStatus`. Err: `Failed command to mongodb2:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46info
Sent all 11 host requests to channel. Awaiting responses...
Post by Jon Petitta
I didn't know how to go about doing it, I found the versions later on...
The logs are showing in goal/computing state for everything except.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Cannot call
FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error reading from local
db: <Clust28_SNP_1_36> [23:30:17.865] Error querying local.clustermanager
collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot call FindOne(null) in
coll (local.clustermanager) on a non-running Mongo instance or otherwise
nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36error getting
nextVersion for (mongodb1:27000): <Clust28_SNP_1_36> [23:30:17.865] Error
reading from local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
As a note I'm running local Ubuntu Server vm's.
Post by Asya Kamsky
You should have been able to just upgrade the cluster to a new version
without unmanaging it.
Have you checked the agent logs? Usually if there was an error you
would find it there (it might not be an obvious explanation but it will
help the MMS folks figure out what went wrong).
Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first time
this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end, then it
states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for the
most part, but once it is fully deployed, the view mode looks nothing like
it used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google
Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/eb198181-6c39-4185-85b5-14948d31f602%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jon Petitta
2014-11-22 04:05:17 UTC
Permalink
Well I just fixed my own wizard deployment issue.

I had gone into versions and unchecked everything but 2.8, this caused the
issue.

I went back in and put it back to where the only thing unchecked is 2.8,
the issue is gone.

Guess I can upgrade somehow to 2.8 after 2.6 is deployed.
Post by Jon Petitta
I am no longer getting automation agent error, just monitoring agent
errors as outlined below.
One thing I did notice though, even though I specified a shard deployment,
the nodes are spawning as stand alone instances...
This may be why the UI in MMS portal no longer looks like it used to...
I still can't deploy using the wizard, and doing manual appears to cause
the nodes to go stand alone, any help would be greatly appreciated!
Post by Jon Petitta
I blew away the /data dir for a few nodes, they rebuilt, no more errors.
I am getting some errors for the monitoring agent.
mongodb111/21/14 - 00:07:46info
Done. Sleeping for 54s...
mongodb111/21/14 - 00:07:46error
Failed to post ping Failure posting ping. Op: Post Err: read tcp
54.221.213.229:443: connection reset by peer at
monitoring-agent/components/conf.go:314 at
monitoring-agent/components/agent.go:348 at
monitoring-agent/components/agent.go:373 at
monitoring-agent/components/agent.go:386 at
mongodb.com/monitoring-agent/monitoring-agent.go:174 at
pkg/runtime/proc.c:247 at pkg/runtime/proc.c:1445
mongodb111/21/14 - 00:07:46info
Posting final ping payload containing 11/11 hosts
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure `replStatus`.
Err: `Failed command to mongodb3:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure `replStatus`.
Err: `Failed command to mongodb2:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure `replStatus`.
Err: `Failed command to mongodb4:27019 running [{replSetGetStatus 1}]
against DB admin. Err: `not running with --replSet` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`serverStatus`. Err: `Failed command to mongodb3:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`serverStatus`. Err: `Failed command to mongodb4:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`serverStatus`. Err: `Failed command to mongodb2:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46info
Sent all 11 host requests to channel. Awaiting responses...
Post by Jon Petitta
I didn't know how to go about doing it, I found the versions later on...
The logs are showing in goal/computing state for everything except.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Cannot call
FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error reading from
local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36error getting
nextVersion for (mongodb1:27000): <Clust28_SNP_1_36> [23:30:17.865] Error
reading from local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
As a note I'm running local Ubuntu Server vm's.
Post by Asya Kamsky
You should have been able to just upgrade the cluster to a new version
without unmanaging it.
Have you checked the agent logs? Usually if there was an error you
would find it there (it might not be an obvious explanation but it will
help the MMS folks figure out what went wrong).
Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first time
this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end, then
it states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for the
most part, but once it is fully deployed, the view mode looks nothing like
it used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google
Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/4a51f0eb-8dd0-43f1-8ff7-bd49278208bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jon Petitta
2014-11-22 14:48:23 UTC
Permalink
I give up...

It would never deploy again correctly....

The replica sets don't wan't to init for some reason.

Now the agent logs are showing can't talk to mms.mongodb.com...
Post by Jon Petitta
Well I just fixed my own wizard deployment issue.
I had gone into versions and unchecked everything but 2.8, this caused the
issue.
I went back in and put it back to where the only thing unchecked is 2.8,
the issue is gone.
Guess I can upgrade somehow to 2.8 after 2.6 is deployed.
Post by Jon Petitta
I am no longer getting automation agent error, just monitoring agent
errors as outlined below.
One thing I did notice though, even though I specified a shard
deployment, the nodes are spawning as stand alone instances...
This may be why the UI in MMS portal no longer looks like it used to...
I still can't deploy using the wizard, and doing manual appears to cause
the nodes to go stand alone, any help would be greatly appreciated!
Post by Jon Petitta
I blew away the /data dir for a few nodes, they rebuilt, no more errors.
I am getting some errors for the monitoring agent.
mongodb111/21/14 - 00:07:46info
Done. Sleeping for 54s...
mongodb111/21/14 - 00:07:46error
Failed to post ping Failure posting ping. Op: Post Err: read tcp
54.221.213.229:443: connection reset by peer at
monitoring-agent/components/conf.go:314 at
monitoring-agent/components/agent.go:348 at
monitoring-agent/components/agent.go:373 at
monitoring-agent/components/agent.go:386 at
mongodb.com/monitoring-agent/monitoring-agent.go:174 at
pkg/runtime/proc.c:247 at pkg/runtime/proc.c:1445
mongodb111/21/14 - 00:07:46info
Posting final ping payload containing 11/11 hosts
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`replStatus`. Err: `Failed command to mongodb3:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`replStatus`. Err: `Failed command to mongodb2:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`replStatus`. Err: `Failed command to mongodb4:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`serverStatus`. Err: `Failed command to mongodb3:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`serverStatus`. Err: `Failed command to mongodb4:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`serverStatus`. Err: `Failed command to mongodb2:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at
monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46info
Sent all 11 host requests to channel. Awaiting responses...
Post by Jon Petitta
I didn't know how to go about doing it, I found the versions later on...
The logs are showing in goal/computing state for everything except.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Cannot call
FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error reading from
local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36error getting
nextVersion for (mongodb1:27000): <Clust28_SNP_1_36> [23:30:17.865] Error
reading from local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
As a note I'm running local Ubuntu Server vm's.
Post by Asya Kamsky
You should have been able to just upgrade the cluster to a new version
without unmanaging it.
Have you checked the agent logs? Usually if there was an error you
would find it there (it might not be an obvious explanation but it will
help the MMS folks figure out what went wrong).
Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first
time this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end, then
it states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for the
most part, but once it is fully deployed, the view mode looks nothing like
it used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google
Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it,
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/5908f748-be42-48ea-82aa-877ef25fb898%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Asya Kamsky
2014-11-22 15:22:02 UTC
Permalink
Hi Jon,

Sorry you were having so much trouble... One thing I might suggest if
you're not sick of trying, is to start with a new group. Sometimes it's
possible if you got your group in a "bad" state and it's not completely
cleaned up, it can cause hard-to-diagnose problems later. If you start
with a new group, then it's basically a clean slate.

I'm not sure how it's possible you were getting standalone nodes - do you
mean you were getting replica sets of one member for each shard? As far as
I know, it's not actually possible to make each shard a standalone mongod -
it must be a replica set.

Asya
Post by Jon Petitta
I give up...
It would never deploy again correctly....
The replica sets don't wan't to init for some reason.
Now the agent logs are showing can't talk to mms.mongodb.com...
Post by Jon Petitta
Well I just fixed my own wizard deployment issue.
I had gone into versions and unchecked everything but 2.8, this caused
the issue.
I went back in and put it back to where the only thing unchecked is 2.8,
the issue is gone.
Guess I can upgrade somehow to 2.8 after 2.6 is deployed.
Post by Jon Petitta
I am no longer getting automation agent error, just monitoring agent
errors as outlined below.
One thing I did notice though, even though I specified a shard
deployment, the nodes are spawning as stand alone instances...
This may be why the UI in MMS portal no longer looks like it used to...
I still can't deploy using the wizard, and doing manual appears to cause
the nodes to go stand alone, any help would be greatly appreciated!
Post by Jon Petitta
I blew away the /data dir for a few nodes, they rebuilt, no more errors.
I am getting some errors for the monitoring agent.
mongodb111/21/14 - 00:07:46info
Done. Sleeping for 54s...
mongodb111/21/14 - 00:07:46error
Failed to post ping Failure posting ping. Op: Post Err: read tcp
54.221.213.229:443: connection reset by peer at
monitoring-agent/components/conf.go:314 at monitoring-agent/components/agent.go:348
at monitoring-agent/components/agent.go:373 at
monitoring-agent/components/agent.go:386 at
mongodb.com/monitoring-agent/monitoring-agent.go:174 at
pkg/runtime/proc.c:247 at pkg/runtime/proc.c:1445
mongodb111/21/14 - 00:07:46info
Posting final ping payload containing 11/11 hosts
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`replStatus`. Err: `Failed command to mongodb3:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`replStatus`. Err: `Failed command to mongodb2:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`replStatus`. Err: `Failed command to mongodb4:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`serverStatus`. Err: `Failed command to mongodb3:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`serverStatus`. Err: `Failed command to mongodb4:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`serverStatus`. Err: `Failed command to mongodb2:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46info
Sent all 11 host requests to channel. Awaiting responses...
Post by Jon Petitta
I didn't know how to go about doing it, I found the versions later on...
The logs are showing in goal/computing state for everything except.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Cannot call
FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error reading from
local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36error getting
nextVersion for (mongodb1:27000): <Clust28_SNP_1_36> [23:30:17.865] Error
reading from local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
As a note I'm running local Ubuntu Server vm's.
Post by Asya Kamsky
You should have been able to just upgrade the cluster to a new
version without unmanaging it.
Have you checked the agent logs? Usually if there was an error you
would find it there (it might not be an obvious explanation but it will
help the MMS folks figure out what went wrong).
Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first
time this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end, then
it states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for
the most part, but once it is fully deployed, the view mode looks nothing
like it used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google
Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it,
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-
c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups
"mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/5908f748-be42-48ea-82aa-877ef25fb898%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/5908f748-be42-48ea-82aa-877ef25fb898%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CAOe6dJBVY0fxyJyVLQ6jwfymK1ktCdSrnt28omJO9%3Dacv%2Bj8Uw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Jon Petitta
2014-11-22 17:23:19 UTC
Permalink
I'm running fresh ubuntu server 14 vms, I even started completely over,
maybe it's something with my process...

This is my first time really using mongo, and I know linux basics, I
normally live in windows world.

I use virtual box for my vms, this following is what I did the first time,
which seemed to workout, just that I wanted to try 2.8, which is when I
messed things up.

I installed ubuntu server from scratch, hooked up my first automation agent
from MMS to this vm.

I then shut down the vm, us vboxmanage to clonehd and modifyhd to
multiattach.

Next I created 6 new vms based off of this base image.

I then proceeded to change the hostnames for the 6 machines.

I also modified /etc/hosts so they could talk to each other (I think I
messed this part up the second time around....)
I did notice something odd though, seems debian builds place 127.0.1.1
HOSTNAME in there for GDK support... I think this messes up mongo
I'm not really sure how to properly resolve the hosts entry for the local
machine..
currently I have it set to
127.0.0.1 HOSTNAME localhost
I removed the 127.0.1.1...

Once all that once configured, and in MMS deploy, all six vms registered, i
proceeded with deployment

I setup a cluster, 2shard, 3 node reps

The first time through, this worked like a charm, the cluster came up, had
2 shards, and a 3 node reps, performed some tests with a POC c# client, all
was good.

Then I noticed that I was not on 2.8, and I didn't see an obvious way to
upgrade.

So I figured I'd just start over, maybe I missed something.

I unmanaged the cluster, at which point I found the versions, made it so
that only 2.8 was checked, and was not able to deploy using wizard, gives
me that weird error I mentioned.

Next I attempted to do a manual cluster config and deploy, which seemed to
work as expected, but the nodes would never behave correctly after that

a lot of times they would never reach the goal state, always in some other
state.

When they where in goal state, in edit mode, it showed them as a cluster,
but when you go to view mode, they are listed as individual machines, not
in a cluster, just standalone instances of mongod...

Now I'm at the point I recreated the 6 linux vms form the base image, and
am trying this again from the beginning, but I"m still not sure I have the
hosts file correct.

This time around all the agents are saying they can't talk to mms, can't
update state, can't get jobs, can't get settings...


buntu11/22/14 - 12:21:05error
Error while refreshing settings: [12:21:05.625] Error retrieving settings
from MMS: Get
https://mms.mongodb.com/agents/api/automation/settings/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error retrieving settings from MMS: Get
https://mms.mongodb.com/agents/api/automation/settings/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error loading desired cluster configs : [12:21:05.625] Error retrieving
cluster config from
'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error retrieving cluster config from
'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
Error checking for new jobs: [12:20:54.617] Error retrieving jobs:
[12:20:54.617] Error retrieving jobs: Get
https://mms.mongodb.com/agents/api/automation/jobs/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
Error retrieving jobs: [12:20:54.617] Error retrieving jobs: Get
https://mms.mongodb.com/agents/api/automation/jobs/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
Error retrieving jobs: Get
https://mms.mongodb.com/agents/api/automation/jobs/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
mongodb511/22/14 - 12:20:53error
Error loading desired cluster configs : [12:20:53.241] Error retrieving
cluster config from
'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb5&ahs=mongodb5&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb5&ahs=mongodb5&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
mongodb511/22/14 - 12:20:53error
Error retrieving cluster config from
'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb5&ahs=mongodb5&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb5&ahs=mongodb5&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
mongodb311/22/14 - 12:20:20error
Error while refreshing settings: [12:20:20.299] Error retrieving settings
from MMS: Get
https://mms.mongodb.com/agents/api/automation/settings/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:20error
Error retrieving settings from MMS: Get
https://mms.mongodb.com/agents/api/automation/settings/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:14error
Error loading desired cluster configs : [12:20:14.283] Error retrieving
cluster config from
'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:14error
Error retrieving cluster config from
'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
Error checking for new jobs: [12:19:35.312] Error retrieving jobs:
[12:19:35.312] Error retrieving jobs: Get
https://mms.mongodb.com/agents/api/automation/jobs/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
Error retrieving jobs: [12:19:35.312] Error retrieving jobs: Get
https://mms.mongodb.com/agents/api/automation/jobs/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
Error retrieving jobs: Get
https://mms.mongodb.com/agents/api/automation/jobs/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:07error
Error while refreshing settings: [12:19:07.533] Error retrieving settings
from MMS: Get
https://mms.mongodb.com/agents/api/automation/settings/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
mongodb411/22/14 - 12:19:07error
Error retrieving settings from MMS: Get
https://mms.mongodb.com/agents/api/automation/settings/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:14error
Error sending status to MMS: [12:17:14.074] Error sending status to MMS:
Error POSTing to
https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
Post
https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:14error
Error sending status to MMS: Error POSTing to
https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
Post
https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:04error
Error while refreshing settings: [12:17:04.089] Error retrieving settings
from MMS: Get
https://mms.mongodb.com/agents/api/automation/settings/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:04error
Error retrieving settings from MMS: Get
https://mms.mongodb.com/agents/api/automation/settings/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
mongodb111/22/14 - 12:16:45error
Error sending status to MMS: [12:16:45.280] Error sending status to MMS:
Error POSTing to
https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=mongodb1&ahs=mongodb1&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
Post
https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=mongodb1&ahs=mongodb1&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
mongodb111/22/14 - 12:16:45error
Error sending status to MMS: Error POSTing to
https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=mongodb1&ahs=mongodb1&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
Post
https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=mongodb1&ahs=mongodb1&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 54.221.213.229:443: connection timed out
mongodb111/22/14 - 12:16:44error
Error checking for new jobs: [12:16:44.897] Error retrieving jobs:
[12:16:44.897] Error retrieving jobs: Get
https://mms.mongodb.com/agents/api/automation/jobs/v1/546782e6e4b0cb71bc2d3391?ah=mongodb1&ahs=mongodb1&av=1.3.2.739&aos=linux&aa=x86_64&ab=64:
dial tcp 75.101.156.249:443: connection timed out
Post by Asya Kamsky
Hi Jon,
Sorry you were having so much trouble... One thing I might suggest if
you're not sick of trying, is to start with a new group. Sometimes it's
possible if you got your group in a "bad" state and it's not completely
cleaned up, it can cause hard-to-diagnose problems later. If you start
with a new group, then it's basically a clean slate.
I'm not sure how it's possible you were getting standalone nodes - do you
mean you were getting replica sets of one member for each shard? As far as
I know, it's not actually possible to make each shard a standalone mongod -
it must be a replica set.
Asya
Post by Jon Petitta
I give up...
It would never deploy again correctly....
The replica sets don't wan't to init for some reason.
Now the agent logs are showing can't talk to mms.mongodb.com...
Post by Jon Petitta
Well I just fixed my own wizard deployment issue.
I had gone into versions and unchecked everything but 2.8, this caused
the issue.
I went back in and put it back to where the only thing unchecked is 2.8,
the issue is gone.
Guess I can upgrade somehow to 2.8 after 2.6 is deployed.
Post by Jon Petitta
I am no longer getting automation agent error, just monitoring agent
errors as outlined below.
One thing I did notice though, even though I specified a shard
deployment, the nodes are spawning as stand alone instances...
This may be why the UI in MMS portal no longer looks like it used to...
I still can't deploy using the wizard, and doing manual appears to
cause the nodes to go stand alone, any help would be greatly appreciated!
Post by Jon Petitta
I blew away the /data dir for a few nodes, they rebuilt, no more errors.
I am getting some errors for the monitoring agent.
mongodb111/21/14 - 00:07:46info
Done. Sleeping for 54s...
mongodb111/21/14 - 00:07:46error
Failed to post ping Failure posting ping. Op: Post Err: read tcp
54.221.213.229:443: connection reset by peer at
monitoring-agent/components/conf.go:314 at
monitoring-agent/components/agent.go:348 at
monitoring-agent/components/agent.go:373 at
monitoring-agent/components/agent.go:386 at
mongodb.com/monitoring-agent/monitoring-agent.go:174 at
pkg/runtime/proc.c:247 at pkg/runtime/proc.c:1445
mongodb111/21/14 - 00:07:46info
Posting final ping payload containing 11/11 hosts
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`replStatus`. Err: `Failed command to mongodb3:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`replStatus`. Err: `Failed command to mongodb2:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`replStatus`. Err: `Failed command to mongodb4:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`serverStatus`. Err: `Failed command to mongodb3:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`serverStatus`. Err: `Failed command to mongodb4:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`serverStatus`. Err: `Failed command to mongodb2:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46info
Sent all 11 host requests to channel. Awaiting responses...
Post by Jon Petitta
I didn't know how to go about doing it, I found the versions later on...
The logs are showing in goal/computing state for everything except.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Cannot call
FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error reading from
local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36error getting
nextVersion for (mongodb1:27000): <Clust28_SNP_1_36> [23:30:17.865] Error
reading from local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
As a note I'm running local Ubuntu Server vm's.
Post by Asya Kamsky
You should have been able to just upgrade the cluster to a new
version without unmanaging it.
Have you checked the agent logs? Usually if there was an error you
would find it there (it might not be an obvious explanation but it will
help the MMS folks figure out what went wrong).
Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first
time this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end,
then it states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for
the most part, but once it is fully deployed, the view mode looks nothing
like it used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google
Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it,
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-
c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups
"mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/5908f748-be42-48ea-82aa-877ef25fb898%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/5908f748-be42-48ea-82aa-877ef25fb898%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/c6eca7c2-4716-445f-997f-afd3f1a53971%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jon Petitta
2014-11-22 17:43:19 UTC
Permalink
something weird is definitely going on with my network configuration.

from vms or my host windows machine, if I resolve hostname with
host/nslookup, for one of the nodes, the ip is definitely not one of mine.

but if I ping via hostname, the correct ip is used.

I guess I'll have to figure out how to subdomain linux, so much fun.
Post by Jon Petitta
I'm running fresh ubuntu server 14 vms, I even started completely over,
maybe it's something with my process...
This is my first time really using mongo, and I know linux basics, I
normally live in windows world.
I use virtual box for my vms, this following is what I did the first time,
which seemed to workout, just that I wanted to try 2.8, which is when I
messed things up.
I installed ubuntu server from scratch, hooked up my first automation
agent from MMS to this vm.
I then shut down the vm, us vboxmanage to clonehd and modifyhd to
multiattach.
Next I created 6 new vms based off of this base image.
I then proceeded to change the hostnames for the 6 machines.
I also modified /etc/hosts so they could talk to each other (I think I
messed this part up the second time around....)
I did notice something odd though, seems debian builds place 127.0.1.1
HOSTNAME in there for GDK support... I think this messes up mongo
I'm not really sure how to properly resolve the hosts entry for the local
machine..
currently I have it set to
127.0.0.1 HOSTNAME localhost
I removed the 127.0.1.1...
Once all that once configured, and in MMS deploy, all six vms registered,
i proceeded with deployment
I setup a cluster, 2shard, 3 node reps
The first time through, this worked like a charm, the cluster came up, had
2 shards, and a 3 node reps, performed some tests with a POC c# client, all
was good.
Then I noticed that I was not on 2.8, and I didn't see an obvious way to
upgrade.
So I figured I'd just start over, maybe I missed something.
I unmanaged the cluster, at which point I found the versions, made it so
that only 2.8 was checked, and was not able to deploy using wizard, gives
me that weird error I mentioned.
Next I attempted to do a manual cluster config and deploy, which seemed to
work as expected, but the nodes would never behave correctly after that
a lot of times they would never reach the goal state, always in some other
state.
When they where in goal state, in edit mode, it showed them as a cluster,
but when you go to view mode, they are listed as individual machines, not
in a cluster, just standalone instances of mongod...
Now I'm at the point I recreated the 6 linux vms form the base image, and
am trying this again from the beginning, but I"m still not sure I have the
hosts file correct.
This time around all the agents are saying they can't talk to mms, can't
update state, can't get jobs, can't get settings...
buntu11/22/14 - 12:21:05error
Error while refreshing settings: [12:21:05.625] Error retrieving settings
from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error retrieving settings from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error loading desired cluster configs : [12:21:05.625] Error retrieving
cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error retrieving cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
[12:20:54.617] Error retrieving jobs: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
Error retrieving jobs: [12:20:54.617] Error retrieving jobs: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
Error retrieving jobs: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb511/22/14 - 12:20:53error
Error loading desired cluster configs : [12:20:53.241] Error retrieving
cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb5&ahs=mongodb5&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb511/22/14 - 12:20:53error
Error retrieving cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb5&ahs=mongodb5&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb311/22/14 - 12:20:20error
Error while refreshing settings: [12:20:20.299] Error retrieving settings
from MMS: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:20error
Error retrieving settings from MMS: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:14error
Error loading desired cluster configs : [12:20:14.283] Error retrieving
cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:14error
Error retrieving cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
[12:19:35.312] Error retrieving jobs: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
Error retrieving jobs: [12:19:35.312] Error retrieving jobs: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
Error retrieving jobs: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:07error
Error while refreshing settings: [12:19:07.533] Error retrieving settings
from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb411/22/14 - 12:19:07error
Error retrieving settings from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:14error
Error POSTing to
Post
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:14error
Error sending status to MMS: Error POSTing to
Post
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:04error
Error while refreshing settings: [12:17:04.089] Error retrieving settings
from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:04error
Error retrieving settings from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb111/22/14 - 12:16:45error
Error POSTing to
Post
dial tcp 54.221.213.229:443: connection timed out
mongodb111/22/14 - 12:16:45error
Error sending status to MMS: Error POSTing to
Post
dial tcp 54.221.213.229:443: connection timed out
mongodb111/22/14 - 12:16:44error
[12:16:44.897] Error retrieving jobs: Get
dial tcp 75.101.156.249:443: connection timed out
Post by Asya Kamsky
Hi Jon,
Sorry you were having so much trouble... One thing I might suggest if
you're not sick of trying, is to start with a new group. Sometimes it's
possible if you got your group in a "bad" state and it's not completely
cleaned up, it can cause hard-to-diagnose problems later. If you start
with a new group, then it's basically a clean slate.
I'm not sure how it's possible you were getting standalone nodes - do you
mean you were getting replica sets of one member for each shard? As far as
I know, it's not actually possible to make each shard a standalone mongod -
it must be a replica set.
Asya
Post by Jon Petitta
I give up...
It would never deploy again correctly....
The replica sets don't wan't to init for some reason.
Now the agent logs are showing can't talk to mms.mongodb.com...
Post by Jon Petitta
Well I just fixed my own wizard deployment issue.
I had gone into versions and unchecked everything but 2.8, this caused
the issue.
I went back in and put it back to where the only thing unchecked is
2.8, the issue is gone.
Guess I can upgrade somehow to 2.8 after 2.6 is deployed.
Post by Jon Petitta
I am no longer getting automation agent error, just monitoring agent
errors as outlined below.
One thing I did notice though, even though I specified a shard
deployment, the nodes are spawning as stand alone instances...
This may be why the UI in MMS portal no longer looks like it used to...
I still can't deploy using the wizard, and doing manual appears to
cause the nodes to go stand alone, any help would be greatly appreciated!
Post by Jon Petitta
I blew away the /data dir for a few nodes, they rebuilt, no more errors.
I am getting some errors for the monitoring agent.
mongodb111/21/14 - 00:07:46info
Done. Sleeping for 54s...
mongodb111/21/14 - 00:07:46error
Failed to post ping Failure posting ping. Op: Post Err: read tcp
54.221.213.229:443: connection reset by peer at
monitoring-agent/components/conf.go:314 at
monitoring-agent/components/agent.go:348 at
monitoring-agent/components/agent.go:373 at
monitoring-agent/components/agent.go:386 at
mongodb.com/monitoring-agent/monitoring-agent.go:174 at
pkg/runtime/proc.c:247 at pkg/runtime/proc.c:1445
mongodb111/21/14 - 00:07:46info
Posting final ping payload containing 11/11 hosts
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`replStatus`. Err: `Failed command to mongodb3:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`replStatus`. Err: `Failed command to mongodb2:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`replStatus`. Err: `Failed command to mongodb4:27019 running
[{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
at monitoring-agent/components/task.go:272 at
monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb3:27019Task failure
`serverStatus`. Err: `Failed command to mongodb3:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb4:27019Task failure
`serverStatus`. Err: `Failed command to mongodb4:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46errormongodb2:27019Task failure
`serverStatus`. Err: `Failed command to mongodb2:27019 running
[{serverStatus 1} {oplog 1}] against DB admin. Err: `exception: Problem
reading earliest entry from oplog` at monitoring-agent/components/task.go:272
at monitoring-agent/components/worker.go:155 at
monitoring-agent/components/worker.go:221 at
monitoring-agent/components/worker.go:233 at pkg/runtime/proc.c:1445`
mongodb111/21/14 - 00:07:46info
Sent all 11 host requests to channel. Awaiting responses...
Post by Jon Petitta
I didn't know how to go about doing it, I found the versions later on...
The logs are showing in goal/computing state for everything except.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Cannot call
FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36Error reading from
local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
mongodb411/20/14 - 23:30:17errorClust28_SNP_1_36error getting
nextVersion for (mongodb1:27000): <Clust28_SNP_1_36> [23:30:17.865] Error
reading from local db: <Clust28_SNP_1_36> [23:30:17.865] Error querying
local.clustermanager collection : <Clust28_SNP_1_36> [23:30:17.865] Cannot
call FindOne(null) in coll (local.clustermanager) on a non-running Mongo
instance or otherwise nil session.
As a note I'm running local Ubuntu Server vm's.
Post by Asya Kamsky
You should have been able to just upgrade the cluster to a new
version without unmanaging it.
Have you checked the agent logs? Usually if there was an error you
would find it there (it might not be an obvious explanation but it will
help the MMS folks figure out what went wrong).
Asya
Post by Jon Petitta
I created a shard configuration with 6 nodes using MMS, the first
time this worked like a charm.
But I noticed that the mongod was not 2.8, so I removed/unmanaged
everything so my deployment was empty again.
Ran through the setup wizard again, get all the way to the end,
then it states.
TypeError: a is undefined
So I attempted to configure the cluster manually, which works for
the most part, but once it is fully deployed, the view mode looks nothing
like it used to. I am unable to access the charts.
--
You received this message because you are subscribed to the Google
Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it,
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/8996d880-
c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/8996d880-c88f-4acd-a063-c2e57aa4c0b4%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "mongodb-user"
group.
http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mongodb-user/5908f748-be42-48ea-82aa-877ef25fb898%40googlegroups.com
<https://groups.google.com/d/msgid/mongodb-user/5908f748-be42-48ea-82aa-877ef25fb898%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/6eec1477-7a9a-44a5-914e-23cb15c7f0fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jon Petitta
2014-11-23 16:43:48 UTC
Permalink
Ok, I'm not sure what is going on with the host/nslookup stuff...

I decided to give it a break yesterday, and decided to have a look at it
this morning.

My deployment appears to be in an odd state, anyway I'll start a new post
with my findings, so it won't get all confusing in here, you can consider
this thread dead.
Post by Jon Petitta
something weird is definitely going on with my network configuration.
from vms or my host windows machine, if I resolve hostname with
host/nslookup, for one of the nodes, the ip is definitely not one of mine.
but if I ping via hostname, the correct ip is used.
I guess I'll have to figure out how to subdomain linux, so much fun.
I'm running fresh ubuntu server 14 vms, I even started completely over,
maybe it's something with my process...
This is my first time really using mongo, and I know linux basics, I
normally live in windows world.
I use virtual box for my vms, this following is what I did the first time,
which seemed to workout, just that I wanted to try 2.8, which is when I
messed things up.
I installed ubuntu server from scratch, hooked up my first automation
agent from MMS to this vm.
I then shut down the vm, us vboxmanage to clonehd and modifyhd to
multiattach.
Next I created 6 new vms based off of this base image.
I then proceeded to change the hostnames for the 6 machines.
I also modified /etc/hosts so they could talk to each other (I think I
messed this part up the second time around....)
I did notice something odd though, seems debian builds place 127.0.1.1
HOSTNAME in there for GDK support... I think this messes up mongo
I'm not really sure how to properly resolve the hosts entry for the local
machine..
currently I have it set to
127.0.0.1 HOSTNAME localhost
I removed the 127.0.1.1...
Once all that once configured, and in MMS deploy, all six vms registered,
i proceeded with deployment
I setup a cluster, 2shard, 3 node reps
The first time through, this worked like a charm, the cluster came up, had
2 shards, and a 3 node reps, performed some tests with a POC c# client, all
was good.
Then I noticed that I was not on 2.8, and I didn't see an obvious way to
upgrade.
So I figured I'd just start over, maybe I missed something.
I unmanaged the cluster, at which point I found the versions, made it so
that only 2.8 was checked, and was not able to deploy using wizard, gives
me that weird error I mentioned.
Next I attempted to do a manual cluster config and deploy, which seemed to
work as expected, but the nodes would never behave correctly after that
a lot of times they would never reach the goal state, always in some other
state.
When they where in goal state, in edit mode, it showed them as a cluster,
but when you go to view mode, they are listed as individual machines, not
in a cluster, just standalone instances of mongod...
Now I'm at the point I recreated the 6 linux vms form the base image, and
am trying this again from the beginning, but I"m still not sure I have the
hosts file correct.
This time around all the agents are saying they can't talk to mms, can't
update state, can't get jobs, can't get settings...
buntu11/22/14 - 12:21:05error
Error while refreshing settings: [12:21:05.625] Error retrieving settings
from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error retrieving settings from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error loading desired cluster configs : [12:21:05.625] Error retrieving
cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:21:05error
Error retrieving cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=ubuntu&ahs=ubuntu&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
[12:20:54.617] Error retrieving jobs: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
Error retrieving jobs: [12:20:54.617] Error retrieving jobs: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:20:54error
Error retrieving jobs: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb511/22/14 - 12:20:53error
Error loading desired cluster configs : [12:20:53.241] Error retrieving
cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb5&ahs=mongodb5&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb511/22/14 - 12:20:53error
Error retrieving cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb5&ahs=mongodb5&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb311/22/14 - 12:20:20error
Error while refreshing settings: [12:20:20.299] Error retrieving settings
from MMS: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:20error
Error retrieving settings from MMS: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:14error
Error loading desired cluster configs : [12:20:14.283] Error retrieving
cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb311/22/14 - 12:20:14error
Error retrieving cluster config from '
https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb3&ahs=mongodb3&av=1.3.2.739&aos=linux&aa=x86_64&ab=64'
: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
[12:19:35.312] Error retrieving jobs: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
Error retrieving jobs: [12:19:35.312] Error retrieving jobs: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:35error
Error retrieving jobs: Get
dial tcp 75.101.156.249:443: connection timed out
mongodb411/22/14 - 12:19:07error
Error while refreshing settings: [12:19:07.533] Error retrieving settings
from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
mongodb411/22/14 - 12:19:07error
Error retrieving settings from MMS: Get
dial tcp 54.221.213.229:443: connection timed out
ubuntu11/22/14 - 12:17:14error
Error POSTing to
Post
...
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/b47e31d8-1b4a-4765-ac90-a273a57bbb1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Continue reading on narkive:
Loading...