From 155738f30ca39b80957a420005a4680b07b5f505 Mon Sep 17 00:00:00 2001 From: Florian Sey Date: Tue, 31 Jan 2023 03:06:21 +0100 Subject: [PATCH] doc: fix typo and command in geth documentation (#26577) This PR fixes a typo and an invalid command in doc. Co-authored-by: Florian Sey --- docs/fundamentals/logs.md | 2 +- docs/fundamentals/private-network.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/fundamentals/logs.md b/docs/fundamentals/logs.md index b3f4fe6abe..df04a80aec 100644 --- a/docs/fundamentals/logs.md +++ b/docs/fundamentals/logs.md @@ -5,7 +5,7 @@ description: Geth's log messages explained A Geth node continually reports messages to the console allowing users to monitor Geth's current status in real-time. The logs indicate when Geth is running normally and indicates when some attention is required. However, reading these logs can be difficult for new users. This page will help to interpret the log messages to better understand what Geth is doing. -Note that there are a large number of log messages covering a wide range of possible scenarios for a Geth node. This page will only address a subset of commonly seen messages. For more, see the [Geth GitHub](https://github.com/ethereum/go-ethereum), [Discord](https://discord.gg/WHNkYDsAKU) or search on [ethereum.stackexchange](https://ethereum.stackexchange.com/). Log messages are usually sufficiently self-descrining that they do not require additional explanation. +Note that there are a large number of log messages covering a wide range of possible scenarios for a Geth node. This page will only address a subset of commonly seen messages. For more, see the [Geth GitHub](https://github.com/ethereum/go-ethereum), [Discord](https://discord.gg/WHNkYDsAKU) or search on [ethereum.stackexchange](https://ethereum.stackexchange.com/). Log messages are usually sufficiently self-describing that they do not require additional explanation. ## Configuring log messages {#configuring-log-messages} diff --git a/docs/fundamentals/private-network.md b/docs/fundamentals/private-network.md index 51556719b5..ed002f2876 100644 --- a/docs/fundamentals/private-network.md +++ b/docs/fundamentals/private-network.md @@ -162,7 +162,7 @@ geth --datadir data --networkid 15 --nat extip:172.16.254.4 The 'node record' of the bootnode can be extracted using the JS console: ```sh -geth attach data/geth.ipc --exec admin.nodeInfo.enr +geth attach --exec admin.nodeInfo.enr data/geth.ipc ``` This command should print a base64 string such as the following example. Other nodes will use the information contained in the bootstrap node record to connect to the peer-to-peer network.