substrate-docs
substrate-docs copied to clipboard
difference of the displaying information while following tutorials to build a local chain
the tutorial show the info below 2021-11-24 15:36:35 Running in --dev mode, RPC CORS has been disabled. 2021-11-24 15:36:35 Substrate Node 2021-11-24 15:36:35 ✌️ version 4.0.0-dev-82b7c2c-aarch64-macos 2021-11-24 15:36:35 ❤️ by Substrate DevHub https://github.com/substrate-developer-hub, 2017-2021 2021-11-24 15:36:35 📋 Chain specification: Development 2021-11-24 15:36:35 🏷 Node name: six-wash-9274 2021-11-24 15:36:35 👤 Role: AUTHORITY 2021-11-24 15:36:35 💾 Database: RocksDb at /tmp/substrateP1jD7H/chains/dev/db 2021-11-24 15:36:35 ⛓ Native runtime: node-template-100 (node-template-1.tx1.au1) 2021-11-24 15:36:35 🔨 Initializing Genesis block/state (state: 0xa59b…5331, header-hash: 0xc5d2…37f3) 2021-11-24 15:36:35 👴 Loading GRANDPA authority set from genesis on what appears to be first startup. 2021-11-24 15:36:35 ⏱ Loaded block-time = 6s from block 0xc5d2fdad35e14684753f087c1a20f022274e154d39add4f7efe34e95476a37f3 2021-11-24 15:36:35 Using default protocol ID "sup" because none is configured in the chain specs 2021-11-24 15:36:35 🏷 Local node identity is: 12D3KooWG5niQF5bjsFao3D8DZRpUUB6uWZC2pK8hCDZ94zsr8Sc 2021-11-24 15:36:35 📦 Highest known block at #0 ... ... ... 2021-11-24 15:36:40 💤 Idle (0 peers), best: #1 (0xd2b5…d03f), finalized #0 (0xc5d2…37f3), ⬇ 0 ⬆ 0
But when I use the command I only get the info below
./target/release/node-template --dev
2022-07-23 20:03:29 〽️ Prometheus exporter started at 127.0.0.1:9615
2022-07-23 20:03:30 🙌 Starting consensus session on top of parent 0xf0176440a52e6c0998a49bf4ef263baa061245d97d653e9831c4db0308aef22e
2022-07-23 20:03:30 🎁 Prepared block for proposing at 1 (1 ms) [hash: 0xb0d3cb165d089f6b5cd187534ff4e46f6d8fe994ec1c5c65c70580b0df5ec4bd; parent_hash: 0xf017…f22e; extrinsics (1): [0x8e73…8af4]]
2022-07-23 20:03:30 🔖 Pre-sealed block for proposal at 1. Hash now 0x66f99f33cfd26aac6a6d37ecfceb55491ea899e3cc5e8321bfa4cd06dd0c3067, previously 0xb0d3cb165d089f6b5cd187534ff4e46f6d8fe994ec1c5c65c70580b0df5ec4bd.
2022-07-23 20:03:30 ✨ Imported #1 (0x66f9…3067)
2022-07-23 20:03:34 💤 Idle (0 peers), best: #1 (0x66f9…3067), finalized #0 (0xf017…f22e), ⬇ 0 ⬆ 0
2022-07-23 20:03:36 🙌 Starting consensus session on top of parent 0x66f99f33cfd26aac6a6d37ecfceb55491ea899e3cc5e8321bfa4cd06dd0c3067
2022-07-23 20:03:36 🎁 Prepared block for proposing at 2 (0 ms) [hash: 0x28a32139004fe07f28251148092680810dbbc257348e3f29cd4f3bb30657b8e5; parent_hash: 0x66f9…3067; extrinsics (1): [0x5068…a856]]
2022-07-23 20:03:36 🔖 Pre-sealed block for proposal at 2. Hash now 0x83ca664157405295e2c11f158982023d681b43a17fb22da67f41ca962a2e0845, previously 0x28a32139004fe07f28251148092680810dbbc257348e3f29cd4f3bb30657b8e5.
@jiyidefeng1990 , I can't reproduce this issue. Can you provide additional information? Maybe it is an environment issue? Are you able to run the node bit just concerned that the log messages are different or are you unable to run the node template?