Unable to generate configuration for GATEWAY ba se group

[#1]

The version of CDH5.16.1 I used recently has the following error, which makes it impossible to use the cm management platform to execute some commands, such as distributing the Gateway configuration. I hope to provide some solutions. 2019-11-07 14:00:02,161 ERROR com.cloudera.cmf.scheduler-1_Worker-1:com.cloudera.cmf.service.AbstractRoleHandler: (1 skipped) Unable to generate configuration for GATEWAY ba se group 2019-11-07 14:00:02,161 ERROR com.cloudera.cmf.scheduler-1_Worker-1:com.cloudera.cmf.service.AbstractRoleHandler: Unable to generate configuration for HIVESERVER2: hive-HIVE SERVER2-0f0c09243092e98c6d762d9b05f72d25 2019-11-07 14:00:02,163 ERROR com.cloudera.cmf.scheduler-1_Worker-1:com.cloudera.cmf.scheduler.CommandDispatcherJob: Failed to invoke command (GlobalPoolsRefresh) for schedu le (1) java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException at com.cloudera.cmf.service.AbstractRoleHandler.generateConfigFiles(AbstractRoleHandler.java:968) at com.cloudera.cmf.service.AbstractRoleHandler.generateConfiguration(AbstractRoleHandler.java:902) at com.cloudera.cmf.service.hive.BaseHiveRoleHandler.makeProcess(BaseHiveRoleHandler.java:93) at com.cloudera.cmf.command.GlobalPoolsRefreshCommand$1.apply(GlobalPoolsRefreshCommand.java:104) at com.cloudera.cmf.command.GlobalPoolsRefreshCommand$1.apply(GlobalPoolsRefreshCommand.java:82) at com.cloudera.cmf.cluster.PoolsRefreshCmdWorkCreator.constructRoleRefreshes(PoolsRefreshCmdWorkCreator.java:80) at com.cloudera.cmf.command.GlobalPoolsRefreshCommand.constructWork(GlobalPoolsRefreshCommand.java:123) at com.cloudera.cmf.command.GlobalPoolsRefreshCommand.constructWork(GlobalPoolsRefreshCommand.java:75) at com.cloudera.cmf.command.GlobalPoolsRefreshCommand.constructWork(GlobalPoolsRefreshCommand.java:34) at com.cloudera.cmf.command.CmdWorkCommand.execute(CmdWorkCommand.java:54) at com.cloudera.cmf.service.ServiceHandlerRegistry.executeGlobalCommandHelper(ServiceHandlerRegistry.java:781) at com.cloudera.cmf.service.ServiceHandlerRegistry.executeGlobalCommand(ServiceHandlerRegistry.java:749) at com.cloudera.server.cmf.components.OperationsManagerImpl.executeGlobalCmd(OperationsManagerImpl.java:1752) at com.cloudera.cmf.scheduler.CommandDispatcherJob.dispatchCommand(CommandDispatcherJob.java:248) at com.cloudera.cmf.scheduler.CommandDispatcherJob.executeCommand(CommandDispatcherJob.java:191) at com.cloudera.cmf.scheduler.CommandDispatcherJob.access$500(CommandDispatcherJob.java:61) at com.cloudera.cmf.scheduler.CommandDispatcherJob$1.call(CommandDispatcherJob.java:168) at com.cloudera.cmf.scheduler.CommandDispatcherJob$1.call(CommandDispatcherJob.java:165) at com.cloudera.server.common.RetryWrapper.executeWithRetry(RetryWrapper.java:32) at com.cloudera.server.common.RetryUtils.executeWithRetryHelper(RetryUtils.java:210) at com.cloudera.server.common.RetryUtils.executeWithRetryConstantSleep(RetryUtils.java:73) at com.cloudera.cmf.scheduler.CommandDispatcherJob.execute(CommandDispatcherJob.java:162) at org.quartz.core.JobRunShell.run(JobRunShell.java:206) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:548) Caused by: java.lang.RuntimeException: java.lang.NullPointerException at com.cloudera.cmf.service.AbstractRoleHandler.generateConfigFiles(AbstractRoleHandler.java:968) at com.cloudera.cmf.service.AbstractClientConfigHandler.buildClientConfigFiles(AbstractClientConfigHandler.java:124) at com.cloudera.cmf.service.AbstractClientConfigHandler.buildClientConfigFiles(AbstractClientConfigHandler.java:110) at com.cloudera.cmf.service.components.ConfigHelper.getClientConfigs(ConfigHelper.java:147) at com.cloudera.cmf.service.AbstractRoleHandler.generateClientConfigsForDependencies(AbstractRoleHandler.java:1006) at com.cloudera.cmf.service.AbstractRoleHandler.generateConfigFiles(AbstractRoleHandler.java:952) ... 23 more Caused by: java.lang.NullPointerException at com.cloudera.cmf.service.hadoopcommon.HadoopCommonHelpers.makeJavaOpts(HadoopCommonHelpers.java:242) Thank you.

[#2 · Accepted solution]

The problem has been solved because the yarn service component has a client configuration with no value. There is a warning in the yarn component. After restoring it, hive and yarn can operate normally.