[jira] [Comment Edited] (AMBARI-25978) add logsearch support
[ https://issues.apache.org/jira/browse/AMBARI-25978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756330#comment-17756330 ] Robin Zuo edited comment on AMBARI-25978 at 8/19/23 4:20 PM: - Related PR: https://github.com/apache/ambari/pull/3744 was (Author: JIRAUSER292801): Related PR: https://github.com/apache/ambari/pull/3743 > add logsearch support > - > > Key: AMBARI-25978 > URL: https://issues.apache.org/jira/browse/AMBARI-25978 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Assignee: Robin Zuo >Priority: Major > Fix For: 2.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > ambari 2.8.0 does not support logsearch, I'd like to add it in next release > > Related issues: > For ambari-logsearch-portal fail to start, please refer to: > https://issues.apache.org/jira/browse/AMBARI-25992 > For ambari-logsearch-logfeeder fail to start, please refer to: > https://issues.apache.org/jira/browse/AMBARI-25993 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25978) add logsearch support
[ https://issues.apache.org/jira/browse/AMBARI-25978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756330#comment-17756330 ] Robin Zuo commented on AMBARI-25978: Related PR: https://github.com/apache/ambari/pull/3743 > add logsearch support > - > > Key: AMBARI-25978 > URL: https://issues.apache.org/jira/browse/AMBARI-25978 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Assignee: Robin Zuo >Priority: Major > Fix For: 2.9.0 > > > ambari 2.8.0 does not support logsearch, I'd like to add it in next release > > Related issues: > For ambari-logsearch-portal fail to start, please refer to: > https://issues.apache.org/jira/browse/AMBARI-25992 > For ambari-logsearch-logfeeder fail to start, please refer to: > https://issues.apache.org/jira/browse/AMBARI-25993 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25978) add logsearch support
[ https://issues.apache.org/jira/browse/AMBARI-25978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Zuo updated AMBARI-25978: --- Description: ambari 2.8.0 does not support logsearch, I'd like to add it in next release Related issues: For ambari-logsearch-portal fail to start, please refer to: https://issues.apache.org/jira/browse/AMBARI-25992 For ambari-logsearch-logfeeder fail to start, please refer to: https://issues.apache.org/jira/browse/AMBARI-25993 was: ambari 2.8.0 does not support logsearch, I'd like to add it in next release Related issues: For ambari-logsearch-portal fail to start, please refer to: https://issues.apache.org/jira/browse/AMBARI-25992 For ambari-logsearch-logfeeder fail to start, please refer to: https://issues.apache.org/jira/browse/AMBARI-25993 > add logsearch support > - > > Key: AMBARI-25978 > URL: https://issues.apache.org/jira/browse/AMBARI-25978 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Assignee: Robin Zuo >Priority: Major > Fix For: 2.9.0 > > > ambari 2.8.0 does not support logsearch, I'd like to add it in next release > > Related issues: > For ambari-logsearch-portal fail to start, please refer to: > https://issues.apache.org/jira/browse/AMBARI-25992 > For ambari-logsearch-logfeeder fail to start, please refer to: > https://issues.apache.org/jira/browse/AMBARI-25993 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25978) add logsearch support
[ https://issues.apache.org/jira/browse/AMBARI-25978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Zuo updated AMBARI-25978: --- Description: ambari 2.8.0 does not support logsearch, I'd like to add it in next release Related issues: For ambari-logsearch-portal fail to start, please refer to: https://issues.apache.org/jira/browse/AMBARI-25992 For ambari-logsearch-logfeeder fail to start, please refer to: https://issues.apache.org/jira/browse/AMBARI-25993 was:ambari 2.8.0 does not support logsearch, I'd like to add it in next release > add logsearch support > - > > Key: AMBARI-25978 > URL: https://issues.apache.org/jira/browse/AMBARI-25978 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Assignee: Robin Zuo >Priority: Major > Fix For: 2.9.0 > > > ambari 2.8.0 does not support logsearch, I'd like to add it in next release > > Related issues: > For ambari-logsearch-portal fail to start, please refer to: > https://issues.apache.org/jira/browse/AMBARI-25992 > For ambari-logsearch-logfeeder fail to start, please refer to: > https://issues.apache.org/jira/browse/AMBARI-25993 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25992) logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade
[
https://issues.apache.org/jira/browse/AMBARI-25992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25992:
Labels: pull-request-available (was: )
> logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade
>
>
> Key: AMBARI-25992
> URL: https://issues.apache.org/jira/browse/AMBARI-25992
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-logsearch
>Reporter: Robin Zuo
>Assignee: Robin Zuo
>Priority: Major
> Labels: pull-request-available
>
> ambari-logsearch-portal server cannot startup.
> After spring-boot upgrade from 2.0.6.RELEASE to 2.1.5.RELEASE, due to the
> change of class LdapAutoConfiguration, spring need the LdapTemplate bean
> during startup.
> Without the LdapTemplate bean, logsearch-portal server report the following
> error:
> 2023-08-11 06:28:24,471 [main] WARN org.eclipse.jetty.webapp.WebAppContext
> (WebAppContext.java:554) - Failed startup of context
> o.s.b.w.e.j.JettyEmbeddedWebAppContext@6e8fdd19\{application,/,[file:///tmp/jetty-docbase.7488131157696980871.61888/,
>
> jar:file:/usr/lib/ambari-logsearch-portal/libs/swagger-ui-3.19.0.jar!/META-INF/resources],UNAVAILABLE}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'servletEndpointRegistrar' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]:
> Bean instantiation via factory method failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]:
> Factory method 'servletEndpointRegistrar' threw exception; nested exception
> is org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'healthEndpoint' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]:
> Unsatisfied dependency expressed through method 'healthEndpoint' parameter
> 1; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'healthIndicatorRegistry' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/health/HealthIndicatorAutoConfiguration.class]:
> Bean instantiation via factory method failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.springframework.boot.actuate.health.HealthIndicatorRegistry]: Factory
> method 'healthIndicatorRegistry' threw exception; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.springframework.boot.actuate.autoconfigure.ldap.LdapHealthIndicatorAutoConfiguration':
> Unsatisfied dependency expressed through constructor parameter 0; nested
> exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'ldapTemplate' defined in class path resource
> [org/springframework/boot/autoconfigure/ldap/LdapAutoConfiguration.class]:
> Unsatisfied dependency expressed through method 'ldapTemplate' parameter 0;
> nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type 'org.springframework.ldap.core.ContextSource'
> available: expected at least 1 bean which qualifies as autowire candidate.
> Dependency annotations: {}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25993) logsearch-logfeeder cannot startup due to lake of configuration
[ https://issues.apache.org/jira/browse/AMBARI-25993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25993: Labels: pull-request-available (was: ) > logsearch-logfeeder cannot startup due to lake of configuration > --- > > Key: AMBARI-25993 > URL: https://issues.apache.org/jira/browse/AMBARI-25993 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Assignee: Robin Zuo >Priority: Major > Labels: pull-request-available > > logsearch-logfeeder fail to start and report the following error: > 2023-08-19 14:20:40,835 [main] INFO > org.springframework.boot.StartupInfoLogger (StartupInfoLogger.java:50) - > Starting LogFeeder on hadoop-1 with PID 78570 > (/usr/lib/ambari-logsearch-logfeeder/libs/ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar > started by root in /var/lib/ambari-agent) > 2023-08-19 14:20:40,861 [main] INFO > org.springframework.boot.SpringApplication (SpringApplication.java:675) - No > active profile set, falling back to default profiles: default > 2023-08-19 14:20:43,187 [main] ERROR > org.springframework.boot.SpringApplication (SpringApplication.java:858) - > Application run failed > java.lang.IllegalArgumentException: String 'null' cannot be converted to > LogFeederMode enum > at > org.apache.ambari.logfeeder.conf.LogFeederMode.fromString(LogFeederMode.java:48) > ~[ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar:?] > at > org.apache.ambari.logfeeder.conf.condition.NonCloudStorageCondition.matches(NonCloudStorageCondition.java:34) > ~[ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar:?] > at > org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:108) > ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25993) logsearch-logfeeder cannot startup due to lake of configuration
Robin Zuo created AMBARI-25993: -- Summary: logsearch-logfeeder cannot startup due to lake of configuration Key: AMBARI-25993 URL: https://issues.apache.org/jira/browse/AMBARI-25993 Project: Ambari Issue Type: Technical task Components: ambari-logsearch Reporter: Robin Zuo logsearch-logfeeder fail to start and report the following error: 2023-08-19 14:20:40,835 [main] INFO org.springframework.boot.StartupInfoLogger (StartupInfoLogger.java:50) - Starting LogFeeder on hadoop-1 with PID 78570 (/usr/lib/ambari-logsearch-logfeeder/libs/ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar started by root in /var/lib/ambari-agent) 2023-08-19 14:20:40,861 [main] INFO org.springframework.boot.SpringApplication (SpringApplication.java:675) - No active profile set, falling back to default profiles: default 2023-08-19 14:20:43,187 [main] ERROR org.springframework.boot.SpringApplication (SpringApplication.java:858) - Application run failed java.lang.IllegalArgumentException: String 'null' cannot be converted to LogFeederMode enum at org.apache.ambari.logfeeder.conf.LogFeederMode.fromString(LogFeederMode.java:48) ~[ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar:?] at org.apache.ambari.logfeeder.conf.condition.NonCloudStorageCondition.matches(NonCloudStorageCondition.java:34) ~[ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar:?] at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:108) ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Assigned] (AMBARI-25993) logsearch-logfeeder cannot startup due to lake of configuration
[ https://issues.apache.org/jira/browse/AMBARI-25993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Zuo reassigned AMBARI-25993: -- Assignee: Robin Zuo > logsearch-logfeeder cannot startup due to lake of configuration > --- > > Key: AMBARI-25993 > URL: https://issues.apache.org/jira/browse/AMBARI-25993 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Assignee: Robin Zuo >Priority: Major > > logsearch-logfeeder fail to start and report the following error: > 2023-08-19 14:20:40,835 [main] INFO > org.springframework.boot.StartupInfoLogger (StartupInfoLogger.java:50) - > Starting LogFeeder on hadoop-1 with PID 78570 > (/usr/lib/ambari-logsearch-logfeeder/libs/ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar > started by root in /var/lib/ambari-agent) > 2023-08-19 14:20:40,861 [main] INFO > org.springframework.boot.SpringApplication (SpringApplication.java:675) - No > active profile set, falling back to default profiles: default > 2023-08-19 14:20:43,187 [main] ERROR > org.springframework.boot.SpringApplication (SpringApplication.java:858) - > Application run failed > java.lang.IllegalArgumentException: String 'null' cannot be converted to > LogFeederMode enum > at > org.apache.ambari.logfeeder.conf.LogFeederMode.fromString(LogFeederMode.java:48) > ~[ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar:?] > at > org.apache.ambari.logfeeder.conf.condition.NonCloudStorageCondition.matches(NonCloudStorageCondition.java:34) > ~[ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar:?] > at > org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:108) > ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25992) logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade
[
https://issues.apache.org/jira/browse/AMBARI-25992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Zuo updated AMBARI-25992:
---
Parent: AMBARI-25951
Issue Type: Technical task (was: Improvement)
> logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade
>
>
> Key: AMBARI-25992
> URL: https://issues.apache.org/jira/browse/AMBARI-25992
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-logsearch
>Reporter: Robin Zuo
>Assignee: Robin Zuo
>Priority: Major
>
> ambari-logsearch-portal server cannot startup.
> After spring-boot upgrade from 2.0.6.RELEASE to 2.1.5.RELEASE, due to the
> change of class LdapAutoConfiguration, spring need the LdapTemplate bean
> during startup.
> Without the LdapTemplate bean, logsearch-portal server report the following
> error:
> 2023-08-11 06:28:24,471 [main] WARN org.eclipse.jetty.webapp.WebAppContext
> (WebAppContext.java:554) - Failed startup of context
> o.s.b.w.e.j.JettyEmbeddedWebAppContext@6e8fdd19\{application,/,[file:///tmp/jetty-docbase.7488131157696980871.61888/,
>
> jar:file:/usr/lib/ambari-logsearch-portal/libs/swagger-ui-3.19.0.jar!/META-INF/resources],UNAVAILABLE}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'servletEndpointRegistrar' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]:
> Bean instantiation via factory method failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]:
> Factory method 'servletEndpointRegistrar' threw exception; nested exception
> is org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'healthEndpoint' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]:
> Unsatisfied dependency expressed through method 'healthEndpoint' parameter
> 1; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'healthIndicatorRegistry' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/health/HealthIndicatorAutoConfiguration.class]:
> Bean instantiation via factory method failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.springframework.boot.actuate.health.HealthIndicatorRegistry]: Factory
> method 'healthIndicatorRegistry' threw exception; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.springframework.boot.actuate.autoconfigure.ldap.LdapHealthIndicatorAutoConfiguration':
> Unsatisfied dependency expressed through constructor parameter 0; nested
> exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'ldapTemplate' defined in class path resource
> [org/springframework/boot/autoconfigure/ldap/LdapAutoConfiguration.class]:
> Unsatisfied dependency expressed through method 'ldapTemplate' parameter 0;
> nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type 'org.springframework.ldap.core.ContextSource'
> available: expected at least 1 bean which qualifies as autowire candidate.
> Dependency annotations: {}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Assigned] (AMBARI-25992) logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade
[
https://issues.apache.org/jira/browse/AMBARI-25992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Zuo reassigned AMBARI-25992:
--
Assignee: Robin Zuo
> logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade
>
>
> Key: AMBARI-25992
> URL: https://issues.apache.org/jira/browse/AMBARI-25992
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch
>Reporter: Robin Zuo
>Assignee: Robin Zuo
>Priority: Major
>
> ambari-logsearch-portal server cannot startup.
> After spring-boot upgrade from 2.0.6.RELEASE to 2.1.5.RELEASE, due to the
> change of class LdapAutoConfiguration, spring need the LdapTemplate bean
> during startup.
> Without the LdapTemplate bean, logsearch-portal server report the following
> error:
> 2023-08-11 06:28:24,471 [main] WARN org.eclipse.jetty.webapp.WebAppContext
> (WebAppContext.java:554) - Failed startup of context
> o.s.b.w.e.j.JettyEmbeddedWebAppContext@6e8fdd19\{application,/,[file:///tmp/jetty-docbase.7488131157696980871.61888/,
>
> jar:file:/usr/lib/ambari-logsearch-portal/libs/swagger-ui-3.19.0.jar!/META-INF/resources],UNAVAILABLE}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'servletEndpointRegistrar' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]:
> Bean instantiation via factory method failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]:
> Factory method 'servletEndpointRegistrar' threw exception; nested exception
> is org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'healthEndpoint' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]:
> Unsatisfied dependency expressed through method 'healthEndpoint' parameter
> 1; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'healthIndicatorRegistry' defined in class path resource
> [org/springframework/boot/actuate/autoconfigure/health/HealthIndicatorAutoConfiguration.class]:
> Bean instantiation via factory method failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to instantiate
> [org.springframework.boot.actuate.health.HealthIndicatorRegistry]: Factory
> method 'healthIndicatorRegistry' threw exception; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.springframework.boot.actuate.autoconfigure.ldap.LdapHealthIndicatorAutoConfiguration':
> Unsatisfied dependency expressed through constructor parameter 0; nested
> exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'ldapTemplate' defined in class path resource
> [org/springframework/boot/autoconfigure/ldap/LdapAutoConfiguration.class]:
> Unsatisfied dependency expressed through method 'ldapTemplate' parameter 0;
> nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type 'org.springframework.ldap.core.ContextSource'
> available: expected at least 1 bean which qualifies as autowire candidate.
> Dependency annotations: {}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25992) logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade
Robin Zuo created AMBARI-25992:
--
Summary: logsearch-portal cannot startup due to
spring-boot-autoconfigure upgrade
Key: AMBARI-25992
URL: https://issues.apache.org/jira/browse/AMBARI-25992
Project: Ambari
Issue Type: Improvement
Components: ambari-logsearch
Reporter: Robin Zuo
ambari-logsearch-portal server cannot startup.
After spring-boot upgrade from 2.0.6.RELEASE to 2.1.5.RELEASE, due to the
change of class LdapAutoConfiguration, spring need the LdapTemplate bean during
startup.
Without the LdapTemplate bean, logsearch-portal server report the following
error:
2023-08-11 06:28:24,471 [main] WARN org.eclipse.jetty.webapp.WebAppContext
(WebAppContext.java:554) - Failed startup of context
o.s.b.w.e.j.JettyEmbeddedWebAppContext@6e8fdd19\{application,/,[file:///tmp/jetty-docbase.7488131157696980871.61888/,
jar:file:/usr/lib/ambari-logsearch-portal/libs/swagger-ui-3.19.0.jar!/META-INF/resources],UNAVAILABLE}
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'servletEndpointRegistrar' defined in class path resource
[org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]:
Bean instantiation via factory method failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
[org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]:
Factory method 'servletEndpointRegistrar' threw exception; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name 'healthEndpoint' defined in class path resource
[org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]:
Unsatisfied dependency expressed through method 'healthEndpoint' parameter 1;
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'healthIndicatorRegistry' defined in class path
resource
[org/springframework/boot/actuate/autoconfigure/health/HealthIndicatorAutoConfiguration.class]:
Bean instantiation via factory method failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
[org.springframework.boot.actuate.health.HealthIndicatorRegistry]: Factory
method 'healthIndicatorRegistry' threw exception; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name
'org.springframework.boot.actuate.autoconfigure.ldap.LdapHealthIndicatorAutoConfiguration':
Unsatisfied dependency expressed through constructor parameter 0; nested
exception is org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'ldapTemplate' defined in class path resource
[org/springframework/boot/autoconfigure/ldap/LdapAutoConfiguration.class]:
Unsatisfied dependency expressed through method 'ldapTemplate' parameter 0;
nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying
bean of type 'org.springframework.ldap.core.ContextSource' available: expected
at least 1 bean which qualifies as autowire candidate. Dependency annotations:
{}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
