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

v5.40.0, double initialization issue on Shiden #1277

Closed
crypto-pithecus opened this issue Jun 22, 2024 · 5 comments
Closed

v5.40.0, double initialization issue on Shiden #1277

crypto-pithecus opened this issue Jun 22, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@crypto-pithecus
Copy link

crypto-pithecus commented Jun 22, 2024

Description

With the latest release v5.40.0, the Shiden backup node keeps failing with 'Double initialization' error message. The same error message was observed even with a new sync of Shiden DB. This backup node is running without any issue at this moment with v5.39.1.

Steps to Reproduce

  1. Execute the following
sudo apt update
sudo apt upgrade -y
git clone https://github.com/AstarNetwork/Astar.git
  1. Generate the binary
cd ~/Astar
CARGO_PROFILE_RELEASE_LTO=true RUSTFLAGS="-C codegen-units=1" cargo build --release
  1. Stop the service, update the binary under /usr/local/bin, and restart the service

  2. See error

Expected vs. Actual Behavior

Sync and run without any errors

Environment

Ubuntu 20.04
A backup node

  • Operating system: Ubuntu 20.04
  • Project version/tag: v5.40.0
  • Rust version (run rustup show):
Default host: x86_64-unknown-linux-gnu
rustup home:  /root/.rustup

installed toolchains
--------------------

stable-x86_64-unknown-linux-gnu (default)
nightly-x86_64-unknown-linux-gnu
1.73.0-x86_64-unknown-linux-gnu

active toolchain
----------------

stable-x86_64-unknown-linux-gnu (default)
rustc 1.79.0 (129f3b996 2024-06-10)

Logs, Errors or Screenshots

2024-06-21 21:36:18 [Relaychain] double initialization
2024-06-21 21:36:18 [Parachain] Essential task `aura` failed. Shutting down service.
2024-06-21 21:36:18 [Relaychain] subsystem exited with error subsystem="dispute-coordinator" err=FromOrigin { origin: "dispute-coordinator", source: SubsystemReceive(Generated(Context("Signal channel is terminated and empty."))) }
Error: Service(Other("Essential task failed."))

or

2024-06-22 00:12:12 [Relaychain] double initialization
2024-06-22 00:12:12 [Parachain] Essential task `aura` failed. Shutting down service.
2024-06-22 00:12:12 [Relaychain] subsystem exited with error subsystem="runtime-api" err=Generated(Context("Signal channel is terminated and empty."))

Additional Information

This error message kept being displayed and the node kept being restarted.
Feel free to change the label on this issue, I just used one of the templates.

@crypto-pithecus crypto-pithecus added the bug Something isn't working label Jun 22, 2024
@ermalkaleci
Copy link
Contributor

Either use binaries from release https://github.com/AstarNetwork/Astar/releases/tag/v5.40.0
Or to build from latest release commit 004040baad84e3ea811ee2b990ded2edda96fffa

@crypto-pithecus
Copy link
Author

crypto-pithecus commented Jun 23, 2024

Thanks! As the node is running on Ubuntu 20.04, using binaries might not be an option, so I compiled it from the repository. I just have checked that the f05bed0 commit
f05bed0. Let me check if this error still is reproducible with the v5.40.0 release commit.

Reopened the issue as accidentally clicked "close issue".

@ermalkaleci
Copy link
Contributor

ermalkaleci commented Jun 23, 2024

That commit had the bug. Don't use master next time as master has ongoing development/features. Always make sure to point to latest tag

@ermalkaleci
Copy link
Contributor

The bug is already fixed #1272

@crypto-pithecus
Copy link
Author

Thanks! Normally I do compile it with the official latest release rather than one in development. Let me double check from next time, thanks!

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

No branches or pull requests

2 participants