Unable to start Ops Manager mongodb-mms on Amazon Linux

630 views
Skip to first unread message

Alan Stott

unread,
Nov 5, 2016, 2:00:03 AM11/5/16
to mongodb-user

If anyone can point us in the direction would be appreciated. Trying to evaluate Ops Manager for our start-up.

Running a replica set using Mongo 3.2 on Amazon Linux.

[ec2-user@ip-10-0-0-26 init.d]$ sudo service mongodb-mms start

Starting pre-flight checks

An unexpected error occurred during pre-flight checks: Unable to provision, see the following errors:


1) Error injecting constructor, java.net.UnknownHostException: ip-10-0-0-26: ip-10-0-0-26: Name or service not known

  at com.xgen.svc.core.AppSettings.<init>(AppSettings.java:125)

  at com.xgen.svc.core.AppSettings.class(AppSettings.java:45)

  while locating com.xgen.svc.core.AppSettings

    for parameter 0 at com.xgen.svc.core.dao.mongo.MongoSvcProvider.<init>(MongoSvcProvider.java:23)

  at com.xgen.svc.core.dao.mongo.MongoSvcProvider.class(MongoSvcProvider.java:19)

  while locating com.xgen.svc.core.dao.mongo.MongoSvcProvider

  while locating com.xgen.svc.core.dao.mongo.MongoSvc


1 error

com.google.inject.ProvisionException: Unable to provision, see the following errors:


1) Error injecting constructor, java.net.UnknownHostException: ip-10-0-0-26: ip-10-0-0-26: Name or service not known

  at com.xgen.svc.core.AppSettings.<init>(AppSettings.java:125)

  at com.xgen.svc.core.AppSettings.class(AppSettings.java:45)

  while locating com.xgen.svc.core.AppSettings

    for parameter 0 at com.xgen.svc.core.dao.mongo.MongoSvcProvider.<init>(MongoSvcProvider.java:23)

  at com.xgen.svc.core.dao.mongo.MongoSvcProvider.class(MongoSvcProvider.java:19)

  while locating com.xgen.svc.core.dao.mongo.MongoSvcProvider

  while locating com.xgen.svc.core.dao.mongo.MongoSvc


1 error

at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1025)

at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)

at com.mycila.inject.jsr250.Jsr250InjectorImpl.getInstance(Jsr250InjectorImpl.java:123)

at com.xgen.svc.core.PreFlightCheck.performChecks(PreFlightCheck.java:90)

at com.xgen.svc.core.PreFlightCheck.main(PreFlightCheck.java:150)

Caused by: java.net.UnknownHostException: ip-10-0-0-26: ip-10-0-0-26: Name or service not known

at java.net.InetAddress.getLocalHost(InetAddress.java:1505)

at com.xgen.svc.core.util.SystemUtils.getHostname(SystemUtils.java:16)

at com.xgen.svc.core.AppSettings.recordInstanceOverrides(AppSettings.java:366)

at com.xgen.svc.core.AppSettings.<init>(AppSettings.java:170)

at com.xgen.svc.core.AppSettings.<init>(AppSettings.java:125)

at com.xgen.svc.core.AppSettings$$FastClassByGuice$$577b2d6c.newInstance(<generated>)

at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)

at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)

at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)

at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)

at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267)

at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)

at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)

at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)

at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)

at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)

at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38)

at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62)

at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:104)

at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)

at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267)

at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)

at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)

at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)

at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)

at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)

at com.google.inject.internal.BoundProviderFactory.get(BoundProviderFactory.java:61)

at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)

at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)

at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)

... 4 more

Caused by: java.net.UnknownHostException: ip-10-0-0-26: Name or service not known

at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)

at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)

at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)

at java.net.InetAddress.getLocalHost(InetAddress.java:1500)

... 33 more



Basic config pointing to hostnames which map to each ec2 instance in different availability zones.

#

# Ops Manager Configuration File

#


# #####################################

# Ops Manager MongoDB storage settings

#

# The following MongoURI parameters are for configuring the MongoDB storage

# that backs the Ops Manager server's functionality. By default. the Ops Manager server is

# configured to expect a local standalone instance of MongoDB running on

# the default port 27017.

#

# For more advanced configurations of the backing MongoDB store, such as

# running with replication or authentication, please refer to the

# documentation at http://mms.mongodb.com/help-hosted.

# ####################################

mongo.mongoUri=mongodb://mongoZoneA,mongoZoneB,mongoZoneC

mongo.ssl=false


# #####################################

# MongoDB SSL Settings (Optional)

#

# The following parameters are for configuring the SSL certificates to be

# used by the Ops Manager server to connect to its MongoDB backing stores. These

# settings are only applied to the mongoUri connection above when

# `mongo.ssl` is set to true.

# CAFile - the certificate of the CA that issued the MongoDB server certificate(s)

# PEMKeyFile - a client certificate containing a certificate and private key

#             (needed when MongoDB is running with --sslCAFile)

# PEMKeyFilePassword - required if the `PEMKeyFile` contains an encrypted private key

# ####################################

mongodb.ssl.CAFile=

mongodb.ssl.PEMKeyFile=

mongodb.ssl.PEMKeyFilePassword=


# #####################################

# Kerberos Module (Optional)

#

# The following parameters are for configuring Ops Manager to use Kerberos to connection

# to its MongoDB backing stores.

#

# jvm.java.security.krb5.kdc: This should be the IP/FQDN of the KDC server. The value will be set to JVM's

# java.security.krb5.kdc.

#

# jvm.java.security.krb5.realm: This is the default REALM for Kerberos. It is being used for JVM's

# java.security.krb5.realm.

#

# mms.kerberos.principal: The principal we used to authenticate with MongoDB. This should be the exact same user

# on the mongoUri above.

#

# mms.kerberos.keyTab: The absolute path to the keytab file for the principal.

#

# mms.kerberos.debug: The debug flag to output more information on Kerberos authentication process.

#

# Please note, all the parameters are required for Kerberos authentication, except mms.kerberos.debug. The mechanism

# will not be functioning if any of the setting value is missing.

#

# Assume your kdc server FQDN is kdc.example.com, your Kerberos default realm is: EXAMPLE.COM,

# the host running Ops Manager is mmsweb.example.com, the Kerberos for Ops Manager is mms/mmsweb.ex...@EXAMPLE.com,

# And you have a keytab file for mms/mmsweb.ex...@EXAMPLE.COM located at /path/to/mms.keytab, then the

# configurations would be:

#       jvm.java.security.krb5.kdc=kdc.example.com

#       jvm.java.security.krb5.realm=EXAMPLE.COM

#       mms.kerberos.principal=mms/mmsweb.ex...@EXAMPLE.COM

#       mms.kerberos.keyTab=/path/to/mms.keytab

#       mms.kerberos.debug=false

#

# ####################################

jvm.java.security.krb5.kdc=

jvm.java.security.krb5.realm=

mms.kerberos.principal=

mms.kerberos.keyTab=

mms.kerberos.debug=


# #####################################

# Instance Parameter Overrides

#

# In this section include any parameters to be used on this instance

# of Ops Manager. These parameters will override any global configuration

# stored in the Ops Manager database.

#

# See https://docs.opsmanager.mongodb.com/current/reference/configuration/

# for additional information

#

# #####################################


Wan Bachtiar

unread,
Nov 9, 2016, 1:17:50 AM11/9/16
to mongodb-user

Error injecting constructor, java.net.UnknownHostException: ip-10-0-0-26: ip-10-0-0-26: Name or service not known

Hi Alan,

Based on the error line, it seems that there's an issue with your DNS setup on your VPC. Make sure that ip-10-0-0-26 is a resolvable hostname. Check that your instances' network configuration has been setup properly. You may find the Amazon VPC DHCP options useful.

Trying to evaluate Ops Manager for our start-up.

As you may already know OpsManager Application is part of the MongoDB Enterprise edition, which is a commercially supported product.

If your company/organisation already has a commercial subscription and you have further questions about running OpsManager, you should open a private case in the Commercial Support Portal.

Alternatively if you are evaluating MongoDB Enterprise and interested, send me a private message with your contact details and I can request a MongoDB Account Executive to contact you.

Regards,

Wan.

Reply all
Reply to author
Forward
0 new messages