Problem starting monitoring agent with MMS On-prem

[Andrew Gedminas]

Successfully tested MMS in the Cloud.

Now I want to try MMS On-Prem.

Installed MMS On-Prem.

Changed the mmsApiKey and mmsBaseURL in  monitoring-agent.config with the ones provided by the MMS On-Prem service.

Now when I start the agent, I get the following error.

[2014/07/24 14:00:11] [monitoring.error] [monitoring-agent/components/agent.go:314] Failed to fetch Conf

Failure getting conf. Op: Get Err: unsupported protocol scheme ""

        at monitoring-agent/components/conf.go:249

        at monitoring-agent/components/agent.go:312

        at monitoring-agent/components/agent.go:344

        at mongodb.com/monitoring-agent/monitoring-agent.go:160

        at pkg/runtime/proc.c:220

        at pkg/runtime/proc.c:1394

[2014/07/24 14:00:11] [monitoring.info] [monitoring-agent/components/agent.go:349] Done. Sleeping for 27.5s...

[2014/07/24 14:00:14] [monitoring.netappender.error] [monitoring-agent/components/logging.go:193] Error sending bulk log messages

Failure sending log message to MMS. Op: Post Err: unsupported protocol scheme ""

        at monitoring-agent/components/logging.go:124

        at monitoring-agent/components/logging.go:142

        at monitoring-agent/components/logging.go:192

        at monitoring-agent/components/logging.go:213

        at pkg/runtime/proc.c:1394

Help.

[Andrew Gedminas]

Figured out the problem.

After installing MMS On-Prem, I set the mms.centralUrl parameter w/ just the IP address and w/o the hhtp: e.g.(mms.centralUrl=172.20.30.41:8080).

I added the http - mms.centralUrl=http://172.20.30.41:8080 then updated monitoring-agent.config mmsBaseUrl parameter with http and it worked.