You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be good if users that run into issues could use an ethd command to print out debug issue, to copy paste into ethstaker Discord.
Things like git commit id, if the git dir is tainted, docker version, ownership of the eth-docker dir
whether ext network is being used, which network it points to, whether that exists; .env ownership, prometheus and SSV ownership, is SSV dkg configured to point to the current repo and is its config file correct for 3.x, choice config parameters such as ports and _node variables and relevant targets as per compose file …
Is Erigon v2 or v3 target, is the DB v2 or v3
Basic info as well as migration info while relevant; with migration info removed 1 month after hardforks.
The text was updated successfully, but these errors were encountered:
It'd be good if users that run into issues could use an ethd command to print out debug issue, to copy paste into ethstaker Discord.
Things like git commit id, if the git dir is tainted, docker version, ownership of the eth-docker dir
whether ext network is being used, which network it points to, whether that exists; .env ownership, prometheus and SSV ownership, is SSV dkg configured to point to the current repo and is its config file correct for 3.x, choice config parameters such as ports and _node variables and relevant targets as per compose file …
Is Erigon v2 or v3 target, is the DB v2 or v3
Basic info as well as migration info while relevant; with migration info removed 1 month after hardforks.
The text was updated successfully, but these errors were encountered: