-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
使用docker-compose启动 java-wisdomcore节点后,我应该如何开始同步区块?(After starting the 'Java wisdomcore' node with 'docker compose', how do I start to synchronize blocks?) #74
Comments
hi,
if you enable full node, the node will start sync task automatically.
best regards.
…________________________________
From: LmingXie <[email protected]>
Sent: Wednesday, September 23, 2020 1:47 AM
To: WisedomChainGroup/java-wisdomcore <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [WisedomChainGroup/java-wisdomcore] 使用docker-compose启动 java-wisdomcore节点后,我应该如何开始同步区块?(After starting the 'Java wisdomcore' node with 'docker compose', how do I start to synchronize blocks?) (#74)
问题描述(Problem description):我想要搭建一个WDC的全节点,使用docker-compose启动 java-wisdomcore节点后,我应该如何让节点开始同步区块?(I want to build a WDC full node,After starting the 'Java wisdomcore' node with 'docker compose', how do I start to synchronize blocks?)
我的wdc.yml配置(my wdc.yml to configure):
version: '3.1'
services:
wdc_pgsql:
image: wisdomchain/wdc_pgsql
restart: always
container_name: wdc_pgsql
privileged: true
volumes:
- /mnt/wdc/data/wdc_pgsql:/var/lib/postgresql/data
ports:
- 127.0.0.1:5432:5432
environment:
POSTGRES_USER: wdcadmin
POSTGRES_PASSWORD: PqR_m03VaTsB1M/hyKY
WDC_POSTGRES_USER: replica
WDC_POSTGRES_PASSWORD: replica
wdc_core:
image: wisdomchain/wdc_core
restart: always
container_name: wdc_core
privileged: true
volumes:
- /mnt/wdc/data/wdc_logs:/logs
ports:
- 19585:19585
environment:
DATA_SOURCE_URL: 'jdbc:postgresql://wdc_pgsql:5432/postgres'
DB_USERNAME: 'replica'
DB_PASSWORD: 'replica'
ENABLE_MINING: 'false'
WDC_MINER_COINBASE: '1c33e5d8adde0cf3cc52c7505468e79586a46688'
FAST_SYNC_DIRECTORY: '/genesis/'
启动后的日志(Log after startup):
. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot :: (v2.2.5.RELEASE)
2020-09-23 09:08:44.324 INFO 6 --- [ main] org.wisdom.Start : Starting Start on 207faaeda59a with PID 6 (/app/app.jar started by root in /)
2020-09-23 09:08:44.331 INFO 6 --- [ main] org.wisdom.Start : No active profile set, falling back to default profiles: default
2020-09-23 09:08:46.367 INFO 6 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2020-09-23 09:08:46.588 INFO 6 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 182ms. Found 3 JPA repository interfaces.
2020-09-23 09:08:47.564 INFO 6 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'scheduleConfig' of type [org.wisdom.pool.ScheduleConfig$$EnhancerBySpringCGLIB$$ef88da81] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-09-23 09:08:48.379 INFO 6 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 19585 (http)
2020-09-23 09:08:48.413 INFO 6 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2020-09-23 09:08:48.414 INFO 6 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.31]
2020-09-23 09:08:48.505 INFO 6 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2020-09-23 09:08:48.505 INFO 6 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 4082 ms
2020-09-23 09:08:49.019 INFO 6 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]
2020-09-23 09:08:49.192 INFO 6 --- [ main] org.hibernate.Version : HHH000412: Hibernate ORM core version 5.4.12.Final
2020-09-23 09:08:49.360 INFO 6 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
2020-09-23 09:08:49.499 INFO 6 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2020-09-23 09:08:49.608 INFO 6 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2020-09-23 09:08:49.632 INFO 6 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect
2020-09-23 09:08:50.775 INFO 6 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2020-09-23 09:08:50.785 INFO 6 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2020-09-23 09:08:50.841 INFO 6 --- [ main] init : initial validator found address = 1pQfDX4fvz7uzBQuM9FbuoKWohmhg9TmY
2020-09-23 09:08:50.841 INFO 6 --- [ main] init : initial validator found address = 12hk3cWr28BJWjASCy9Diw4bqH8SnWvSpP
2020-09-23 09:08:50.841 INFO 6 --- [ main] init : initial validator found address = 18mRFaYHguJyCWtAA9ZV1PZuGAb6UzAijE
2020-09-23 09:08:50.841 INFO 6 --- [ main] init : initial validator found address = 19JNq2jAprkxVrpkgBiRaa1m47WcUMXtCb
2020-09-23 09:08:50.841 INFO 6 --- [ main] init : initial validator found address = 1317J5fZb8kVrACnfi3PXN1T21573hYata
2020-09-23 09:08:58.649 INFO 6 --- [ main] sync : start sync status from 0 to 0
2020-09-23 09:08:58.660 INFO 6 --- [ main] sync : sync status finished
2020-09-23 09:09:10.864 INFO 6 --- [ main] ???? : total supply is 3.9766632030811584E8 WDC
2020-09-23 09:09:11.748 INFO 6 --- [ main] net : peer server is listening on wisdom://0d9ee35f099ff954e6cef820fdc7ca03fa62049bc91fefb0fa94a887192943aa2d87d2761325d9bdaa750e8229daa729897730b974009377eaa26d847afea362@localhost:9235
2020-09-23 09:09:11.748 INFO 6 --- [ main] net : provide address to your peers to connect wisdom://2d87d2761325d9bdaa750e8229daa729897730b974009377eaa26d847afea362@localhost:9235
2020-09-23 09:09:12.228 WARN 6 --- [ main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
2020-09-23 09:09:12.732 INFO 6 --- [ main] .s.s.UserDetailsServiceAutoConfiguration :
Using generated security password: 2947629c-942a-4439-9ff5-7c9e91a0222e
2020-09-23 09:09:12.846 INFO 6 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Creating filter chain: any request, [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@7524125c, org.springframework.security.web.context.SecurityContextPersistenceFilter@294bb6ae, org.springframework.security.web.header.HeaderWriterFilter@712594f4, org.springframework.security.web.authentication.logout.LogoutFilter@3f2a7ca0, org.wisdom.endpoint.AuthFilter@7612f385, org.springframework.security.web.authentication.www.BasicAuthenticationFilter@357e7113, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@71ac5723, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@84e43fb, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@330d16af, org.springframework.security.web.session.SessionManagementFilter@67aaf882, org.springframework.security.web.access.ExceptionTranslationFilter@3599b18, org.springframework.security.web.access.intercept.FilterSecurityInterceptor@57466fb7]
2020-09-23 09:09:12.860 INFO 6 --- [ main] o.s.s.c.ThreadPoolTaskScheduler : Initializing ExecutorService 'taskScheduler'
2020-09-23 09:09:13.556 INFO 6 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 2 endpoint(s) beneath base path '/wisdom'
2020-09-23 09:09:13.702 INFO 6 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 19585 (http) with context path ''
2020-09-23 09:09:13.707 INFO 6 --- [ main] org.wisdom.Start : Started Start in 29.964 seconds (JVM running for 30.458)
2020-09-23 09:16:01.814 INFO 6 --- [io-19585-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring DispatcherServlet 'dispatcherServlet'
2020-09-23 09:16:01.814 INFO 6 --- [io-19585-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet'
2020-09-23 09:16:01.837 INFO 6 --- [io-19585-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 23 ms
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#74>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJUMHLCX2C4FT2FBSF6S2M3SHG7ZLANCNFSM4RW2CL4A>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
问题描述(Problem description):我想要搭建一个WDC的全节点,使用docker-compose启动 java-wisdomcore节点后,我应该如何让节点开始同步区块?(I want to build a WDC full node,After starting the 'Java wisdomcore' node with 'docker compose', how do I start to synchronize blocks?)
我的wdc.yml配置(my wdc.yml to configure):
启动后的日志(Log after startup):
The text was updated successfully, but these errors were encountered: