Support Questions

Find answers, ask questions, and share your expertise

Failing to start the Cloudera Server with compatibilty issue.

New Contributor

Hi,

 

We have downgraded the CDH version from 6.3.0 to 5.15. While starting cloudera-scm-server we are seeing below exception in the server log. Can anyone help on this issue?

 

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'dssdToggleListener.PostCommit' defined in URL [jar:file:/usr/share/cmf/common_jars/server-5.15.1.jar!/com/cloudera/cmf/service/dssd/components/DssdToggleListener$PostCommit.class]: Unsatisfied dependency expressed through constructor argument with index 2 of type [com.cloudera.server.cmf.descriptor.components.DescriptorFactory]: : Error creating bean with name 'monitoringTypesInitializer': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Range [CDH 4.0.0‥CDH 6.0.0) does not enclose compatibility range [CDH 6.3.0‥CDH 7.0.0); nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'monitoringTypesInitializer': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Range [CDH 4.0.0‥CDH 6.0.0) does not enclose compatibility range [CDH 6.3.0‥CDH 7.0.0)
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:730)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1003)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:907)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:105)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)

 

 

 

 

4 REPLIES 4

Super Collaborator

Hi @Rahul20 ,

 

Only upgrade rollback from C6 to C5 is tested and documented. I assume you have upgraded from CDH5.15 to CDH6.3 and then decided to rollback? If so, did you follow this doc to do the downgrade?

https://docs.cloudera.com/documentation/enterprise/upgrade/topics/install_rollback.html#concept_vpl_...

What is your current CM version?

 

Thanks!

Li Wang, Technical Solution Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:

Terms of Service

Community Guidelines

How to use the forum

New Contributor

Hi,

 

Thanks for the reply.

 

The machine was installed with CDH6.3 and then we decided to downgrade it to CDH5.15.

 

We have verified it was showing CDH as 5.15 after the downgrade. But still, we face the issue while bringing up the Cloudera Manager.

 

Thanks and Regards,

Rahul Kumar Pamidi.

 

 

Cloudera Employee
Can we confirm a detail. The DSSD service is related to using EMC DSSD based storage on the data nodes. Are you using DSSD mode in Cloudera Manager?

Cloudera Employee

Hi @Rahul20 ,

 

Before upgrading to CDH 6.3.0 did you took the back up  of CM 6.3/CDH 5.15 database and data directories) properly? And after downgrade to CDH 5.15 and before starting CM server did you properly restored backup? If not then CM won't start correctly.

 

Thanks,
Salim