Skip to content
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.

Sign up for GitHub

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

Jump to bottom

JCLI Block stuck #2304

Open
acewf opened this issue Jun 2, 2020 · 2 comments
Open

JCLI Block stuck #2304

acewf opened this issue Jun 2, 2020 · 2 comments
Labels
automated bug Something isn't working subsys-rest issues or PRs for the REST interface

Comments

@acewf
Copy link

acewf commented Jun 2, 2020

Describe the bug
Seems although the node keeps receiving block announcements, the JCLI status isn't updated.

Mandatory Information

  1. jcli 0.8.18 (HEAD-690eb547, release, linux [x86_64]) - [rustc 1.42.0 (b8cedc004 2020-03-09)];
  2. jormungandr 0.8.18 (HEAD-690eb547, release, linux [x86_64]) - [rustc 1.42.0 (b8cedc004 2020-03-09)]

To Reproduce
Steps to reproduce the behavior:

  1. Run node until get's stuck on same block
  2. Restart jormungandr and let it finish boostrapping
  3. Check logs of block announcement and check the time
  4. Run jcli rest v0 node stats get
  5. Check lastReceivedBlockTime keeps being with value '~'

Expected behavior
If your node receives a block announcement, seems that the property lastReceivedBlockTime should be updated.

Additional context

Jun 02 14:28:41.550 INFO connection closed, peer_addr: 5.252.226.161:28390, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:41.594 INFO accepted connection, peer_addr: 50.39.174.129:53428, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:41.630 INFO accepted connection, peer_addr: 95.216.212.162:4648, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:41.696 INFO connection closed, peer_addr: 95.216.212.162:4648, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:41.736 INFO disconnecting client, node_id: 27d71ef92f0cf3e515cdebdbe9f2b9554bb44f4961d6a200, peer_addr: 50.39.174.129:4002, task: network
Jun 02 14:28:41.885 INFO connection closed, peer_addr: 50.39.174.129:53428, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:41.971 INFO accepted connection, peer_addr: 95.216.210.17:65020, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:42.054 INFO connection closed, peer_addr: 95.216.210.17:65020, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:42.476 INFO accepted connection, peer_addr: 147.232.191.42:55066, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:42.645 INFO connection closed, peer_addr: 147.232.191.42:55066, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:42.728 INFO accepted connection, peer_addr: 23.96.214.121:41932, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:42.919 INFO connection closed, peer_addr: 23.96.214.121:41932, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.143 INFO accepted connection, peer_addr: 163.172.30.29:8456, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.184 INFO connection closed, peer_addr: 163.172.30.29:8456, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.219 INFO accepted connection, peer_addr: 51.154.18.152:54353, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.252 INFO accepted connection, peer_addr: 209.250.239.195:13080, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.278 INFO connection closed, peer_addr: 51.154.18.152:54353, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.285 INFO received block announcement from network, from_node_id: 0c9a21452fe80f4f28aadd1d52cdf1db15a58e4142822c07, date: 171.34653, parent: 07a25a3a02507682633d39baa3dbd76087eb5a9a7d5f4b62ee4faf1254a4ae85, hash: aa6d7fca124e7d1f46938807f9c52319fab50833761a531610942edf6c1b57a8, task: block
Jun 02 14:28:43.286 INFO connection closed, peer_addr: 209.250.239.195:13080, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.368 INFO accepted connection, peer_addr: 49.12.1.134:3050, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.409 INFO connection closed, peer_addr: 49.12.1.134:3050, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.439 INFO accepted connection, peer_addr: 188.165.210.69:16278, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.459 INFO connection closed, peer_addr: 188.165.210.69:16278, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.643 INFO accepted connection, peer_addr: 54.39.157.224:40422, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.670 INFO accepted connection, peer_addr: 5.252.224.229:63328, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.692 INFO accepted connection, peer_addr: 149.28.62.209:49458, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.728 INFO connection closed, peer_addr: 5.252.224.229:63328, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.777 INFO accepted connection, peer_addr: 209.250.239.195:13184, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.800 INFO connection closed, peer_addr: 54.39.157.224:40422, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.814 INFO connection closed, peer_addr: 209.250.239.195:13184, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.833 INFO received block announcement from network, from_node_id: 0e736f25e3f1e15dba01cc6c25ed1ef495b7991f715d5114, date: 171.34653, parent: 07a25a3a02507682633d39baa3dbd76087eb5a9a7d5f4b62ee4faf1254a4ae85, hash: aa6d7fca124e7d1f46938807f9c52319fab50833761a531610942edf6c1b57a8, task: block
Jun 02 14:28:43.833 INFO connection closed, peer_addr: 149.28.62.209:49458, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.836 INFO accepted connection, peer_addr: 85.144.242.193:39674, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:43.892 INFO connection closed, peer_addr: 85.144.242.193:39674, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:44.606 INFO accepted connection, peer_addr: 202.92.217.26:25014, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:44.839 INFO accepted connection, peer_addr: 157.245.73.37:59326, local_addr: 0.0.0.0:3000, task: network
Jun 02 14:28:44.872 INFO connection closed, peer_addr: 157.245.73.37:59326, local_addr: 0.0.0.0:3000, task: network
[2/06/20 2:28:44] ➜  ~ getNodeStats
---
blockRecvCnt: 0
lastBlockContentSize: 0
lastBlockDate: "171.34596"
lastBlockFees: 0
lastBlockHash: b7af91b6c4959a9b84bec9760cc9429095b8c74fe595b7b4f38f221edae30d19
lastBlockHeight: "625781"
lastBlockSum: 0
lastBlockTime: "2020-06-02T14:26:49+00:00"
lastBlockTx: 0
lastReceivedBlockTime: ~
nodeId: 6f5b4432f7b8cb82e4dd3c894cd2cc7488a86b4703c4bec5
peerAvailableCnt: 1723
peerConnectedCnt: 53
peerQuarantinedCnt: 197
peerTotalCnt: 1927
peerUnreachableCnt: 7
state: Running
txRecvCnt: 0
uptime: 71
version: jormungandr 0.8.18-690eb547
@dkijania
Copy link
Contributor

dkijania commented Jun 8, 2020

I have the same observations but using REST api only. Looks like stats fields with last prefix are not updated for both passive and leader node. See PR with reproduced issue: #2334

@dkijania dkijania added automated bug Something isn't working subsys-rest issues or PRs for the REST interface labels Jun 8, 2020
@dkijania
Copy link
Contributor

dkijania commented Jun 8, 2020

and this: #2333

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
automated bug Something isn't working subsys-rest issues or PRs for the REST interface
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@acewf @dkijania