Error When Starting New Instance of Datameer

Problem

Following a clean installation, the Datameer server fails to start. The following "Caused by" is logged in the conductor.log file when Datameer is attempting to start.


{

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'virtualFilesystem': Unsatisfied dependency expressed through field '_eventLogger'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'eventLogger' defined in URL [jar:file:/app/datameer/Datameer-7.1.6-mapr-5.2.0/webapps/conductor/WEB-INF/lib/dap-conductor-7.1.6.jar!/datameer/dap/conductor/metrics/EventLogger.class]: Unsatisfied dependency expressed through constructor parameter 3; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'java.lang.Integer' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Qualifier(value=eventlog.number-of-async-threads)

}

 

Cause

This issue occurs when customizations have been made to "cacert" concerning SSL configuration of Jetty.  

In some cases, configuration files might have been copied directly between installations. This can also lead to missing parameters or improper configuration settings being applied.

 

Solution

To resolve this issue, begin by stopping Datameer and restoring the stock "cacert" file. Ensure that Datameer will boot with the stock options in place.

Once you are able to boot, please review the following documentation to ensure you have completed all of the steps:

https://documentation.datameer.com/documentation/display/DAS70/Import+Custom+SSL+Certificates