apache / apache/dubbo-admin

使用Docker部署Dubbo-Admin启动失败报错,版本是0.5.0

Open
#1,021 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
4.1k
Forks
2.2k
Avg merge
10d 12h
Merged PRs (30d)
4

Description

![image](https://user-images.githubusercontent.com/12378933/224019438-cef7d460-4e70-4ebe-86c9-15180d7dcaff.png)

会因为个别服务问题导致Admin启动失败吗?

```
dubbo-admin2 | SLF4J: Class path contains multiple SLF4J bindings.
dubbo-admin2 | SLF4J: Found binding in [jar:file:/app.jar!/BOOT-INF/lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
dubbo-admin2 | SLF4J: Found binding in [jar:file:/app.jar!/BOOT-INF/lib/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
dubbo-admin2 | SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
dubbo-admin2 | SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
dubbo-admin2 |
dubbo-admin2 | . ____ _ __ _ _
dubbo-admin2 | /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
dubbo-admin2 | ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
dubbo-admin2 | \\/ ___)| |_)| | | | | || (_| | ) ) ) )
dubbo-admin2 | ' |____| .__|_| |_|_| |_\__, | / / / /
dubbo-admin2 | =========|_|==============|___/=/_/_/_/
dubbo-admin2 | :: Spring Boot :: (v2.3.12.RELEASE)
dubbo-admin2 |
dubbo-admin2 | log4j:WARN No appenders could be found for logger (org.apache.dubbo.rpc.model.FrameworkModel).
dubbo-admin2 | log4j:WARN Please initialize the log4j system properly.
dubbo-admin2 | log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
dubbo-admin2 | 2023-03-09 12:01:33.103 INFO 6 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
dubbo-admin2 | 2023-03-09 12:01:33.308 INFO 6 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 164ms. Found 0 JPA repository interfaces.
dubbo-admin2 | 2023-03-09 12:01:38.714 INFO 6 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
dubbo-admin2 | 2023-03-09 12:01:39.000 INFO 6 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 12096 ms
dubbo-admin2 | 2023-03-09 12:01:42.752 INFO 6 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
dubbo-admin2 | 2023-03-09 12:01:43.456 INFO 6 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
dubbo-admin2 | _ _ |_ _ _|_. ___ _ | _
dubbo-admin2 | | | |\/|_)(_| | |_\ |_)||_|_\
dubbo-admin2 | / |
dubbo-admin2 | 3.4.2
dubbo-admin2 | 2023-03-09 12:08:21.222 WARN 6 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getServiceMapping' defined in class path resource [org/apache/dubbo/admin/config/ConfigCenter.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apache.dubbo.admin.registry.mapping.ServiceMapping]: Factory method 'getServiceMapping' threw exception; nested exception is org.apache.dubbo.rpc.RpcException: Fail to create remoting client for service(dubbo://12.12.12.12:30003/org.apache.dubbo.metadata.MetadataService?codec=dubbo&connections=1&dubbo=2.0.2&group=bessky-store-platform-aliexpress&heartbeat=60000&port=30003&protocol=dubbo&release=3.1.1&retries=0&side=provider&timeout=360000&version=1.0.0): client(url: dubbo://12.12.12.12:30003/org.apache.dubbo.metadata.MetadataService?codec=dubbo&connections=1&dubbo=2.0.2&group=bessky-store-platform-aliexpress&heartbeat=60000&port=30003&protocol=dubbo&release=3.1.1&retries=0&side=provider&timeout=360000&version=1.0.0) failed to connect to server /12.12.12.12:30003 client-side timeout 3000ms (elapsed: 3001ms) from netty client 172.17.0.2 using dubbo version 3.0.8
dubbo-admin2 | 2023-03-09 12:08:21.236 INFO 6 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown initiated...
dubbo-admin2 | 2023-03-09 12:08:21.245 INFO 6 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown completed.
dubbo-admin2 | 2023-03-09 12:08:21.267 INFO 6 --- [ main] ConditionEvaluationReportLoggingListener :
dubbo-admin2 |
dubbo-admin2 | Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
dubbo-admin2 | 2023-03-09 12:08:21.308 ERROR 6 --- [ main] o.s.boot.SpringApplication : Application run failed
dubbo-admin2 |
dubbo-admin2 | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getServiceMapping' defined in class path resource [org/apache/dubbo/admin/config/ConfigCenter.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apache.dubbo.admin.registry.mapping.ServiceMapping]: Factory method 'getServiceMapping' threw exception; nested exception is org.apache.dubbo.rpc.RpcException: Fail to create remoting client for service(dubbo://12.12.12.12:30003/org.apache.dubbo.metadata.MetadataService?codec=dubbo&connections=1&dubbo=2.0.2&group=bessky-store-platform-aliexpress&heartbeat=60000&port=30003&protocol=dubbo&release=3.1.1&retries=0&side=provider&timeout=360000&version=1.0.0): client(url: dubbo://12.12.12.12:30003/org.apache.dubbo.metadata.MetadataService?codec=dubbo&connections=1&dubbo=2.0.2&group=bessky-store-platform-aliexpress&heartbeat=60000&port=30003&protocol=dubbo&release=3.1.1&retries=0&side=provider&timeout=360000&version=1.0.0) failed to connect to server /12.12.12.12:30003 client-side timeout 3000ms (elapsed: 3001ms) from netty client 172.17.0.2 using dubbo version 3.0.8
dubbo-admin2 | at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:657)
dubbo-admin2 | at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:637)
dubbo-admin2 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1341)
dubbo-admin2 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1181)
dubbo-admin2 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:556)
dubbo-admin2 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:516)
dubbo-admin2 | at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:324)
dubbo-admin2 | at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
```

Contributor guide

Open the contributing guide

Research direction

Start with the ConfigCenter.getServiceMapping factory method named in the startup stack trace, then reproduce the 0.5.0 Docker deployment using the logged provider endpoint. Determine whether one unreachable service should prevent Admin startup and document or verify the expected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java, spring-boot
Domain
backend, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.