Try   HackMD

DAppNode EthMultiClient testing - Update with core hash

Who did this test?

wimel
18-04-2020

Intro

  • All checkboxes should be ticked for a successful test.
  • All empty code boxes should be filled with an answer
  • If anything does not look as expected, take screenshots, record a video or paste logs. This guide is in a hackmd so you can add as much info about the test result as you need
    • Add captures in-place with hackmd's native "Insert image"
    • Add brief logs (less than 10 lines) or question answers in place between triple back ticks ```
    • Add bigger logs in a pastebin.com and add the link in-place with a brief description of it
    • Add videos in an open, free, no-sign in platform such as streamable.com

1. Prepare test

1.1 DAppNode's versions

Paste your DAppNode's versions, from /support/report

Core DAppNode Packages versions
ethchain.dnp.dappnode.eth: 0.2.20
wifi.dnp.dappnode.eth: 0.2.0
dappmanager.dnp.dappnode.eth: 0.2.24, commit: ab83eca5
vpn.dnp.dappnode.eth: 0.2.4, commit: 1873bf3d
ethforward.dnp.dappnode.eth: 0.2.3
ipfs.dnp.dappnode.eth: 0.2.4
core.dnp.dappnode.eth: 0.2.26
admin.dnp.dappnode.eth: 0.2.15, commit: 66299094
wamp.dnp.dappnode.eth: 0.2.0
bind.dnp.dappnode.eth: 0.2.1
System info
docker version: Docker version 18.09.8-ce, build 0dd43dd87fd530113bf44c9bba9ad8b20ce4637f
docker compose version: docker-compose version 1.24.1, build 4667896b
Disk usage: 51%

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

1.2 Record ETHCHAIN status

Such as Synced #9171621 or Syncing 73512/9165251

INFO [04-18|11:58:01.611] Imported new chain segment               blocks=1    txs=188  mgas=9.970   elapsed=217.792ms mgasps=45.778   number=9896303 hash=5d60bc…fe6041 dirty=1022.92MiB

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

1.3 Pre-test checklist

  • DNP_ETHCHAIN is installed, running, and set to GETH

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

  • Geth DNP is not installed

  • DAPPMANAGER version is <= 0.2.24

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

  • ADMIN version is <= 0.2.15

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

  • Your DAppNode has NOT had any new multi-client branch version installed

    • If yes: Reach out to Lion to clean your local DB
    • If you can't do that, do the test in a clean DAppNode

2. Do test

  • Install new core package by hash
    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

Before the upgrades and to provide max information about the upgrade process these are some warnings

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

  • Record resulting DAppNode version again from /support/report
Core DAppNode Packages versions
dappmanager.dnp.dappnode.eth: 0.2.25, branch: HEAD, commit: 4141cf30
vpn.dnp.dappnode.eth: 0.2.5
bind.dnp.dappnode.eth: 0.2.2
core.dnp.dappnode.eth: 0.2.27
admin.dnp.dappnode.eth: 0.2.16, branch: heads/v0.2.16, commit: db1e7612
wifi.dnp.dappnode.eth: 0.2.0
ethforward.dnp.dappnode.eth: 0.2.3
ipfs.dnp.dappnode.eth: 0.2.4
wamp.dnp.dappnode.eth: 0.2.0
System info
docker version: Docker version 18.09.8-ce, build 0dd43dd87fd530113bf44c9bba9ad8b20ce4637f
docker compose version: docker-compose version 1.24.1, build 4667896b
Disk usage: 51%

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

  • Make sure the migration logs are correct. DAPPMANAGER logs should include (in order)
Removed ETHCHAIN package
Migrated ETHCHAIN Geth data volume
Migrated ETHCHAIN Identity volume
Deleted ETHCHAIN Geth data volume
Deleted ETHCHAIN Identity volume
Migrated ETHCHAIN

  • Make sure DNP_ETHCHAIN is not installed. It should no be in UI's view /packages system tab

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

  • Make sure Geth is installed. It should be in UI's view /packages

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

  • Make sure the volume migration was correct

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

  • Sync status should be the same. Compare with the sync status you recorded earlier

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

  • Go to /installer and make sure packages load from the remote server

    Image Not Showing Possible Reasons
    • The image file may be corrupted
    • The server hosting the image is unavailable
    • The image path is incorrect
    • The image format is not supported
    Learn More →

Some information and problems during the upgrade process:

On the first try to update can't update all packages and I need to force the upgrade again, the test is do it using the VPN client in remote mode using the web interface of DappNode.

On system/repository I can see a new "tab" Repository, with this I can check that the upgrade is correct.

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

On system/info I can see some "red" alerts I share the screen with the info.

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

Takes a little time to sync again the node when the upgrade is finish, we can see the logs of Geth under /packages/geth.dnp.dappnode.eth/logs

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

I can check that I'm using the new option of DappNode and is using "remote" server until my node is totally sync

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

Last changed by 
 
wimel
Head behind DelegaNetworks, heart behind ColmenaLabs_svq.
0
321

Read more

Untitled

Tests DAppNode Geth+Nimbus Goerli Geth Hash: http://my.dappnode/#/installer/%2Fipfs%2FQmYcLwW5bcUJ2ur3yBawgMVYJEcG1bEbTjTjJ16rsAUXKH Version: 0.2.43 /ipfs/QmYcLwW5bcUJ2ur3yBawgMVYJEcG1bEbTjTjJ16rsAUXKH Logs:

Sep 6, 2022
Untitled

Distribution: [ ] Lighthouse+Nethermind = Wimel, Carlos (DAppNodeOVH02) [ ] Prysm+Erigon = Luka, Carlos [ ] Nimbus+Geth = Wimel, Marce [ ] Teku+Geth = Luka, Marce Distribution of Backups: [ ] Prysm+Nethermind = Voss

Sep 2, 2022
Peers for Sentinel testnet, AKA Bluenet

Github repo DelegaNetworks 7bc7ff12d43cd1f3cc575f6fac8ba28950efa608@49.12.206.250:26656 DragonStake 8cafbfbf541ec5757c5fd6bdac219ab2f06b38a2@95.216.241.248:26656 qf3l3k de7112da3d76ea51917f6754fed37386acbf23dd@65.21.232.149:26696

Sep 11, 2021
Flags para el nodo de Avalanche

./avalanchego --help Usage of ./avalanchego/build/avalanchego: --api-admin-enabled If true, this node exposes the Admin API --api-auth-password-file string Password file used to initially create/validate API authorization tokens. Leading and trailing whitespace is removed from the password. Can be changed via API call. --api-auth-required Require authorization token to call HTTP APIs --api-health-enabled If true, this node exposes the Health API (default true) --api-info-enabled If true, this node exposes the Info API (default true) --api-ipcs-enabled If true, IPCs can be opened --api-keystore-enabled If true, this node exposes the Keystore API (default true)

Apr 20, 2021
Read more from wimel
Published on HackMD