V1.0RC30 cannot start normally
shiner-chen opened this issue · 2 comments
shiner-chen commented
I downloaded the V1.0RC30 source code and built the project locally. I found the below error when start the geoserver-cloud. How to deal with it ?
[chenx@localhost geoserver-cloud]$ docker-compose ps
/usr/local/lib/python3.6/site-packages/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography and will be removed in a future release.
from cryptography.hazmat.backends import default_backend
Name Command State Ports
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
gscloud_admin_1 /bin/sh -c exec env USER_I ... Up (unhealthy) 0.0.0.0:9091->8080/tcp,:::9091->8080/tcp
gscloud_config_1 /bin/sh -c exec env USER_I ... Up (healthy) 0.0.0.0:8888->8080/tcp,:::8888->8080/tcp, 8081/tcp
gscloud_discovery_1 /bin/sh -c exec env USER_I ... Up (healthy) 8081/tcp, 0.0.0.0:8761->8761/tcp,:::8761->8761/tcp
gscloud_gateway_1 /bin/sh -c exec env USER_I ... Up (healthy) 0.0.0.0:9090->8080/tcp,:::9090->8080/tcp, 8081/tcp
gscloud_gwc_1 /bin/sh -c exec env USER_I ... Exit 255
gscloud_postgis_1 docker-entrypoint.sh postgres Up 0.0.0.0:5432->5432/tcp,:::5432->5432/tcp
gscloud_rabbitmq_1 docker-entrypoint.sh rabbi ... Up 15671/tcp, 0.0.0.0:15672->15672/tcp,:::15672->15672/tcp, 15691/tcp, 15692/tcp, 25672/tcp, 4369/tcp, 5671/tcp, 0.0.0.0:5672->5672/tcp,:::5672->5672/tcp
gscloud_rest_1 /bin/sh -c exec env USER_I ... Exit 255
gscloud_wcs_1 /bin/sh -c exec env USER_I ... Exit 255
gscloud_webui_1 /bin/sh -c exec env USER_I ... Exit 255
gscloud_wfs_1 /bin/sh -c exec env USER_I ... Exit 255
gscloud_wms_1 /bin/sh -c exec env USER_I ... Exit 255
[chenx@localhost geoserver-cloud]$
[chenx@localhost geoserver-cloud]$ docker logs gscloud_gwc_1
2023-03-07 09:25:58.519 INFO 1 --- [ main] c.c.j.SimpleJNDIStaticContextInitializer : Initializing JNDI InitialContextFactoryBuilder
2023-03-07 09:25:58.524 INFO 1 --- [ main] c.c.j.SimpleJNDIStaticContextInitializer : Registered JNDI implementation using org.geoserver.cloud.jndi.SimpleNamingContextBuilder
2023-03-07 09:25:59.387 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.retry.annotation.RetryConfiguration' of type [org.springframework.retry.annotation.RetryConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-03-07 09:26:00.096 DEBUG 1 --- [ main] o.s.retry.support.RetryTemplate : Retry: count=0
2023-03-07 09:26:00.213 INFO 1 --- [ main] c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at : http://config:8080
2023-03-07 09:26:00.464 INFO 1 --- [ main] c.c.c.ConfigServicePropertySourceLocator : Located environment: name=geoserver, profiles=[gwc_service,datadir], label=null, version=null, state=null
2023-03-07 09:26:00.465 INFO 1 --- [ main] b.c.PropertySourceBootstrapConfiguration : Located property source: [BootstrapPropertySource {name='bootstrapProperties-configClient'}]
2023-03-07 09:26:00.515 INFO 1 --- [ main] c.c.j.SimpleJNDIStaticContextInitializer : JNDI InitialContextFactoryBuilder already set
2023-03-07 09:26:00.517 INFO 1 --- [ main] o.g.c.gwc.app.GeoWebCacheApplication : The following 2 profiles are active: "gwc_service", "datadir"
2023-03-07 09:26:05.827 INFO 1 --- [ main] faultConfiguringBeanFactoryPostProcessor : No bean named 'errorChannel' has been explicitly defined. Therefore, a default PublishSubscribeChannel will be created.
2023-03-07 09:26:05.865 INFO 1 --- [ main] faultConfiguringBeanFactoryPostProcessor : No bean named 'integrationHeaderChannelRegistry' has been explicitly defined. Therefore, a default DefaultHeaderChannelRegistry will be created.
2023-03-07 09:26:06.073 INFO 1 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=311248e0-d2ec-3376-92f9-abe42b277cbe
2023-03-07 09:26:06.897 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.integration.config.IntegrationManagementConfiguration' of type [org.springframework.integration.config.IntegrationManagementConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-03-07 09:26:06.907 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'integrationChannelResolver' of type [org.springframework.integration.support.channel.BeanFactoryChannelResolver] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-03-07 09:26:06.932 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-03-07 09:26:06.943 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration$ReactorDeferringLoadBalancerFilterConfig' of type [org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration$ReactorDeferringLoadBalancerFilterConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-03-07 09:26:06.946 INFO 1 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'reactorDeferringLoadBalancerExchangeFilterFunction' of type [org.springframework.cloud.client.loadbalancer.reactive.DeferringLoadBalancerExchangeFilterFunction] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-03-07 09:26:07.487 INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2023-03-07 09:26:07.498 INFO 1 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2023-03-07 09:26:07.498 INFO 1 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.69]
2023-03-07 09:26:07.597 INFO 1 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2023-03-07 09:26:07.597 INFO 1 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 7046 ms
2023-03-07 09:26:07.771 ERROR 1 --- [ main] o.s.b.web.embedded.tomcat.TomcatStarter : Error starting Tomcat context. Exception: org.springframework.beans.factory.UnsatisfiedDependencyException. Message: Error creating bean with name 'webMvcMetricsFilter' defined in class path resource [org/springframework/boot/actuate/autoconfigure/metrics/web/servlet/WebMvcMetricsAutoConfiguration.class]: Unsatisfied dependency expressed through method 'webMvcMetricsFilter' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'simpleMeterRegistry' defined in class path resource [org/springframework/boot/actuate/autoconfigure/metrics/export/simple/SimpleMetricsExportAutoConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'geoserverCatalogMetrics' defined in class path resource [org/geoserver/cloud/autoconfigure/metrics/catalog/CatalogMetricsAutoConfiguration.class]: Unsatisfied dependency expressed through method 'geoserverCatalogMetrics' parameter 1; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'catalog' defined in class path resource [org/geoserver/cloud/config/catalog/backend/core/CoreBackendConfiguration.class]: Unsatisfied dependency expressed through method 'localWorkspaceCatalog' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'advertisedCatalog' defined in class path resource [org/geoserver/cloud/config/catalog/backend/core/CoreBackendConfiguration.class]: Unsatisfied dependency expressed through method 'advertisedCatalog' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'dataDirectory' defined in class path resource [org/geoserver/cloud/config/catalog/backend/core/CoreBackendConfiguration.class]: Unsatisfied dependency expressed through method 'dataDirectory' parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.geoserver.platform.GeoServerResourceLoader' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
2023-03-07 09:26:07.798 INFO 1 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2023-03-07 09:26:08.029 WARN 1 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat
2023-03-07 09:26:08.051 INFO 1 --- [ main] ConditionEvaluationReportLoggingListener :
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2023-03-07 09:26:08.165 INFO 1 --- [ main] org.geoserver.cloud.config.security : GeoServer security being configured through classpath*:/applicationSecurityContext.xml
2023-03-07 09:26:08.183 ERROR 1 --- [ main] o.s.b.d.LoggingFailureAnalysisReporter :
***************************
APPLICATION FAILED TO START
***************************
Description:
Parameter 0 of method dataDirectory in org.geoserver.cloud.config.catalog.backend.core.CoreBackendConfiguration required a bean of type 'org.geoserver.platform.GeoServerResourceLoader' that could not be found.
Action:
Consider defining a bean of type 'org.geoserver.platform.GeoServerResourceLoader' in your configuration.
groldan commented
Hi, the docker compose files in the root directory are only meant to be run in tandem, e.g., to use the datadirectory backend:
docker-compose -f docker-compose.yml -f docker-compose-shared_datadir.yml --compatibility
or to use the jdbcconfig backend:
docker-compose -f docker-compose.yml -f docker-compose-jdbcconfig.yml --compatibility
these are used only during development, for example to run a service through eclipse and make it join the cluster.
For a simpler set up there are docker-compose.yml files under docs/deploy/docker-compose/stable/
groldan commented
Closing as not-a-bug, feel free to re-open if it is