Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Who agreed with this topic

HTTP Error 500 when accessing CM

Explorer

Host had a hard reboot and now am getting an HTTP Error 500 when trying to access Cloudera Manager. The service was dead but the pid still existed, so I deleted the pid file and restarted the service - which shows as running, but still getting the HTTP error 500. Any ideas on what to check?

 

Problem accessing /cmf/login. Reason:

Error creating bean with name 'newServiceHandlerRegistry' defined in class path resource [com/cloudera/server/cmf/config/components/BeanConfiguration.class]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public com.cloudera.cmf.service.ServiceHandlerRegistry com.cloudera.server.cmf.config.components.BeanConfiguration.newServiceHandlerRegistry()] threw exception; nested exception is java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
Who agreed with this topic