i tried to start a node on docker but I only get that error.
Files on dockerhost are located there:
/mnt/storage/storagenode
/mnt/storage/identity/storagenode
They belong to a normal user and got 755 permissions.
For setting up and starting I use this commands and execute with a normal user which is in the docker group. <> stands for sensitive data I removed.
I´m on a Raspi 4 with 2 sdds attached. I created a lvm over both sdds with ext4 and mounted it to /mnt/storage. Added to fstab ofc. The normal user should indicate that it is not the root user.
2024-11-10 17:22:16,700 INFO Set uid to user 0 succeeded
2024-11-10 17:22:16,708 INFO RPC interface 'supervisor' initialized
2024-11-10 17:22:16,708 INFO supervisord started with pid 1
2024-11-10 17:22:17,712 INFO spawned: 'processes-exit-eventlistener' with pid 49
2024-11-10 17:22:17,717 INFO spawned: 'storagenode' with pid 50
2024-11-10 17:22:17,722 INFO spawned: 'storagenode-updater' with pid 51
2024-11-10T17:22:17Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "console.address"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.details"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "contact.external-address"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.enabled"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.address"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.email"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet"}
2024-11-10T17:22:17Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.private-address"}
2024-11-10T17:22:17Z INFO Anonymized tracing enabled {"Process": "storagenode-updater"}
2024-11-10T17:22:17Z INFO Running on version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.115.5"}
2024-11-10T17:22:17Z INFO Downloading versions. {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2024-11-10T17:22:17Z INFO Configuration loaded {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2024-11-10T17:22:17Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2024-11-10T17:22:17Z INFO Operator email {"Process": "storagenode", "Address": "<>"}
2024-11-10T17:22:17Z INFO Operator wallet {"Process": "storagenode", "Address": "<>"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "info"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "bandwidth"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "orders"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "piece_expiration"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "pieceinfo"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "piece_spaced_used"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "reputation"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "storage_usage"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "used_serial"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "satellites"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "notifications"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "heldamount"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "pricing"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "secret"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "garbage_collection_filewalker_progress"}
2024-11-10T17:22:17Z INFO db database does not exist {"Process": "storagenode", "database": "used_space_per_prefix"}
No, it shall be online immediately. Check the logs, check your port forwarding settings, check your DDNS, check if you have public IP — some internet providers use carrier grade NAT to conserve addresses
Ok, then I have to check.
Pi is directly behind a FritzBox.
Port is opened for udp and tcp.
I use the ddns service provided by fritz itself. This is working as a wireguard server is running several month.
processes are running, only errors like this occuring
2024-11-10T20:36:06Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "attempts": 1, "error": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: not signed by any CA in the whitelist: CA cert", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}