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.

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

Improve consensus logs after system failure #708

Open
DmytroNazarenko opened this issue Dec 16, 2022 · 0 comments
Open

Improve consensus logs after system failure #708

DmytroNazarenko opened this issue Dec 16, 2022 · 0 comments

Comments

@DmytroNazarenko
Copy link
Contributor

To improve investigate of future problems suggesting to add more information when schain completely stuck:
[2022-12-01 23:04:17.799] [3:main] [info] 245642:IO:Got ping
[2022-12-01 23:04:18.967] [3:main] [info] 245642:IO:Got ping
[2022-12-01 23:04:24.311] [3:main] [info] 245642:Stuck check Could not connect to 2/3 of nodes. Will not restart
[2022-12-01 23:04:27.313] [3:main] [info] 245642:Stuck detected. Checking network connectivity ...
[2022-12-01 23:04:27.910] [3:main] [info] 245642:IO:Got ping
[2022-12-01 23:04:29.817] [3:main] [info] 245642:IO:Got ping

Suggestion:
If consensus can't connect to 2/3 of nodes, print IP/port of tihis nodes.

@kladkogex kladkogex self-assigned this Jul 21, 2023
@kladkogex kladkogex added this to the 2.3 milestone Jul 21, 2023
@DmytroNazarenko DmytroNazarenko removed this from the 2.3 milestone Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants