search

tronprotocol / tron-deployment

tron main net conf
175 stars 367 forks source link

Tron nile stopped syncing at block 43284760 #122

Open andkom opened 3 months ago

andkom commented 3 months ago

Tron (nile) stopped syncing at block #43284760

Actions performed:

1) Updated test_net_config.conf and pulled fresh java-tron image -> didn't help 2) Emptied output-director and restarted java-tron -> syncing stuck at block #160

andkom commented 3 months ago

Config: https://github.com/tronprotocol/tron-deployment/blob/master/test_net_config.conf

After tron restart nodes count drops to 0:

============ Peer stats: all 2, active 2, passive 0

Peer /65.108.122.240:18888
connect time: 28s [3ms]
last know block num: 0
needSyncFromPeer:true
needSyncFromUs:false
syncToFetchSize:4000
syncToFetchSizePeekNum:43284761
syncBlockRequestedSize:0
remainNum:4222873
syncChainRequested:0
blockInProcess:2000

Peer /65.109.22.249:18888
connect time: 28s [4ms]
last know block num: 0
needSyncFromPeer:true
needSyncFromUs:false
syncToFetchSize:4000
syncToFetchSizePeekNum:43284761
syncBlockRequestedSize:0
remainNum:4222873
syncChainRequested:0
blockInProcess:1999

11:54:30.758 WARN  [peer-status-check] [net](PeerStatusCheck.java:51) Peer /65.108.122.240 not sync for a long time
11:54:30.758 INFO  [peer-status-check] [net](PeerConnection.java:175) Send peer /65.108.122.240:18888 message type: P2P_DISCONNECT
reason: TIME_OUT
11:54:30.758 WARN  [peer-status-check] [net](PeerStatusCheck.java:51) Peer /65.109.22.249 not sync for a long time
11:54:30.758 INFO  [peer-status-check] [net](PeerConnection.java:175) Send peer /65.109.22.249:18888 message type: P2P_DISCONNECT
reason: TIME_OUT
11:54:30.758 INFO  [peerClient-25] [net](P2pChannelInitializer.java:45) Close channel:/65.109.22.249:18888
11:54:30.758 INFO  [peerClient-27] [net](P2pChannelInitializer.java:45) Close channel:/65.108.122.240:18888
11:54:30.758 INFO  [peerClient-25] [net](ConnPoolService.java:261) Peer stats: channels 1, activePeers 1, active 1, passive 0
11:54:30.758 INFO  [peerClient-27] [net](ConnPoolService.java:261) Peer stats: channels 0, activePeers 0, active 0, passive 0
11:54:37.754 INFO  [peer-manager] [net](PeerManager.java:152)

============ Peer stats: all 0, active 0, passive 0

11:54:47.752 INFO  [NodePersistTask] [net](NodePersistService.java:82) Write nodes to store: 27/27 nodes
11:54:47.754 INFO  [peer-manager] [net](PeerManager.java:152)
fyyhtx commented 3 months ago

@andkom The configuration file of the Nile testnet can be obtained from here: https://nileex.io/join/getJoinPage. Make sure the proposal configuration is consistent with the nile testnet template:

block = { needSyncCheck = false maintenanceTimeInterval = 600000 proposalExpireTime = 600000 // }

What is the version of the service currently running? Make sure to use the latest nile branch to run the program: https://nileex.io/

In addition, considering that the database may be dirty, you can use a new snapshot to start the node, which can be downloaded from here: https://nile-snapshots.s3-accelerate.amazonaws.com/backup20240616/FullNode_output-directory.tgz

andkom commented 3 months ago

I use, default testnet config from https://github.com/tronprotocol/tron-deployment/blob/master/test_net_config.conf

2 weeks ago I replaced output-directory with fresh snapshot and it fixed issue, today I noticed that node is stuck again at block #47785755, I replaced with fresh snapshot and it fixed again.

Config from https://nileex.io/join/getJoinPage confuses me that the it is very different from fresh config.

Will try your changes.

andkom commented 3 months ago

version 4.7.5

fyyhtx commented 3 months ago

Looking forward to the results of your try!