| #! /bin/bash | |
| # http://linuxcommand.org/wss0150.php | |
| function error_exit | |
| { | |
| echo "$1" 1>&2 | |
| exit 1 | |
| } | |
| # http://unix.stackexchange.com/questions/70859/why-doesnt-sudo-su-in-a-shell-script-run-the-rest-of-the-script-as-root |
So a FOSS project might have signed releases with a GPG sig. How do you verify it on a Linux machine?
Example sigp/lighthouse, but same idea for any project.
Install gpg: sudo apt install gpg
Grab their PGP key ID from their download page and
gpg --keyserver pgp.mit.edu --recv THEIRKEYID and wait
A typical user of eth-docker is someone who wants to become a validator on the Ethereum network, also known as staking or staker, or someone who is already a validator on the Ethereum network and wants to add more validators to their setup. They can be someone who is going to setup their machine at home, someone who is going to use some kind of VPS to host their setup, or some kind of institutional staker working for large staking services or large investors.
eth-docker is an automation wrapper to run an "Ethereum node", consisting of a consensus layer client, execution layer client, and validator client.
I was looking after a Dell PowerEdge R420 server with a hardware RAID card in it, a PERC8 H710P Mini. Connected to this were two WD Blue 3D NAND SATA SSDs in RAID-1, that were handling a write-intensive database: Geth, in this case.
After 11 months of running without problems, I had reason to "resync" Geth, and the server could not keep up with the required IOPS.
Symptoms were Database compacting, degraded performance messages for hours, without recovery, and read/write latency in excess of 20/70ms,
as measured by sudo iostat -mdx and its r_await and w_await data.
The cause of this was that the RAID controller does not support TRIM on the SSD, and the SSD's performance degraded over time because of it.
From Server Control Panel
Note: PBSS in Geth >=1.13.0 removes the need to prune manually.
Geth (Go-Ethereum) as of July 2022 takes about 650 GiB of space on a fast/snap sync, and then grows by ~ 14 GiB/week with default cache, ~ 8 GiB/week with more cache.
Besu, an Ethereum execution layer client, can be optimized for minimal database growth (7-8 GiB/week), and for block processing speed.
The relevant parameter is --Xbonsai-limit-trie-logs-enabled=true
If you have 64 GiB of RAM or more, you can also add --Xplugin-rocksdb-high-spec-enabled=true for even better performance.
A long-running Besu DB will have sizeable trie log storage. This can be reduced with a one-off prune using the
To start, read the official release notes.
If your install fits into "vanilla Debian plus maybe a handful of 3rd-party repos", then this guide for a simple upgrade to Debian 12 "bookworm" from Debian 11 "bullseye" can be helpful. 3rd-party repos are handled with a find command.
Note upgrade is only supported from Debian 11 to Debian 12. If you are on Debian 10, upgrade to Debian 11 first and make sure to change the security repo as per the release notes. Then once on Debian 11, you can upgrade to Debian 12.
This has not been tested, and is a placeholder for instructions when Debian 13 is released in 2025
To start, read the official release notes.
If your install fits into "vanilla Debian plus maybe a handful of 3rd-party repos", then this guide for a simple upgrade to Debian 13 "trixie" from Debian 12 "bookworm" can be helpful. 3rd-party repos are handled with a find command.
Note upgrade is only supported from Debian 12 to Debian 13. If you are on Debian 11, upgrade to Debian 12 first. Then once on Debian 12, you can upgrade to Debian 13.
This is a placeholder for the 15th August 2024 release of Ubuntu 24.04.1
To start, read the official release notes.
If your install fits into "vanilla Ubuntu plus maybe a handful of 3rd-party repos", then this guide for a simple upgrade to Ubuntu 24.04 "Noble Numbat" from Ubuntu 22.04 "Jammy Jellyfish" can be helpful. 3rd-party repos are handled with a find command.