0

I am using Cloudera-manager version 5. Today, I restarted it and it took 1 hour to complete. This is my log.

2023-02-07 02:20:53,912 INFO ScmActive-0:com.cloudera.server.cmf.components.ScmActive: ScmActive completed successfully.
2023-02-07 02:20:56,880 INFO MainThread:com.cloudera.server.cmf.jython.components.JythonObjectFactoryImpl: Finished constructing Jython object factory
2023-02-07 02:20:56,970 INFO MainThread:com.cloudera.server.cmf.Main: Server locale set to: en
2023-02-07 02:20:56,995 INFO MainThread:com.cloudera.server.cmf.components.EmbeddedDbManager: CM server is NOT using embedded postgresql database for itself.
2023-02-07 02:20:57,011 INFO MainThread:com.cloudera.cmf.service.CommandScheduleListener: Adding command schedule listener for global-collect-host-statistics
2023-02-07 02:20:57,024 INFO MainThread:com.cloudera.cmf.service.CommandScheduleListener: Initializing schedule for global-collect-host-statistics
2023-02-07 02:20:57,045 INFO MainThread:com.cloudera.cmf.service.CommandScheduleListener: Replacing existing schedule for global-collect-host-statistics
2023-02-07 02:20:57,093 INFO MainThread:com.cloudera.cmf.service.CommandScheduleListener: Removed schedule DbCommandSchedule{id=71, commandName=global-collect-host-statistics, displayName=null, description=null}
2023-02-07 02:20:57,097 INFO MainThread:com.cloudera.cmf.service.CommandScheduleListener: Adding schedule - DbCommandSchedule{id=72, commandName=global-collect-host-statistics, displayName=null, description=null}
2023-02-07 02:50:55,264 INFO ScmActive-0:com.cloudera.server.cmf.components.ScmActive: (119 skipped) ScmActive completed successfully.
2023-02-07 03:19:36,262 INFO JmxPeriodicLogging-0:com.cloudera.enterprise.PeriodicJmx: JMX: ... <Very many characters.>
2023-02-07 03:20:38,635 INFO ParcelUpdateService:com.cloudera.parcel.components.LocalParcelManagerImpl: Found files CDH-5.14.4-1.cdh5.14.4.p0.3-el7.parcel,SPARK2-2.4.0.cloudera2-1.cdh5.13.3.p0.1041012-el6.parcel,SPARK2-2.4.0
.cloudera2-1.cdh5.13.3.p0.1041012-el7.parcel,SPARK2-2.2.0.cloudera1-1.cdh5.12.0.p0.142354-el7.parcel,SPARK2-2.1.0.cloudera3-1.cdh5.13.3.p0.569822-el6.parcel,SPARK2-2.1.0.cloudera3-1.cdh5.13.3.p0.569822-el7.parcel,KAFKA-3.1.0
-1.3.1.0.p0.35-el6.parcel,STREAMSETS_DATACOLLECTOR-3.4.1-el7.parcel,KAFKA-3.1.0-1.3.1.0.p0.35-el7.parcel,CDH-5.14.4-1.cdh5.14.4.p0.3-el6.parcel,SPARK2-2.2.0.cloudera1-1.cdh5.12.0.p0.142354-el6.parcel,KUDU-1.1.0-1.kudu1.1.0.p
0.5-el6.parcel,STREAMSETS_DATACOLLECTOR-3.4.1-el6.parcel under /opt/cloudera/parcel-repo
2023-02-07 03:20:38,829 ERROR ParcelUpdateService:com.cloudera.parcel.components.ParcelDownloaderImpl: (10 skipped) Unable to retrieve remote parcel repository manifest
java.util.concurrent.ExecutionException: java.net.ConnectException: Received fatal alert: protocol_version to https://archive.cloudera.com/cdh5/parcels/5.14/manifest.json
    <Very many characters.>
Caused by: java.net.ConnectException: Received fatal alert: protocol_version to https://archive.cloudera.com/cdh5/parcels/5.14/manifest.json
    at com.ning.http.client.providers.netty.NettyConnectListener.operationComplete(NettyConnectListener.java:100)
    ... 22 more
Caused by: javax.net.ssl.SSLException: Received fatal alert: protocol_version
    <Very many characters.>
    ... 3 more
2023-02-07 03:20:40,623 ERROR ParcelUpdateService:com.cloudera.parcel.components.ParcelDownloaderImpl: Failed to download manifest. Status code: 404 URI: http://archive.cloudera.com/spark2/parcels/2.4.0.cloudera2/manifest.js
on/
2023-02-07 03:20:41,515 INFO ParcelUpdateService:com.cloudera.parcel.components.ParcelDownloaderImpl: (14 skipped) Parcel DbParcel{id=416, filename=SPARK2-2.1.0.cloudera3-1.cdh5.13.3.p0.569822-trusty.parcel} no longer exists
 on source repo but still in use.
2023-02-07 03:20:56,259 INFO ScmActive-0:com.cloudera.server.cmf.components.ScmActive: (119 skipped) ScmActive completed successfully.
2023-02-07 03:50:31,616 INFO MainThread:com.cloudera.cmf.scheduler.CmfScheduler: Added command schedule '72' to the scheduler
2023-02-07 03:50:31,701 INFO MainThread:com.cloudera.server.cmf.Main: Starting Auto Upgrade
2023-02-07 03:50:31,706 INFO MainThread:com.cloudera.cmf.service.upgrade.AutoUpgradeHandlerRegistry: No Auto Upgrades required.
2023-02-07 03:50:31,706 INFO MainThread:com.cloudera.server.cmf.Main: Successfully completed Auto Upgrade
2023-02-07 03:50:31,866 INFO MainThread:com.cloudera.server.cmf.Main: Agent RPC connections will use port: 7182
2023-02-07 03:50:31,872 INFO MainThread:com.cloudera.server.common.HttpConnectorServer: Max heartbeat processing thread: 12 and Max threads for CM agent avro http connector: 200
2023-02-07 03:50:32,016 INFO MainThread:org.mortbay.log: jetty-6.1.26.cloudera.4
2023-02-07 03:50:32,086 INFO MainThread:org.mortbay.log: Started SelectChannelConnector@0.0.0.0:7182
2023-02-07 03:50:32,086 INFO MainThread:com.cloudera.server.cmf.Main: Started Agent RPC server.
2023-02-07 03:50:32,091 INFO MainThread:org.quartz.core.QuartzScheduler: JobFactory set to: com.cloudera.cmf.scheduler.CmfJobFactory@fcd2bb5
2023-02-07 03:50:32,091 INFO MainThread:org.quartz.core.QuartzScheduler: Scheduler com.cloudera.cmf.scheduler-1_$_NON_CLUSTERED started.
2023-02-07 03:50:32,156 INFO com.cloudera.cmf.scheduler-1_Worker-1:com.cloudera.cmf.service.ServiceHandlerRegistry: Executing command GlobalPoolsRefresh BasicCmdArgs{scheduleId=1, scheduledTime=2023-02-06T17:00:00.000Z}.
2023-02-07 03:50:32,224 INFO MainThread:com.cloudera.server.cmf.WebServerImpl: Using webapp:/usr/share/cmf/webapp
2023-02-07 03:50:32,420 INFO MainThread:com.cloudera.server.cmf.WebServerImpl: Plaintext web connections will use port: 7180


What do I need to do to resolve this error? Thank you all.

Currently, my Cloudera-manager is still in use for the service, so it is not frequently restarted to check the error details.

Viet
  • 1

0 Answers0