Created 01-18-2018 10:53 PM
Hello,
after Update to 5.12.2 I can't check for new remote parcels.
These message are in cloudera-scm-server.log:
2018-01-19 07:28:21,430 INFO ParcelUpdateService:com.cloudera.parcel.components.LocalParcelManagerImpl: Found files KAFKA-3.0.0-1.3.0.0.p0.40-el6.parcel,CDH-5.11.1-1.cdh5.11.1.p0.4-el6.parcel,CDH-5.12.2-1.cdh5.12.2.p0.4-el6.parcel,SPARK2-2.2.0.cloudera1-1.cdh5.12.0.p0.142354-el6.parcel under /opt/cloudera/parcel-repo
2018-01-19 07:28:22,743 ERROR ParcelUpdateService:com.cloudera.parcel.components.ParcelDownloaderImpl: (1 skipped) Unable to retrieve remote parcel repository manifest
java.io.EOFException: No content to map to Object due to end of input
at org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2444)
at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2396)
at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1602)
at com.cloudera.parcel.components.ParcelDownloaderImpl.getRepoInfoFromFuture(ParcelDownloaderImpl.java:545)
at com.cloudera.parcel.components.ParcelDownloaderImpl.getRepositoryInfo(ParcelDownloaderImpl.java:517)
at com.cloudera.parcel.components.ParcelDownloaderImpl.syncRemoteRepos(ParcelDownloaderImpl.java:346)
at com.cloudera.parcel.components.ParcelDownloaderImpl$1.run(ParcelDownloaderImpl.java:438)
at com.cloudera.parcel.components.ParcelDownloaderImpl$1.run(ParcelDownloaderImpl.java:433)
at com.cloudera.cmf.persist.ReadWriteDatabaseTaskCallable.call(ReadWriteDatabaseTaskCallable.java:36)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
We use a proxy in our environment (configured via administration -> settings..). I can access alle the remote parcels URLs via console an curl / wget / w3m from the server.
this problem seems to be known but all the solutions does not change anythin.
Best Regards,
Oliver
Created 01-26-2018 01:01 AM
the solution was: remove all of the repositories from CM and restart the cloudera-server-manager. the default repos are set at the start if no repos are present.
Created 01-19-2018 03:11 AM
one more information: parcels download via proxy (for example spark) in cloudera manager works fine so there is no system wide problem.
Created 01-26-2018 01:01 AM
the solution was: remove all of the repositories from CM and restart the cloudera-server-manager. the default repos are set at the start if no repos are present.