Docs about Port-forwarding on TrueNAS

I guess that it was the second attempt to install the app, but your friend did not get a new authorization token, so the authorization is failed during setup, but the Truechart app did not notice that and attempted to start the node.

So now you need to get a new authorization token and replace it in the app, then start the app. I do not know though - would it try to sign the identity or not. Likely not.
In this case you can sign it manually.

  1. Open a shell to the Storj container
  2. Execute commands:
bash
mkdir tmp
cd tmp
wget https://github.com/storj/storj/releases/latest/download/identity_linux_amd64.zip
unzip identity_linux_amd64.zip
./identity authorize identity --config-dir=/app/tmp --identity-dir=/app REPLACE_ME_TO_THE_AUTHORIZATION_TOKEN

You need to replace REPLACE_ME_TO_THE_AUTHORIZATION_TOKEN to the new authorization token in the last command.
If the authorization would be successful, you may restart the app and check its logs again.

1 Like

OK, the CLI identity authorization moved me forward! I am now online and QUIC is OK. Within the web GUI everything looks perfect, in fact.

However, the setup log is recording errors regarding my email and wallet not being “specified.” This is particularly odd, since the GUI shows my wallet address.

It seems it was my mistake (my apologies for the frustration) thinking short posts were better, so I’ll provide the whole tail of the latest setup log with its errors:

2023-07-30T16:19:08.986260259Z 17000K … … … … … 99% 109M 0s
2023-07-30T16:19:08.986598271Z 17050K … … … 100% 73.5M=0.2s
2023-07-30T16:19:08.986627676Z
2023-07-30T16:19:08.986663764Z 2023-07-30 16:19:08 (69.7 MB/s) - ‘/tmp/storagenode.zip’ saved [17483827/17483827]
2023-07-30T16:19:08.986672049Z
2023-07-30T16:19:09.229174598Z 2023-07-30 16:19:09,229 INFO RPC interface ‘supervisor’ initialized
2023-07-30T16:19:09.229238227Z 2023-07-30 16:19:09,229 INFO supervisord started with pid 7
2023-07-30T16:19:10.231025657Z 2023-07-30 16:19:10,230 INFO spawned: ‘processes-exit-eventlistener’ with pid 66
2023-07-30T16:19:10.231659863Z 2023-07-30 16:19:10,231 INFO spawned: ‘storagenode’ with pid 67
2023-07-30T16:19:10.232167753Z 2023-07-30 16:19:10,232 INFO spawned: ‘storagenode-updater’ with pid 68
2023-07-30T16:19:10.236706602Z 2023-07-30T16:19:10Z INFO Configuration loaded {“Process”: “storagenode-updater”, “Location”: “/app/config/config.yaml”}
2023-07-30T16:19:10.236715018Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.enabled”}
2023-07-30T16:19:10.236720508Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}
2023-07-30T16:19:10.236738813Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2023-07-30T16:19:10.236742770Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2023-07-30T16:19:10.236755083Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2023-07-30T16:19:10.236759000Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features”}
2023-07-30T16:19:10.236768158Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2023-07-30T16:19:10.236771975Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2023-07-30T16:19:10.236775551Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.details”}
2023-07-30T16:19:10.236786452Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2023-07-30T16:19:10.236790319Z 2023-07-30T16:19:10Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “console.address”}
2023-07-30T16:19:10.236799847Z 2023-07-30T16:19:10Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.level”}
2023-07-30T16:19:10.236803604Z 2023-07-30T16:19:10Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.encoding”}
2023-07-30T16:19:10.236816879Z 2023-07-30T16:19:10Z INFO Anonymized tracing enabled {“Process”: “storagenode-updater”}
2023-07-30T16:19:10.236953985Z 2023-07-30T16:19:10Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.84.1”}
2023-07-30T16:19:10.237051217Z 2023-07-30T16:19:10Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2023-07-30T16:19:10.251688625Z 2023-07-30T16:19:10Z INFO Configuration loaded {“process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-07-30T16:19:10.251858693Z 2023-07-30T16:19:10Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-07-30T16:19:10.252645595Z 2023-07-30T16:19:10Z WARN Operator email address isn’t specified. {“process”: “storagenode”}
2023-07-30T16:19:10.252665712Z 2023-07-30T16:19:10Z ERROR Invalid configuration. {“process”: “storagenode”, “error”: “operator wallet address isn’t specified”}
2023-07-30T16:19:10.252670511Z Error: operator wallet address isn’t specified
2023-07-30T16:19:10.253085858Z 2023-07-30 16:19:10,253 INFO exited: storagenode (exit status 1; not expected)
2023-07-30T16:19:10.380600683Z 2023-07-30T16:19:10Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.84.1”}
2023-07-30T16:19:10.380632853Z 2023-07-30T16:19:10Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode”}
2023-07-30T16:19:10.383327623Z 2023-07-30T16:19:10Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.84.1”}
2023-07-30T16:19:10.383342571Z 2023-07-30T16:19:10Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2023-07-30T16:19:11.384687162Z 2023-07-30 16:19:11,384 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-30T16:19:11.385735994Z 2023-07-30 16:19:11,385 INFO spawned: ‘storagenode’ with pid 104
2023-07-30T16:19:11.385850418Z 2023-07-30 16:19:11,385 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-30T16:19:11.403121242Z 2023-07-30T16:19:11Z INFO Configuration loaded {“process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-07-30T16:19:11.403210800Z 2023-07-30T16:19:11Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-07-30T16:19:11.403822764Z 2023-07-30T16:19:11Z WARN Operator email address isn’t specified. {“process”: “storagenode”}
2023-07-30T16:19:11.403879951Z 2023-07-30T16:19:11Z ERROR Invalid configuration. {“process”: “storagenode”, “error”: “operator wallet address isn’t specified”}
2023-07-30T16:19:11.403898456Z Error: operator wallet address isn’t specified
2023-07-30T16:19:11.404357284Z 2023-07-30 16:19:11,404 INFO exited: storagenode (exit status 1; not expected)
2023-07-30T16:19:13.407637181Z 2023-07-30 16:19:13,407 INFO spawned: ‘storagenode’ with pid 118
2023-07-30T16:19:13.424117105Z 2023-07-30T16:19:13Z INFO Configuration loaded {“process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-07-30T16:19:13.424170936Z 2023-07-30T16:19:13Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-07-30T16:19:13.424687442Z 2023-07-30T16:19:13Z WARN Operator email address isn’t specified. {“process”: “storagenode”}
2023-07-30T16:19:13.424705977Z 2023-07-30T16:19:13Z ERROR Invalid configuration. {“process”: “storagenode”, “error”: “operator wallet address isn’t specified”}
2023-07-30T16:19:13.424799061Z Error: operator wallet address isn’t specified
2023-07-30T16:19:13.425152402Z 2023-07-30 16:19:13,425 INFO exited: storagenode (exit status 1; not expected)
2023-07-30T16:19:16.429799493Z 2023-07-30 16:19:16,429 INFO spawned: ‘storagenode’ with pid 130
2023-07-30T16:19:16.447559140Z 2023-07-30T16:19:16Z INFO Configuration loaded {“process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-07-30T16:19:16.447598965Z 2023-07-30T16:19:16Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-07-30T16:19:16.448093740Z 2023-07-30T16:19:16Z WARN Operator email address isn’t specified. {“process”: “storagenode”}
2023-07-30T16:19:16.448113617Z 2023-07-30T16:19:16Z ERROR Invalid configuration. {“process”: “storagenode”, “error”: “operator wallet address isn’t specified”}
2023-07-30T16:19:16.448132863Z Error: operator wallet address isn’t specified
2023-07-30T16:19:16.448660631Z 2023-07-30 16:19:16,448 INFO exited: storagenode (exit status 1; not expected)
2023-07-30T16:19:17.449936953Z 2023-07-30 16:19:17,449 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2023-07-30T16:19:19.452399661Z 2023-07-30 16:19:19,452 WARN received SIGQUIT indicating exit request
2023-07-30T16:19:19.452549301Z 2023-07-30 16:19:19,452 INFO waiting for processes-exit-eventlistener, storagenode-updater to die
2023-07-30T16:19:19.452947195Z 2023-07-30T16:19:19Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2023-07-30T16:19:19.453871654Z 2023-07-30 16:19:19,453 INFO stopped: storagenode-updater (exit status 0)
2023-07-30T16:19:20.455621232Z 2023-07-30 16:19:20,455 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)

this is related to how they prepare the pod with storagenode, they run a setup step without providing an email and wallet in a separate init container, then start the node container normally with a prepared config and all needed parameters. And this behavior actually can broke the node, if you change the path to the data location and/or identity to a wrong one. So be careful.

1 Like