MMS Automation/Monitoring Agents show errors even though MongoDB process logs A OK

3,728 views
Skip to first unread message

Jon Petitta

unread,
Nov 23, 2014, 12:38:18 PM11/23/14
to mongod...@googlegroups.com
My setup.

6 Ubuntu Server 14.04.1 LTS VMs running under VirtualBox on my Windows 7 host.

It would seem that the actual MongoDB deployment was successful, as all the MongoDB process logs are A OK.

Does anyone have any ideas what could be causing these MMS agent errors?

Automation Agent errors

mongodb411/23/14 - 12:28:01error
Error sending status to MMS: [12:28:01.928] Error sending status to MMS: Error POSTing to https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64: Post https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64: net/http: TLS handshake timeout
mongodb411/23/14 - 12:28:01error
Error sending status to MMS: Error POSTing to https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64: Post https://mms.mongodb.com/agents/api/automation/status/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64: net/http: TLS handshake timeout
mongodb211/23/14 - 12:21:08error
Error loading desired cluster configs : [12:21:08.770] Error retrieving cluster config from 'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb2&ahs=mongodb2&av=1.3.2.739&aos=linux&aa=x86_64&ab=64' : Get https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb2&ahs=mongodb2&av=1.3.2.739&aos=linux&aa=x86_64&ab=64: net/http: TLS handshake timeout
mongodb211/23/14 - 12:21:08error
Error retrieving cluster config from 'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb2&ahs=mongodb2&av=1.3.2.739&aos=linux&aa=x86_64&ab=64' : Get https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb2&ahs=mongodb2&av=1.3.2.739&aos=linux&aa=x86_64&ab=64: net/http: TLS handshake timeout
mongodb511/23/14 - 12:20:18error
Error loading desired cluster configs : [12:20:18.128] 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: net/http: TLS handshake timeout
mongodb511/23/14 - 12:20:18error
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: net/http: TLS handshake timeout
mongodb411/23/14 - 12:19:55error
Error loading desired cluster configs : [12:19:55.476] Error retrieving cluster config from 'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64' : Get https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64: read tcp 75.101.156.249:443: connection reset by peer
mongodb411/23/14 - 12:19:55error
Error retrieving cluster config from 'https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64' : Get https://mms.mongodb.com/agents/api/automation/conf/v1/546782e6e4b0cb71bc2d3391?ah=mongodb4&ahs=mongodb4&av=1.3.2.739&aos=linux&aa=x86_64&ab=64: read tcp 75.101.156.249:443: connection reset by peer
mongodb111/23/14 - 11:57:44errorMC1_mongos_100Assuming CanSSL is false because there was an error getting CanSSL : <MC1_mongos_100> [11:57:44.530] Error checking if (mongodb2:27017) permits progress : <MC1_mongos_100> [11:57:44.530] Error getting version of mongodb1:27017: <MC1_mongos_100> [11:57:44.530] Could not get version : Session is nil.
mongodb111/23/14 - 11:57:44errorMC1_mongos_100Error checking if (mongodb2:27017) permits progress : <MC1_mongos_100> [11:57:44.530] Error getting version of mongodb1:27017: <MC1_mongos_100> [11:57:44.530] Could not get version : Session is nil.
mongodb111/23/14 - 11:57:44errorMC1_mongos_100Error getting version of mongodb1:27017: <MC1_mongos_100> [11:57:44.530] Could not get version : Session is nil.
mongodb111/23/14 - 11:57:44errorMC1_mongos_100Could not get version : Session is nil.
mongodb111/23/14 - 11:57:44errorMC1_mongos_100Assuming CanSSL is false because there was an error getting CanSSL : <MC1_mongos_100> [11:57:44.417] Error checking if (mongodb2:27017) permits progress : <MC1_mongos_100> [11:57:44.417] Error getting version of mongodb1:27017: <MC1_mongos_100> [11:57:44.417] Could not get version : Session is nil.
mongodb111/23/14 - 11:57:44errorMC1_mongos_100Error checking if (mongodb2:27017) permits progress : <MC1_mongos_100> [11:57:44.417] Error getting version of mongodb1:27017: <MC1_mongos_100> [11:57:44.417] Could not get version : Session is nil.
mongodb111/23/14 - 11:57:44errorMC1_mongos_100Error getting version of mongodb1:27017: <MC1_mongos_100> [11:57:44.417] Could not get version : Session is nil.
mongodb111/23/14 - 11:57:44errorMC1_mongos_100Could not get version : Session is nil.
mongodb411/23/14 - 11:57:44errorMC1_MS_0_94Assuming CanSSL is false because there was an error getting CanSSL : <MC1_MS_0_94> [11:57:44.036] Error checking if conf server(mongodb3:27019) is healthy and done : <MC1_MS_0_94> [11:57:44.036] Error getting version of mongodb4:27000: <MC1_MS_0_94> [11:57:44.036] Could not get version : Session is nil.
mongodb411/23/14 - 11:57:44errorMC1_MS_0_94Error checking if conf server(mongodb3:27019) is healthy and done : <MC1_MS_0_94> [11:57:44.036] Error getting version of mongodb4:27000: <MC1_MS_0_94> [11:57:44.036] Could not get version : Session is nil.
mongodb411/23/14 - 11:57:44errorMC1_MS_0_94Error getting version of mongodb4:27000: <MC1_MS_0_94> [11:57:44.036] Could not get version : Session is nil.
mongodb411/23/14 - 11:57:44errorMC1_MS_0_94Could not get version : Session is nil.
ubuntu11/23/14 - 11:57:44errorMC1_mongos_102Assuming CanSSL is false because there was an error getting CanSSL : <MC1_mongos_102> [11:57:44.332] Error checking if (mongodb2:27017) is done : <MC1_mongos_102> [11:57:44.332] Error getting version of ubuntu:27017: <MC1_mongos_102> [11:57:44.332] Could not get version : Session is nil.
ubuntu11/23/14 - 11:57:44errorMC1_mongos_102Error checking if (mongodb2:27017) is done : <MC1_mongos_102> [11:57:44.332] Error getting version of ubuntu:27017: <MC1_mongos_102> [11:57:44.332] Could not get version : Session is nil.
ubuntu11/23/14 - 11:57:44errorMC1_mongos_102Error getting version of ubuntu:27017: <MC1_mongos_102> [11:57:44.332] Could not get version : Session is nil.
ubuntu11/23/14 - 11:57:44errorMC1_mongos_102Could not get version : Session is nil.
ubuntu11/23/14 - 11:57:44errorMC1_mongos_102Assuming CanSSL is false because there was an error getting CanSSL : <MC1_mongos_102> [11:57:44.080] Error checking if (mongodb2:27017) is done : <MC1_mongos_102> [11:57:44.080] Error getting version of ubuntu:27017: <MC1_mongos_102> [11:57:44.080] Could not get version : Session is nil.


Monitoring Agent Errors

mongodb411/23/14 - 12:34:48error
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
mongodb411/23/14 - 12:34:48errormongodb3:27019Task failure `localSystemReplSet`. Err: `Query task failed against host `mongodb3:27019` to collection `local.system.replset`. Err: not found at monitoring-agent/components/task.go:329 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`
mongodb411/23/14 - 12:34:48errormongodb4: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`
mongodb411/23/14 - 12:34:48errormongodb4:27019Task failure `localSystemReplSet`. Err: `Query task failed against host `mongodb4:27019` to collection `local.system.replset`. Err: not found at monitoring-agent/components/task.go:329 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`
mongodb411/23/14 - 12:34:48errormongodb4: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`
mongodb411/23/14 - 12:34:48errormongodb3: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`
mongodb411/23/14 - 12:34:48errormongodb3: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`
mongodb411/23/14 - 12:34:48errormongodb5:27019Task failure `replStatus`. Err: `Failed command to mongodb5: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`
mongodb411/23/14 - 12:34:48errormongodb5:27019Task failure `localSystemReplSet`. Err: `Query task failed against host `mongodb5:27019` to collection `local.system.replset`. Err: not found at monitoring-agent/components/task.go:329 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`
mongodb411/23/14 - 12:34:48errormongodb5:27019Task failure `replStatus`. Err: `Failed command to mongodb5: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`
mongodb411/23/14 - 12:33:53error
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
mongodb411/23/14 - 12:33:53errormongodb4:27019Task failure `localSystemReplSet`. Err: `Query task failed against host `mongodb4:27019` to collection `local.system.replset`. Err: not found at monitoring-agent/components/task.go:329 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`
mongodb411/23/14 - 12:33:53errormongodb3: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`
mongodb411/23/14 - 12:33:53errormongodb4: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`
mongodb411/23/14 - 12:33:53errormongodb4: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`
mongodb411/23/14 - 12:33:53errormongodb5:27019Task failure `replStatus`. Err: `Failed command to mongodb5: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`
mongodb411/23/14 - 12:33:53errormongodb3:27019Task failure `localSystemReplSet`. Err: `Query task failed against host `mongodb3:27019` to collection `local.system.replset`. Err: not found at monitoring-agent/components/task.go:329 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`
mongodb411/23/14 - 12:33:53errormongodb5:27019Task failure `localSystemReplSet`. Err: `Query task failed against host `mongodb5:27019` to collection `local.system.replset`. Err: not found at monitoring-agent/components/task.go:329 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`
mongodb411/23/14 - 12:33:53errormongodb3: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`
mongodb411/23/14 - 12:33:53errormongodb5:27019Task failure `replStatus`. Err: `Failed command to mongodb5: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`
mongodb411/23/14 - 12:32:58error
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
mongodb411/23/14 - 12:32:58errormongodb4:27019Task failure `localSystemReplSet`. Err: `Query task failed against host `mongodb4:27019` to collection `local.system.replset`. Err: not found at monitoring-agent/components/task.go:329 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`
mongodb411/23/14 - 12:32:58errormongodb3: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`
mongodb411/23/14 - 12:32:58errormongodb4: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`
mongodb411/23/14 - 12:32:58errormongodb4: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`

Jon Petitta

unread,
Nov 23, 2014, 6:33:37 PM11/23/14
to mongod...@googlegroups.com
I do believe that this is my main issue, this is coming from the monitoring agent.  I've even tried moving the monitoring agent from machine to machine.

Failed to post ping Failure posting ping. Op: Post Err: read tcp 75.101.156.249:443: connection reset by peer

Stephen Steneker

unread,
Nov 24, 2014, 4:47:22 AM11/24/14
to mongod...@googlegroups.com
On Monday, 24 November 2014 10:33:37 UTC+11, Jon Petitta wrote:
I do believe that this is my main issue, this is coming from the monitoring agent.  I've even tried moving the monitoring agent from machine to machine.

Failed to post ping Failure posting ping. Op: Post Err: read tcp 75.101.156.249:443: connection reset by peer

Hi Jon,

Are your VMs able to connect to the outside world? It seems like the configuration is blocking the agent from fetching the configuration from mms.mongodb.com so the set up is incomplete.

How is your VirtualBox networking mode configured -- can you confirm the networking mode (NAT, NAT Network, Bridged, ..) ?

Regards,
Stephen

Jon Petitta

unread,
Nov 24, 2014, 10:57:39 AM11/24/14
to mongod...@googlegroups.com
Each vm can contact the outside world, they can even ping mms.mongodb.com and www.google.com

They are configured with Nat Network, each vm can ping each other via hostname.

The agents/mongodb services deploy and download just fine, it's after that when the issue arises.

Jon Petitta

unread,
Nov 25, 2014, 8:26:14 AM11/25/14
to mongod...@googlegroups.com
Do the guys that wrote MMS hangout in here?

Peter Gravelle

unread,
Nov 25, 2014, 10:23:51 AM11/25/14
to mongod...@googlegroups.com
Hi Jon,

I'm the Technical Account Manager for MMS, and I'll file a proactive ticket for you shortly as the next few steps involve identifying information I do not want to put in a public post. Thanks for your patience.

Regards,
-Peter

Jon Petitta

unread,
Nov 25, 2014, 12:18:34 PM11/25/14
to mongod...@googlegroups.com
Thank you very much!

I've been wracking my brains with MMS for the past week!

There are also issues when you attempt to create a deployment using 2.8, well at least for a cluster config that is, the wizard will not go past selecting your nodes.

Jon Petitta

unread,
Nov 25, 2014, 3:27:39 PM11/25/14
to mongod...@googlegroups.com
Got it resolved!

Thought I'd post an update just in case someone ever needs this info.

The problem turned out to be caused by VirtualBox and the use of NatNetwork, which is apparently buggy.

For a proper setup I recommend the following, or you could just use bridged.

Each VM is configured three network cards as follows.
Nat - To talk to MMS and the outside world (only good for outgoing)
Internal - So the vms can talk to each other
Host-Only - So you can connect with client apps from host for testing

Philippe Courtois

unread,
May 29, 2015, 10:22:47 AM5/29/15
to mongod...@googlegroups.com
HI,

I'm getting the same issue when trying to update the automation agents
from 2.0.4.1140 to 2.0.5.1143

Previous updates worked fine

We did not changed anything

If I try to upload the files manually from the servers it works, why
can't MMS do it too

Thank you for your help

Regards

--
Philippe Courtois
Administrateur de bases de données Sr./Sr. Database administrator
CBC/Société Radio Canada
philippe...@radio-canada.ca
Work: (514) 597-6447
Cell: (514) 776-9141

Dwayne Mcnab

unread,
May 29, 2015, 1:30:02 PM5/29/15
to mongod...@googlegroups.com
Make sure that the mongod or mongodb user has ownership to write to the directory /opt/mongodb-mms-automation/versions. By default this is where mms stores its version files. In the past i had the same issues until i resolved this.

Regards,
Message has been deleted

Oleg Semykin

unread,
Jun 30, 2015, 7:09:14 PM6/30/15
to mongod...@googlegroups.com
I ran into the same issue with brand new MMS cluster deployment.

mongo-0,mongo-1,mongo-2 - data server with 2 mongod's and 1 mongoc instances each.
20019 - is mongod configuration servers.
I have no idea why monitoring agent tries to get replica set status against them....


Monitoring log is flooded by the following messages:
[2015/06/30 15:07:59] [monitoring.worker.blocking-mongo-1:27019.error] [monitoring-agent/components/worker.go:158] Task failure `replStatus`. Err: `Failed command to
 mongo-1:27019 running [{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
        at monitoring-agent/components/task.go:297
        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`
[2015/06/30 15:07:59] [monitoring.worker.blocking-mongo-1:27019.error] [monitoring-agent/components/worker.go:158] Task failure `localSystemReplSet`. Err: `Query tas
k failed against host `mongo-1:27019` to collection `local.system.replset`. Err: not found
        at monitoring-agent/components/task.go:354
        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`
[2015/06/30 15:08:00] [monitoring.worker.nonblocking-mongo-0:27019.error] [monitoring-agent/components/worker.go:158] Task failure `replStatus`. Err: `Failed command
 to mongo-0:27019 running [{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
        at monitoring-agent/components/task.go:297
        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`
[2015/06/30 15:08:00] [monitoring.worker.nonblocking-mongo-1:27019.error] [monitoring-agent/components/worker.go:158] Task failure `replStatus`. Err: `Failed command
 to mongo-1:27019 running [{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
        at monitoring-agent/components/task.go:297
        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`
[2015/06/30 15:08:02] [monitoring.worker.nonblocking-mongo-2:27019.error] [monitoring-agent/components/worker.go:158] Task failure `replStatus`. Err: `Failed command
 to mongo-2:27019 running [{replSetGetStatus 1}] against DB admin. Err: `not running with --replSet`
        at monitoring-agent/components/task.go:297
        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`
[2015/06/30 15:08:03] [monitoring.info] [monitoring-agent/components/agent.go:347] Posting final ping payload containing 9/9 hosts
[2015/06/30 15:08:03] [monitoring.info] [monitoring-agent/components/agent.go:391] Done. Sleeping for 51s...


Please advise how to fix it.

Oleg Semykin

unread,
Jul 5, 2015, 6:23:07 AM7/5/15
to mongod...@googlegroups.com
Any ideas how to fix?
Monitoring Agent is still trying to fetch replSetGetStatus from config servers on 27019 port.
Is that configuration or app error?

Philippe Courtois

unread,
Jul 31, 2015, 10:55:11 AM7/31/15
to mongodb-user, dwayn...@gmail.com
All the directories are own by the mongodb user and I still have the same issue

Regards

PC

Jeff Dupont

unread,
Aug 4, 2015, 2:41:47 PM8/4/15
to mongodb-user
I'm running the same network configuration, so what was the solution?

Dwayne Mcnab

unread,
Aug 4, 2015, 3:28:23 PM8/4/15
to mongod...@googlegroups.com
Here's my dump question. How did you add you cluster to mms? Did you use the mongos server? If you did and all your configuration file options are correct, assuming that you are using a config file if not make sure that all your config options are correct on the command line. If all is A OK then mongo will automagically discover all the members of the cluster. I've had not the same issue but rather mms was showing incorrect information and i had to remove the instance from mms and re-add them to solve the issue. make sure that you are also not using IP's or localhost as the hostname as mms will go crazy. 

On Tue, Aug 4, 2015 at 11:31 AM, Jeff Dupont <jeff....@gmail.com> wrote:
I'm running the same network configuration, so what was the solution?

--
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 a topic in the Google Groups "mongodb-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mongodb-user/a6F03kGl19g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mongodb-user...@googlegroups.com.
To post to this group, send email to mongod...@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/58b6bcec-1ead-4fda-a083-ec335e48611b%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Oleg Semykin

unread,
Aug 11, 2015, 11:11:05 AM8/11/15
to mongodb-user
I've submitted JIRA bug against MSS and posted the original question.
Mongo reps fixed something in my account and it started to work correctly, without errors.

Liz Hall

unread,
May 8, 2017, 1:08:18 PM5/8/17
to mongodb-user
I was missing this directory.  Once added, error cleared.

/var/log/mongodb

be sure its owned by  your mongo user.
Reply all
Reply to author
Forward
0 new messages