v5.40.0, double initialization issue on Shiden

[crypto-pithecus]

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

2. Generate the binary

   cd ~/Astar
   CARGO_PROFILE_RELEASE_LTO=true RUSTFLAGS="-C codegen-units=1" cargo build --release

3. Stop the service, update the binary under /usr/local/bin, and restart the service

4. 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.

[ermalkaleci]

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]

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 https://github.com/AstarNetwork/Astar/commit/f05bed0c65b656fae2002137b7928d33fa1c4484. 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]

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]

The bug is already fixed https://github.com/AstarNetwork/Astar/pull/1272

[crypto-pithecus]

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