Cloudera Community

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Who agreed with this topic

HTTP Error 500 when accessing CM

Labels:
avatar
author-rank Braundmeier
Explorer

Created on ‎06-13-2016 02:38 PM - edited ‎09-16-2022 03:24 AM

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
19,550
0 Kudos
1
Who agreed with this topic