Closed FTwOoO closed 3 years ago
The key error is here:
{error,{{badmatch,{error,timeout}},[{be_db_worker,init
which implies that the db_worker had issues connecting with your database
The key error is here:
{error,{{badmatch,{error,timeout}},[{be_db_worker,init
which implies that the db_worker had issues connecting with your database
"had issues connecting with your database" is fiexed, now logging: "failed to dial proxy server "/p2p/1128ipxTAurFrUHuXx3XjayKQ75BPXgVWcCUDmTH3CnFJ8HoZy1q" not_found" and also has some success log: "new block sync starting with Pid: <0.1941.0>, Ref: #Ref<0.4078392510.943980545.51030>, Peer: "/p2p/1126uhuuGhDSrrFpxEvV5xURN2xKab6XpTrD5YHcxHVBeMUoN3V4"
is the etl runs well? i run the https://github.com/helium/blockchain-http service and call the stats API:
curl x.x.x.x:80/v1/stats | jq
get null data fields:
{ "data": { "token_supply": 0, "election_times": { "last_week": { "stddev": null, "avg": null },
is the API service runs well ?
The key error is here:
{error,{{badmatch,{error,timeout}},[{be_db_worker,init
which implies that the db_worker had issues connecting with your database"had issues connecting with your database" is fiexed, now logging: "failed to dial proxy server "/p2p/1128ipxTAurFrUHuXx3XjayKQ75BPXgVWcCUDmTH3CnFJ8HoZy1q" not_found" and also has some success log: "new block sync starting with Pid: <0.1941.0>, Ref: #Ref<0.4078392510.943980545.51030>, Peer: "/p2p/1126uhuuGhDSrrFpxEvV5xURN2xKab6XpTrD5YHcxHVBeMUoN3V4"
Yes etl is trying to sync with nodes.. It will take a while for it to discover peers to sync blocks with.
is the etl runs well? i run the https://github.com/helium/blockchain-http service and call the stats API:
try :80/v1/blocks/height.
I'm going to guess it will start storing data shortly if you took the blockchain.db dump.
To avoid conversations in multiple places, please join us on discord and ask there since GH issues is not a great place for support questions
The key error is here:
{error,{{badmatch,{error,timeout}},[{be_db_worker,init
which implies that the db_worker had issues connecting with your database"had issues connecting with your database" is fiexed, now logging: "failed to dial proxy server "/p2p/1128ipxTAurFrUHuXx3XjayKQ75BPXgVWcCUDmTH3CnFJ8HoZy1q" not_found" and also has some success log: "new block sync starting with Pid: <0.1941.0>, Ref: #Ref<0.4078392510.943980545.51030>, Peer: "/p2p/1126uhuuGhDSrrFpxEvV5xURN2xKab6XpTrD5YHcxHVBeMUoN3V4"
Yes etl is trying to sync with nodes.. It will take a while for it to discover peers to sync blocks with.
is the etl runs well? i run the https://github.com/helium/blockchain-http service and call the stats API:
try :80/v1/blocks/height.
I'm going to guess it will start storing data shortly if you took the blockchain.db dump.
To avoid conversations in multiple places, please join us on discord and ask there since GH issues is not a great place for support questions
thanks, the problem is no problem. there is no way to bootstrap an etl quickly, and the libp2p complains too many error which can be ignore. nobody can tell which is the real problem and which is not, please write some documentation for the project, about architecture/common issue
server: Alicloud ECS 2 core 4G memory ubuntu 20.04
region: HongKong China docker image: build with Dockerfile of project at branch 1.1.105
run with command:
error: