Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Lock up of a node (^C didn't kill node and stuck) #3577

@pepyakin

Description

@pepyakin

When I launched substrate-node like this

./target/release/substrate purge-chain --dev -y && ./target/release/substrate --dev

and 2 seconds in pressed ^C the node stuck and didn't react to successive presses to ^C.

Here is the log:

2019-09-09 14:13:58 Running in --dev mode, RPC CORS has been disabled.
2019-09-09 14:13:58 Substrate Node
2019-09-09 14:13:58   version 2.0.0-9b08e7ff9-x86_64-macos
2019-09-09 14:13:58   by Parity Technologies, 2017-2019
2019-09-09 14:13:58 Chain specification: Development
2019-09-09 14:13:58 Node name: guiltless-rabbits-7477
2019-09-09 14:13:58 Roles: AUTHORITY
2019-09-09 14:13:58 Initializing Genesis block/state (state: 0x6936…4cdf, header-hash: 0x136d…dc4d)
2019-09-09 14:13:58 Loading GRANDPA authority set from genesis on what appears to be first startup.
2019-09-09 14:13:58 Loaded block-time = BabeConfiguration { slot_duration: 3000, c: (1, 4), median_required_blocks: 1000 } seconds from genesis on first-launch
2019-09-09 14:13:58 Creating empty BABE epoch changes on what appears to be first startup.
2019-09-09 14:13:58 Highest known block at #0
2019-09-09 14:13:58 Using default protocol ID "sup" because none is configured in the chain specs
2019-09-09 14:13:58 Local node identity is: QmVeMbzc1SAP42ciC5n43Mt7hHhZFqMmpCA2T7ibVpW34s
2019-09-09 14:13:58 Failed to put hash 'Key(b"\x12 F \x87\x98\xc8\x0b\xe6S\x1cjdT1-\xb7\xd1PYb7k<\xca\x16\xcd\x18\xf9\x10\xd6\xfe\xa8^")' on Dht.
2019-09-09 14:14:00 Starting consensus session on top of parent 0x136d414e651ca6f64152171a6529674de33262074e2139b1f7c405a340a4dc4d
2019-09-09 14:14:00 Prepared block for proposing at 1 [hash: 0x5e7185150735b2f8ee3ef24e1831a9e7e77b0d9586115e08df4bbcd34ab1c072; parent_hash: 0x136d…dc4d; extrinsics: [0xf44f…41b1]]
2019-09-09 14:14:00 Pre-sealed block for proposal at 1. Hash now 0x51291f978318d98746721e6a03e8991c08fa9ba2c73d9f3da94af18358e1dde0, previously 0x5e7185150735b2f8ee3ef24e1831a9e7e77b0d9586115e08df4bbcd34ab1c072.
2019-09-09 14:14:00 Imported #1 (0x5129…dde0)
2019-09-09 14:14:00 Submitting to the pool: 031200010000008c8812206c8aec03028ab43f0a560a80799d859ad57a45efe4a074cd1aa65a6fd6c3be20000000000000000000ba44ada9f7b4404a62bdf38cc366e6fd93f96eaff23cf67f72a80bf2f35f1e59498ce3999412cd6e1be819fd4205023e6ea79ddd7605d0e109d6211a2b12368e (isSigned: None)
^C

Reproduces quite consistently for me

Metadata

Metadata

Assignees

No one assigned

    Labels

    I3-bugThe node fails to follow expected behavior.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions