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

Unexpected shut down of retired stake pool #2800

Closed
dkijania opened this issue Dec 4, 2020 · 2 comments · Fixed by #2815
Closed

Unexpected shut down of retired stake pool #2800

dkijania opened this issue Dec 4, 2020 · 2 comments · Fixed by #2815
Labels
A-tests Area: Tests automated bug Something isn't working

Comments

@dkijania
Copy link
Contributor

dkijania commented Dec 4, 2020

Describe the bug
For topology like below:
image

when send retire stake pool certificate for leader3, node unexpectedly is shutdown.
Logs:
retire_stake_pool_explorer.zip

Mandatory Information

  1. jcli --full-version output;
  2. jormungandr --full-version output;

To Reproduce
cargo run -- --scenario retire_stake_pool_explorer --root-dir retire_stake --document

@dkijania dkijania added bug Something isn't working subsys-network network related A-tests Area: Tests automated labels Dec 4, 2020
@mzabaluev mzabaluev added subsys-mempool all that touch the mem pool or fragements and removed subsys-mempool all that touch the mem pool or fragements subsys-network network related labels Dec 10, 2020
@mzabaluev
Copy link
Contributor

The root cause is a panic also observed in #2147.

This issue, then, is about improving the diagnostics so that the cause of shutting down is reflected in the logs.

@eugene-babichenko
Copy link
Contributor

With #2812 it outputs a proper error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-tests Area: Tests automated bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants