8000 There's no block in few minutes when upgrading version form v0.20.3 to v0.21.1 ## v0.20.3 升级到 v0.21.1 出现几分钟不出块, · Issue #346 · citahub/cita · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

There's no block in few minutes when upgrading version form v0.20.3 to v0.21.1 ## v0.20.3 升级到 v0.21.1 出现几分钟不出块, #346

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

Closed
jiangxianliang007 opened this issue Mar 19, 2019 · 3 comments
Labels
question Further information is requested

Comments

@jiangxianliang007
Copy link
Contributor

v0.20.3 升级到 v0.21.1 ,出现几分钟不出块的情况,

第一个节点升级时间是15:13
第二个节点升级时间是15:17
第三个节点升级时间是15:22
第四个节点升级时间是15:26

升级第一个节点正常,升级完第二个节点后 开始不出块(查看chain 基本没有日志输出),把所有节点都升级完后,过了5分钟才正常出块,
15:17 开始不出块,15:31 恢复出块,
image

image

@kaikai1024
Copy link
Contributor

Would you please post some logs about bft?

@jiangxianliang007
Copy link
Contributor Author

2019-03-19T15:16:30.042917390+08:00 - WARN - System clock seems off!!!
2019-03-19T15:16:38.522568865+08:00 - INFO - receive_new_status Bft { h: 3901093, r: 1, s: 8 } get new chain status h: 3901093, r: 1, cost time: 11.600345126s
2019-03-19T15:16:38.527503989+08:00 - INFO - receive_new_status Bft { h: 3901094, r: 0, s: 8 } get new chain status h: 3901094, r: 0, cost time: 11.605288088s
2019-03-19T15:16:38.534183970+08:00 - INFO - receive_new_status Bft { h: 3901095, r: 0, s: 8 } get new chain status h: 3901095, r: 0, cost time: 11.611980922s
2019-03-19T15:16:38.538181989+08:00 - INFO - receive_new_status Bft { h: 3901096, r: 0, s: 8 } get new chain status h: 3901096, r: 0, cost time: 11.615979411s
2019-03-19T15:16:41.511940214+08:00 - INFO - new_proposal Bft { h: 3901097, r: 1, s: 0 } proof is old; proof height 3900714
2019-03-19T15:16:45.042920915+08:00 - WARN - System clock seems off!!!
2019-03-19T15:16:46.931122682+08:00 - INFO - receive_new_status Bft { h: 3901097, r: 1, s: 8 } get new chain status h: 3901097, r: 1, cost time: 7.991941788s
2019-03-19T15:16:46.935025314+08:00 - INFO - receive_new_status Bft { h: 3901098, r: 0, s: 8 } get new chain status h: 3901098, r: 0, cost time: 7.995851294s
2019-03-19T15:16:50.527136030+08:00 - INFO - receive_new_status Bft { h: 3901099, r: 0, s: 8 } get new chain status h: 3901099, r: 0, cost time: 3.191132652s
2019-03-19T15:16:50.530895177+08:00 - INFO - receive_new_status Bft { h: 3901100, r: 0, s: 8 } get new chain sta 8000 tus h: 3901100, r: 0, cost time: 3.194907844s
2019-03-19T15:16:53.436095569+08:00 - INFO - new_proposal Bft { h: 3901101, r: 1, s: 0 } proof is old; proof height 3900714
2019-03-19T15:17:20.698939519+08:00 - WARN - System clock seems off!!!
2019-03-19T15:17:35.698890326+08:00 - WARN - System clock seems off!!!
2019-03-19T15:17:50.698915790+08:00 - WARN - System clock seems off!!!
2019-03-19T15:18:05.653677736+08:00 - INFO - new_proposal Bft { h: 3901101, r: 5, s: 0 } proof is old; proof height 3900714
2019-03-19T15:18:05.698895332+08:00 - WARN - System clock seems off!!!
2019-03-19T15:18:20.698923714+08:00 - WARN - System clock seems off!!!
2019-03-19T15:18:35.698901139+08:00 - WARN - System clock seems off!!!
2019-03-19T15:18:50.698904539+08:00 - WARN - System clock seems off!!!
2019-03-19T15:19:16.030900631+08:00 - WARN - System clock seems off!!!
2019-03-19T15:19:51.490900722+08:00 - WARN - System clock seems off!!!
2019-03-19T15:20:16.694913010+08:00 - WARN - System clock seems off!!!
2019-03-19T15:20:41.962911758+08:00 - WARN - System clock seems off!!!
2019-03-19T15:20:56.962921889+08:00 - WARN - System clock seems off!!!
2019-03-19T15:21:52.914896919+08:00 - WARN - System clock seems off!!!
2019-03-19T15:22:07.914899312+08:00 - WARN - System clock seems off!!!
2019-03-19T15:22:53.710892178+08:00 - WARN - System clock seems off!!!
2019-03-19T15:23:18.934900390+08:00 - WARN - System clock seems off!!!
2019-03-19T15:23:33.934912781+08:00 - WARN - System clock seems off!!!
2019-03-19T15:24:09.646904199+08:00 - WARN - System clock seems off!!!
2019-03-19T15:24:34.894890299+08:00 - WARN - System clock seems off!!!
2019-03-19T15:24:49.894923125+08:00 - WARN - System clock seems off!!!
2019-03-19T15:25:15.294910687+08:00 - WARN - System clock seems off!!!
2019-03-19T15:25:50.930896792+08:00 - WARN - System clock seems off!!!
2019-03-19T15:26:16.198913525+08:00 - WARN - System clock seems off!!!
2019-03-19T15:26:31.198891407+08:00 - WARN - System clock seems off!!!
2019-03-19T15:26:56.518897837+08:00 - WARN - System clock seems off!!!
2019-03-19T15:27:11.518918967+08:00 - WARN - System clock seems off!!!
2019-03-19T15:27:26.518895852+08:00 - WARN - System clock seems off!!!
2019-03-19T15:27:41.518913066+08:00 - WARN - System clock seems off!!!
2019-03-19T15:28:37.538898073+08:00 - WARN - System clock seems off!!!
2019-03-19T15:28:52.538902946+08:00 - WARN - System clock seems off!!!
2019-03-19T15:29:27.902906541+08:00 - WARN - System clock seems off!!!
2019-03-19T15:29:42.902909569+08:00 - WARN - System clock seems off!!!
2019-03-19T15:29:57.902901530+08:00 - WARN - System clock seems off!!!
2019-03-19T15:30:23.330896643+08:00 - WARN - System clock seems off!!!
2019-03-19T15:30:48.358909924+08:00 - WARN - System clock seems off!!!
2019-03-19T15:31:03.358904882+08:00 - WARN - System clock seems off!!!
2019-03-19T15:31:28.522937855+08:00 - WARN - System clock seems off!!!
2019-03-19T15:31:43.522905870+08:00 - WARN - System clock seems off!!!
2019-03-19T15:32:28.902911492+08:00 - WARN - System clock seems off!!!
2019-03-19T15:32:52.776200025+08:00 - INFO - new_proposal Bft { h: 3901101, r: 9, s: 0 } proposal new block with 0 txs: block hash 0xec9f122cb14495d517169237a385b160ff2a4bcb0aa3001d3be02b781ff6cf12
2019-03-19T15:32:52.782164335+08:00 - INFO - commit_block Bft { h: 3901101, r: 9, s: 6 } consensus time 961.850041585s proposal 0xec9f…cf12 locked block hash 0xec9f…cf12
2019-03-19T15:32:52.789684171+08:00 - INFO - receive_new_status Bft { h: 3901101, r: 9, s: 8 } get new chain status h: 3901101, r: 9, cost time: 961.857549179s
2019-03-19T15:32:53.190788883+08:00 - INFO - new_proposal Bft { h: 3901102, r: 0, s: 0 } proposal new block with 1 txs: block hash 0xc7c04751b601441de85bc5d81c7b3a56a29a533da5578275723470e616565b14
2019-03-19T15:32:53.220145173+08:00 - INFO - commit_block Bft { h: 3901102, r: 0, s: 6 } consensus time 29.389815ms proposal 0xc7c0…5b14 locked block hash 0xc7c0…5b14
2019-03-19T15:32:53.228610706+08:00 - INFO - receive_new_status Bft { h: 3901102, r: 0, s: 8 } get new chain status h: 3901102, r: 0, cost time: 37.84375ms

@kaikai1024 kaikai1024 changed the title v0.20.3 升级到 v0.21.1 出现几分钟不出块, There's no block in few minutes when upgrading version form v0.20.3 to v0.21.1 ## v0.20.3 升级到 v0.21.1 出现几分钟不出块, Mar 22, 2019
@kaikai1024 kaikai1024 added the question Further information is requested label Apr 29, 2019
@kaikai1024
Copy link
Contributor

Reopen it when reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants
0