Dappnode and Pyrmont errors

AJR · 24 November 2020 18:13

Hi guys,

I’ve installed and am attempting to run the latest Pyrmont package. Some feedback on my experience and some errors I need assistance with.

After installing the Pyrmont package it asks to enter “Wallet Password”. My assumption is you aren’t referring to the Validator keystore password when you go through the Eth 2.0 Launchpad onboarding process? This is a new password? Please confirm.
In the Pyrmont Validator logs I am seeing the following

Type “accept” to accept this terms and conditions [accept/decline]:e[0m (e[92mdefaulte[0m: decline):
time=“2020-11-24 14:17:02” level=error msg=“Could not scan text input, if you are trying to run in non-interactive environment, you
can use the --accept-terms-of-use flag after reading the terms and conditions here:
prysm/TERMS_OF_SERVICE.md at master · prysmaticlabs/prysm · GitHub” prefix=main
e[1m
Prysmatic Labs Terms of Use

By downloading, accessing or using the Prysm implementation (“Prysm”), you (referenced herein
as “you” or the “user”) certify that you have read and agreed to the terms and conditions below.

TERMS AND CONDITIONS: prysm/TERMS_OF_SERVICE.md at master · prysmaticlabs/prysm · GitHub

Is that normal?

I can’t reach “http://prysm-pyrmont.dappnode/”
I’m getting the following errors in the DappManager Logs??

INFO [api/logger:19] RPC success rebootHost
INFO [db/dbFactory:11] New DB instance at /usr/src/app/DNCORE/maindb.json
INFO [db/dbFactory:11] New DB instance at /usr/src/app/DNCORE/dappmanagerdb.json
INFO [ethForward:59] IPFS redirect set to: http://ipfs.dappnode:8080/ipfs/
INFO [ethForward:60] SWARM redirect set to: http://swarm.dappnode
INFO [index:45] Version info { version: ‘0.2.35’,
branch: ‘master’,
commit: ‘cbd7cbcf3e155f0dd7e9e969ee37b431fb916819’ }
INFO [modules/hostScripts/copyScripts:47] Successfully run copyHostScripts.
INFO [api:123] HTTP API 80
INFO [index:39] Host password is secure
INFO [modules/installer/restartPatch:187] No restart patch found, assuming a manual restart
INFO [modules/legacy/migrateLegacyEnvFiles:19] Finished migrating legacy DNP .env files if any
INFO [watchers/nsupdate:44] Successful initial nsupdate call for all DNPs
WARN [initializeDb:169] VPN DB not imported, vpndb.json missing.
ERROR [initializeDb:215] { Error: Error getting internal IP: Command failed: docker run --rm --net=host --entrypoint=/sbin/ip dappmanager.dnp.dappnode.eth:0.2.35 route get 1
ip: RTNETLINK answers: Network unreachable
at Object. (/usr/src/app/webpack:/src/utils/shell.ts:37:16)
at Generator.throw ()
at rejected (/usr/src/app/index.js:19333:65)
at process._tickCallback (internal/process/next_tick.js:68:7)
cmd:
‘docker run --rm --net=host --entrypoint=/sbin/ip dappmanager.dnp.dappnode.eth:0.2.35 route get 1’,
killed: false,
code: 2,
signal: null,
stdout: ‘’,
stderr: ‘ip: RTNETLINK answers: Network unreachable\n’ }
WARN [initializeDb:50] Internal IP is not available yet, retrying in 60 seconds
WARN [watchers/natRenewal:41] No UPnP device available
ERROR [watchers/autoUpdates:72] Error on clearCompletedCoreUpdatesIfAny { Error: dappGet could not resolve request core.dnp.dappnode.eth@, error on aggregate stage: Error: getaddrinfo EAI_AGAIN web3.dappnode.net web3.dappnode.net:443
at exports.XMLHttpRequest.request.onreadystatechange (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:85:1)
at exports.XMLHttpRequest.dispatchEvent (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:1)
at setState (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:1)
at exports.XMLHttpRequest.handleError (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:1)
at ClientRequest.errorHandler (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:1)
at ClientRequest.emit (events.js:189:13)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:189:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
statusCode: 0,
responseText:
‘Error: getaddrinfo EAI_AGAIN web3.dappnode.net web3.dappnode.net:443\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)’ }
(node:1) UnhandledPromiseRejectionWarning: Error: dappGet could not resolve request core.dnp.dappnode.eth@, error on aggregate stage: Error: getaddrinfo EAI_AGAIN web3.dappnode.net web3.dappnode.net:443
at exports.XMLHttpRequest.request.onreadystatechange (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:85:1)
at exports.XMLHttpRequest.dispatchEvent (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:1)
at setState (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:1)
at exports.XMLHttpRequest.handleError (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:1)
at ClientRequest.errorHandler (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:1)
at ClientRequest.emit (events.js:189:13)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:189:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:1) UnhandledPromiseRejectionWarning: Error: dappGet could not resolve request core.dnp.dappnode.eth@, error on aggregate stage: Error: getaddrinfo EAI_AGAIN web3.dappnode.net web3.dappnode.net:443
at exports.XMLHttpRequest.request.onreadystatechange (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:85:1)
at exports.XMLHttpRequest.dispatchEvent (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:1)
at setState (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:1)
at exports.XMLHttpRequest.handleError (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:1)
at ClientRequest.errorHandler (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:1)
at ClientRequest.emit (events.js:189:13)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:189:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
ERROR [watchers/autoUpdates:51] Error on updateSystemPackages { Error: dappGet could not resolve request core.dnp.dappnode.eth@, error on aggregate stage: Error: getaddrinfo EAI_AGAIN web3.dappnode.net web3.dappnode.net:443
at exports.XMLHttpRequest.request.onreadystatechange (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:85:1)
at exports.XMLHttpRequest.dispatchEvent (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:1)
at setState (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:1)
at exports.XMLHttpRequest.handleError (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:1)
at ClientRequest.errorHandler (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:1)
at ClientRequest.emit (events.js:189:13)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:189:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
statusCode: 0,
responseText:
‘Error: getaddrinfo EAI_AGAIN web3.dappnode.net web3.dappnode.net:443\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)’ }
(node:1) UnhandledPromiseRejectionWarning: Error: dappGet could not resolve request core.dnp.dappnode.eth@, error on aggregate stage: Error: getaddrinfo EAI_AGAIN web3.dappnode.net web3.dappnode.net:443
at exports.XMLHttpRequest.request.onreadystatechange (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:85:1)
at exports.XMLHttpRequest.dispatchEvent (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:1)
at setState (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:1)
at exports.XMLHttpRequest.handleError (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:1)
at ClientRequest.errorHandler (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:1)
at ClientRequest.emit (events.js:189:13)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:189:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
(node:1) UnhandledPromiseRejectionWarning: Error: dappGet could not resolve request core.dnp.dappnode.eth@, error on aggregate stage: Error: getaddrinfo EAI_AGAIN web3.dappnode.net web3.dappnode.net:443
at exports.XMLHttpRequest.request.onreadystatechange (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:85:1)
at exports.XMLHttpRequest.dispatchEvent (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:1)
at setState (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:1)
at exports.XMLHttpRequest.handleError (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:1)
at ClientRequest.errorHandler (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:1)
at ClientRequest.emit (events.js:189:13)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:189:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
Socket connected -Wfk3inKMKoT2iLUAAAA
Socket connected rphE9gF7znGsL9DJAAAB
(node:1) ExperimentalWarning: Readable[Symbol.asyncIterator] is an experimental feature. This feature could change at any time
INFO [modules/dyndns/generateKeys:35] Skipping keys generation, found identity in db
INFO [initializeDb:191] Updated local dyndns: ################HASHED OUT###############
(node:1) ExperimentalWarning: The dns.promises API is experimental
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Resolving dependencies…
INFO [calls/packageInstall:67] Resolved request { name: ‘prysm-pyrmont.dnp.dappnode.eth’, ver: ‘0.1.0’ } { ‘prysm-pyrmont.dnp.dappnode.eth’: ‘0.1.0’ }
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Starting download…
WARN [utils/validate:75] Parent path doesn’t exist, creating it: dnp_repo/prysm-pyrmont.dnp.dappnode.eth
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Verifying download…
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Package downloaded
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Loading image…
(node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Package Loaded
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Writing files…
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Starting package…
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Package started
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Cleaning files…
INFO [utils/logUi:25] Progress log prysm-pyrmont.dnp.dappnode.eth Cleaning previous images…
INFO [api/logger:19] RPC success packageInstall
INFO [watchers/nsupdate:42] nsupdate add [ ‘prysm-pyrmont.dnp.dappnode.eth’ ]
ERROR [watchers/natRenewal:79] Error openning port 32771 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 32771 32771 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32770 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 32770 32770 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32769 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 32769 32769 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32769 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 32769 32769 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32771 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 32771 32771 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32768 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 32768 32768 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32770 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 32770 32770 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32768 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 32768 32768 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 1194 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 1194 1194 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 8092 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 8092 8092 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 4001 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 4001 4001 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 4002 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.35 -e DAppNode -a 192.168.1.## 4002 4002 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:99] Port 32771 TCP is not open
ERROR [watchers/natRenewal:99] Port 32770 TCP is not open
ERROR [watchers/natRenewal:99] Port 32769 UDP is not open
ERROR [watchers/natRenewal:99] Port 32769 TCP is not open
ERROR [watchers/natRenewal:99] Port 32771 UDP is not open
ERROR [watchers/natRenewal:99] Port 32768 TCP is not open
ERROR [watchers/natRenewal:99] Port 32770 UDP is not open
ERROR [watchers/natRenewal:99] Port 32768 UDP is not open
ERROR [watchers/natRenewal:99] Port 1194 UDP is not open
ERROR [watchers/natRenewal:99] Port 8092 TCP is not open
ERROR [watchers/natRenewal:99] Port 4001 TCP is not open
ERROR [watchers/natRenewal:99] Port 4002 UDP is not open

uPnP is enbaled on my router

any advice appreciated.
AJ

AJR · 25 November 2020 14:13

Any thoughts on the errors here guys?
I have re-installed Dappnode from the iso and have only installed the DMS package, plus going the through the process of synching Geth and I am getting these errors in the DappManager logs.

ERROR [watchers/natRenewal:71] Error openning port 32768 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.33 -e DAppNode -a 192.168.1.## 32768 32768 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:71] Error openning port 32769 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.33 -e DAppNode -a 192.168.1.## 32769 32769 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:71] Error openning port 32768 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.33 -e DAppNode -a 192.168.1.## 32768 32768 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:71] Error openning port 1194 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.33 -e DAppNode -a 192.168.1.## 1194 1194 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:71] Error openning port 8092 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.33 -e DAppNode -a 192.168.1.## 8092 8092 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:71] Error openning port 4001 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.33 -e DAppNode -a 192.168.1.## 4001 4001 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:71] Error openning port 4002 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.33 -e DAppNode -a 192.168.1.## 4002 4002 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:91] Port 32768 TCP is not open
ERROR [watchers/natRenewal:91] Port 32769 UDP is not open
ERROR [watchers/natRenewal:91] Port 32768 UDP is not open
ERROR [watchers/natRenewal:91] Port 1194 UDP is not open
ERROR [watchers/natRenewal:91] Port 8092 TCP is not open
ERROR [watchers/natRenewal:91] Port 4001 TCP is not open
ERROR [watchers/natRenewal:91] Port 4002 UDP is not open

even though the Support Auto-Diagnose page has UPnP all looking ok

Session is open

IPFS resolves

Has connected to the internet, and detected own public IP

No ports have to be opened OR the router has UPnP enabled

NAT loopback enabled, external IP resolves

Disk usage is ok (<95%)

All core DAppNode Packages are running

thoughts?

ruvenni · 25 November 2020 15:45

HI @AJR

We need you to report the DAppNode version (Support > Report) and Prysm package version before being able to look into the issue.

Prysm version:

Thanks

AJR · 25 November 2020 18:26

Hi @ruvenni first of all thanks for all your assistance.
I have finished installing Goeth Eth 1 chain and have attempted to install the Prysm Pyrmont package…

0.1.3 (v1.0.0, v1.0.0 upstream)

but am receiving this error when trying to install the package from the DappStore

Error: Error verifying image: image tarball must contain strictly one image
at /usr/src/app/webpack:/src/modules/installer/downloadImages.ts:40:20
at Generator.throw ()
at rejected (/usr/src/app/index.js:174508:65)
at process._tickCallback (internal/process/next_tick.js:68:7)

{
“name”: “prysm-pyrmont.dnp.dappnode.eth”,
“version”: “0.1.3”,
“userSettings”: {
“prysm-pyrmont.dnp.dappnode.eth”: {
“environment”: {
“GRAFFITI”: “Validator”,
“HTTP_WEB3PROVIDER”: “http://goerli-geth.dappnode:8545”
}
}
},
“options”: {}
}

ruvenni · 25 November 2020 18:28

In addition, it would be convenient if you do a dig prysm-pyrmont.dappnode while connected to the VPN or dappnode’s wifi and send us the screenshot.

AJR · 25 November 2020 18:32

do you mean via a terminal window? Or is there a console within the my.dappnode web interface?

ruvenni · 25 November 2020 18:34

Dig is a linux command, it should be run in a terminal

AJR · 25 November 2020 18:38

Here you go dappnodeDIG

AJR · 25 November 2020 18:40

There’s an earlier error which was about 20 mins earlier than the Tarball error

Error: timeout
at Timeout._onTimeout (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:54:1)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)

{
“id”: “prysm-pyrmont.dnp.dappnode.eth”
}

AJR · 25 November 2020 18:48

and getting the same tarball error if I try to update the DMS package to

1.0.0

DigDMS

AJR · 25 November 2020 19:43

I’ve made some progress. I noticed the core system packages needed updating so I updated those and have now successfully installed Pyrmont via the ipfs link in GIT (v0.1.4) and updated the DMS package via the DappStore

Current status:
Goeth Chain = OK
Beacon Chain = currently synching
Validator = Getting this error in the logs…

ime=“2020-11-25 19:31:38” level=warning msg=“Running on Pyrmont Testnet” prefix=flags
time=“2020-11-25 19:31:38” level=warning msg=“Enabled full web mode, wallet password will be written to disk at the wallet directory upon completing web onboarding.” prefix=flags
time=“2020-11-25 19:31:38” level=info msg=“Enabling web portal to manage the validator client” prefix=node
time=“2020-11-25 19:31:38” level=info msg=“Checking DB” databasePath=“/root/.eth2validators” prefix=node
time=“2020-11-25 19:31:38” level=warning msg=“You are using a non-default web host. Web traffic is served by HTTP, so be wary of changing this parameter if you are exposing this host to the Internet!” prefix=node web-host=0.0.0.0
time=“2020-11-25 19:31:38” level=info msg=“Starting Prysm web UI on address, open in browser to access” address=“http://0.0.0.0:80” prefix=node
time=“2020-11-25 19:31:38” level=info msg=“Starting validator node” prefix=node version=“Prysm/v1.0.0/c7dd33431fb23f2fa62c1617f5c735fd7104ff0c. Built at: 2020-11-24 18:39:17+00:00”
time=“2020-11-25 19:31:38” level=warning msg=“You are using an insecure gRPC connection. If you are running your beacon node and validator on the same machines, you can ignore this message. If you want to know how to enable secure connections, see: https://docs.prylabs.network/docs/prysm-usage/secure-grpc” prefix=validator
time=“2020-11-25 19:31:38” level=info msg=“Starting gRPC gateway” address=“0.0.0.0:80” prefix=gateway
time=“2020-11-25 19:31:38” level=info msg=“gRPC server listening on address” address=“0.0.0.0:7000” prefix=rpc
time=“2020-11-25 19:32:08” level=warning msg=“You are using the --web option but have not yet signed via a browser. If your web host and port are exposed to the Internet, someone else can attempt to sign up for you! You can visit http://0.0.0.0:80 to view the Prysm web interface” prefix=rpc

AJR · 25 November 2020 20:40

making more progress. Realised I needed to go to the Prysm Web UI - prysm-pyrmont.dappnode

But am now receiving this error on the Wallet Password step.

Possibly because the Beacon Chain hasn’t finished synching yet??

The Validator log shows

time=“2020-11-25 20:34:21” level=info msg=“Successfully created wallet with ability to import keystores” --wallet-dir=“/root/.eth2validators” prefix=accounts

ps. the Prysm Web UI looks very nice!

AJR · 26 November 2020 16:31

Hey guys… I’ve got it working!!

I went through the process again and at Step 1 instead of copying the ‘validator_keys’ folder which has both the keystore.json and deposit.json file I just copied across the keystore.json file. Then went through the remaining steps without an issue.

Can someone confirm if that’s the right process or do you still need to copy the deposit.json file as well?

The next issue which I also posted in the Prysm Discord channel is Log errors…

ruvenni · 26 November 2020 17:55

Hi @AJR

This has been already reported to Prysm. It is not something related with our package integration but to their code instead.

AJR · 26 November 2020 19:10

Thanks for the update Ruvenni.

From my perspective, there are two outstanding issues

I have is the DappManager log showing these errors. Considering that the Validator is running ok, is this an issue?

ERROR [watchers/natRenewal:79] Error openning port 32769 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 32769 32769 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32770 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 32770 32770 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32770 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 32770 32770 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32772 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 32772 32772 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32771 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 32771 32771 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 1194 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 1194 1194 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 8092 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 8092 8092 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 4002 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 4002 4002 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 4001 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 4001 4001 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32768 TCP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 32768 32768 TCP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32769 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 32769 32769 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:79] Error openning port 32768 UDP: Command failed: docker run --rm --net=host --entrypoint=/usr/bin/upnpc dappmanager.dnp.dappnode.eth:0.2.36 -e DAppNode -a 192.168.1.## 32768 32768 UDP 7200
connect: Connection refused
ERROR [watchers/natRenewal:99] Port 32769 TCP is not open
ERROR [watchers/natRenewal:99] Port 32770 UDP is not open
ERROR [watchers/natRenewal:99] Port 32770 TCP is not open
ERROR [watchers/natRenewal:99] Port 32772 UDP is not open
ERROR [watchers/natRenewal:99] Port 32771 UDP is not open
ERROR [watchers/natRenewal:99] Port 1194 UDP is not open
ERROR [watchers/natRenewal:99] Port 8092 TCP is not open
ERROR [watchers/natRenewal:99] Port 4002 UDP is not open
ERROR [watchers/natRenewal:99] Port 4001 TCP is not open
ERROR [watchers/natRenewal:99] Port 32768 TCP is not open
ERROR [watchers/natRenewal:99] Port 32769 UDP is not open
ERROR [watchers/natRenewal:99] Port 32768 UDP is not open
Socket connected yGkHXhWTTzawQMYYAAAC

Even though I’m getting data in the Prysm Web UI Dashboard, I’m not seeing the same information in the Grafana Dashboard in DMS

image667×836 74.2 KB