status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

update faq and add example to systemd (#2645)

This commit is contained in:
0xmiel 2021-06-11 13:56:15 +02:00 committed by GitHub
parent 042600a134
commit f2588be9ab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/the_nimbus_book/src/beacon-node-systemd.md
View File

@ -74,3 +74,7 @@ sudo journalctl -u nimbus-eth2-prater.service --since yesterday
``` ```
For more options, see [here](https://www.raspberrypi.org/documentation/linux/usage/systemd.md). For more options, see [here](https://www.raspberrypi.org/documentation/linux/usage/systemd.md).
## Further examples
- [A systemd service file](https://github.com/chfast/ethereum-node/blob/main/nimbus%40.service) by Pawel Bylica which allows you to start two services at the same time: e.g. `nimbus@prater.service` and `nimbus@mainnet.service`.

16
docs/the_nimbus_book/src/faq.md
View File

@ -2,6 +2,20 @@
## Nimbus ## Nimbus
### How do I fix the discovered new external address warning log?
```
WRN 2021-03-15 02:23:37.569+00:00 Discovered new external address but ENR auto update is off topics="discv5"...
```
It's possible that your ISP has changed your IP address without you knowing.
The first thing to do it to try relaunching the beacon node with with `--enr-auto-update:true` (pass it as an option in the command line).
If this doesn't fix the problem, the next thing to do is to check your external (public) IP address and detect open ports on your connection - you can use [https://www.yougetsignal.com/tools/open-ports/](https://www.yougetsignal.com/tools/open-ports/ ). Note that Nimbus `TCP` and `UDP` ports are both set to `9000` by default.
See [here](./health.md#set-up-port-forwarding), for how to set up port forwarding.
### Why are metrics not working? ### Why are metrics not working?
The metrics server is disabled by default, enable it by passing `--metrics` to the run command: The metrics server is disabled by default, enable it by passing `--metrics` to the run command:
@ -28,7 +42,7 @@ We recommend [running a Nimbus beacon node](./quick-start.md) on [Prater](./prat
To stress test it, `add--subscribe-all-subnets` to the [beacon node options](./options.md). This represents more or less the maximum load you could have on eth2. To stress test it, `add--subscribe-all-subnets` to the [beacon node options](./options.md). This represents more or less the maximum load you could have on eth2.
# How do I add an additional validator? ### How do I add an additional validator?
To add an additional validator, just follow [the same steps](./keys.md) as you did when you added your first. You'll have to restart the beacon node for the changes to take effect. To add an additional validator, just follow [the same steps](./keys.md) as you did when you added your first. You'll have to restart the beacon node for the changes to take effect.