Created on 03-06-2018 11:39 AM - edited 03-06-2018 12:00 PM
I am doing a manual install, I was able to add yum repo to install Cloudera Manager (CM), but when I try to start it, it show that it started successfully, but the logs show that it fails to fetch the Parcels from external repo. (logs below)
The nodes are on a VPC (in AWS) and yum is configured to use a proxy, but evidently the proxy setting in /etc/yum.conf is ignored. (which is understandable because that is probably used by yum command line and not the Java process.)
So here is my question, is there a way to instruct the CM Server to use a proxy to fetch the parcels? I tried setting HTTP_PROXY and HTTPS_PROXY env variable, but no luck. I am trying to avoid setting up a local repository.
Thank you and here is exception from logs: (this happens for all the parcels it tries to fetch, such as CDH, Kafka, Spark, etc... I only included the log for Sqoop)
2018-03-06 19:04:47,221 ERROR ParcelUpdateService:com.cloudera.parcel.components.ParcelDownloaderImpl: Error while attempting to retrieve repository info for repo https://archive.cloudera.com/sqoop-connectors/parcels/latest/ java.io.IOException: Closed at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.doConnect(NettyAsyncHttpProvider.java:873) at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.execute(NettyAsyncHttpProvider.java:858) at com.ning.http.client.AsyncHttpClient.executeRequest(AsyncHttpClient.java:512) at com.ning.http.client.AsyncHttpClient$BoundRequestBuilder.execute(AsyncHttpClient.java:234) at com.cloudera.parcel.components.ParcelDownloaderImpl.getRepositoryInfoFuture(ParcelDownloaderImpl.java:579) at com.cloudera.parcel.components.ParcelDownloaderImpl.getRepositoryInfo(ParcelDownloaderImpl.java:532) at com.cloudera.parcel.components.ParcelDownloaderImpl.syncRemoteRepos(ParcelDownloaderImpl.java:346) at com.cloudera.parcel.components.ParcelDownloaderImpl$1.run(ParcelDownloaderImpl.java:453) at com.cloudera.parcel.components.ParcelDownloaderImpl$1.run(ParcelDownloaderImpl.java:448) at com.cloudera.cmf.persist.ReadWriteDatabaseTaskCallable.call(ReadWriteDatabaseTaskCallable.java:36) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
Created 03-06-2018 12:15 PM
The issue is resolved. The exceptions were misleading; the real issue was this:
Exception in thread "MainThread" java.lang.IllegalArgumentException: Invalid value set for db.setupType, the valid values are EMBEDDED or EXTERNAL
I changed the default value for com.cloudera.cmf.db.sertupType in /etc/cloudera-scm-server/db.properties to EXTERNAL. It was set to INIT.
Created 03-06-2018 12:15 PM
The issue is resolved. The exceptions were misleading; the real issue was this:
Exception in thread "MainThread" java.lang.IllegalArgumentException: Invalid value set for db.setupType, the valid values are EMBEDDED or EXTERNAL
I changed the default value for com.cloudera.cmf.db.sertupType in /etc/cloudera-scm-server/db.properties to EXTERNAL. It was set to INIT.