./mongodb-mms start
Starting pre-flight checks
Successfully finished pre-flight checks
Migrate Ops Manager data
Running migrations...[ OK ]
Start Ops Manager server
Instance 0 starting.....[FAILED]
Check /m/db/m/logs/mms0.log for errors
The logfile has the beow errors
2016-07-21T07:40:35.569+0000 [main] ERROR com.xgen.svc.atm.svc.AutomationMongoDbVersionSvc [autoUpdateDefaultVersions:204] - Failed to update MongoDB default versions from `https://opsmanager.mongodb.com/static/version_manifest/2.0.json`
java.lang.IllegalStateException: json: 'null'
at com.xgen.svc.core.util.HttpUtils.doGetJson(HttpUtils.java:624) ~[mms.jar:2.0.5.358]
at com.xgen.svc.core.util.HttpUtils.doGetJson(HttpUtils.java:606) ~[mms.jar:2.0.5.358]
at com.xgen.svc.atm.svc.AutomationMongoDbVersionSvc.autoUpdateDefaultVersions(AutomationMongoDbVersionSvc.java:192) [mms.jar:2.0.5.358]
at com.xgen.svc.atm.svc.AutomationMongoDbVersionSvc.<init>(AutomationMongoDbVersionSvc.java:74) [mms.jar:2.0.5.358]
at com.xgen.svc.mms.MmsPreFlightCheck$AutomationMongoDBVersionCheck.check(MmsPreFlightCheck.java:241) [mms.jar:2.0.5.358]
at com.xgen.svc.core.PreFlightCheck.performCheck(PreFlightCheck.java:117) [mms.jar:2.0.5.358]
at com.xgen.svc.core.PreFlightCheck.performChecks(PreFlightCheck.java:94) [mms.jar:2.0.5.358]
at com.xgen.svc.core.PreFlightCheck.main(PreFlightCheck.java:150) [mms.jar:2.0.5.358]
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to opsmanager.mongodb.com:443 [opsmanager.mongodb.com/54.175.147.155] failed: connect timed out
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:132) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) ~[httpclient-4.3.4.jar:4.3.4]
at com.xgen.svc.core.util.HttpUtils.doGetJson(HttpUtils.java:619) ~[mms.jar:2.0.5.358]
... 7 common frames omitted
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_92]
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[na:1.8.0_92]
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_92]
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_92]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_92]
at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_92]
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:239) ~[httpclient-4.3.4.jar:4.3.4]
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:123) ~[httpclient-4.3.4.jar:4.3.4]
... 17 common frames omitted
Interesting fact is that it works perfectly fine on RHEL 6.3
So I am wondering is there anything we need to do on RHEL7
Any inputs will be valuable
Thanks,
Tanveer
Hi Tanveer,
According to the Ops Manager documentation, there should be no problem installing on RHEL 7.1.
The errors thrown in the log you provided:
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to opsmanager.mongodb.com:443 [opsmanager.mongodb.com/54.175.147.155] failed: connect timed out
followed by:
Caused by: java.net.SocketTimeoutException: connect timed out
Could be an indication of a possible network or firewall issue on this installation of RHEL. Please check with your network and system administrator to ensure that you are able to reach opsmanager.mongodb.com from this host and that the required ports are available.
It is worth noting that the OpsManager Application is part of the MongoDB Enterprise Advanced subscription, which is a commercially supported product. If your company/organisation already has a commercial subscription and you have further questions about running OpsManager, I would suggest that you consider opening a Commercial Support case.
Alternatively, if you are evaluating MongoDB Enterprise and are interested, feel free to send me a private message of your contact details and I can request a MongoDB Account Executive to reach out to you.
Thanks,
Chris