An error occurred. Is it possible to fix this?

[Dr.Ko]

2024-04-08T04:44:56Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2024-04-08T04:44:56Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "console.address"}
2024-04-08T04:44:56Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "healthcheck.details"}
2024-04-08T04:44:56Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.private-address"}
2024-04-08T04:44:56Z    INFO    Anonymized tracing enabled      {"Process": "storagenode-updater"}
2024-04-08T04:44:56Z    INFO    Running on version      {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.99.3"}
2024-04-08T04:44:56Z    INFO    Downloading versions.   {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2024-04-08T04:44:56Z    INFO    Current binary version  {"Process": "storagenode-updater", "Service": "storagenode", "Version": "v1.99.3"}
2024-04-08T04:44:56Z    INFO    Version is up to date   {"Process": "storagenode-updater", "Service": "storagenode"}
2024-04-08T04:44:56Z    INFO    Current binary version  {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.99.3"}
2024-04-08T04:44:56Z    INFO    Version is up to date   {"Process": "storagenode-updater", "Service": "storagenode-updater"}
2024-04-08 04:44:57,939 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-08 04:44:57,940 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-08 04:44:57,940 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-08 04:44:59,970 INFO exited: storagenode (exit status 1; not expected)
2024-04-08 04:45:00,974 INFO spawned: 'storagenode' with pid 80
2024-04-08 04:45:00,976 WARN received SIGQUIT indicating exit request
2024-04-08 04:45:00,983 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2024-04-08T04:45:00Z    INFO    Got a signal from the OS: "terminated"  {"Process": "storagenode-updater"}
2024-04-08 04:45:00,984 INFO stopped: storagenode-updater (exit status 0)

There seems to be a problem after migration. Is this something that can be resolved?

---

I tried many methods, but couldn’t find an answer, so I decided to start a new journey. I feel sad about the past 4 months.

[daki82]

i can’t see any errors. this is the log of the node updater, not the log of the node.

[Dr.Ko]

Did I load the log incorrectly?
docker log --tail 20 storage node
I loaded it with this… I think it was imported incorrectly, but it has already been deleted from Docker…
After struggling with the data for a week, I was finally able to copy it, but I was mentally shaken when I couldn’t run it…

[arrogantrabbit]

@Dr.Ko

was finally able to copy it

Copy where? Did you adjust permissions?

[Dr.Ko]

It’s a little complicated. So I even wrote a post with this content, but I gave up in the end because I couldn’t execute it…

1. window → qnap → synology (1.5T)
2. window ->synology(2.8T)

The node running on Windows had bad sectors, so the copy speed was slow, and there were parts in the middle that couldn’t be copied, so even if I moved it and ran it well, it seemed like it would be disqualified.

Considering that I’ve had a hard time copying for a week, I don’t think I’ll be able to see the node for a while until the uptimerobot alarm pops up.

[Alexey]

If you mounted the storage from any of NAS with any network filesystem - it will not work. (It can work at the beginning, but will die later).
You need to run your node either directly on your file server, or use iSCSI, no options here.

[Dr.Ko]

I checked the node log and found this error: I thought there were bad sectors on the hard drive and was about to give up, but I’m sad to end it like this, so I’m copying it to a new hard drive as a last attempt, Once the copy is complete, I plan to move it back to Docker and run it.

node.log:58752416:2024-04-08T19:52:12+09:00	INFO	Configuration loaded	{"Location": "C:\\Program Files\\Storj\\Storage Node\\config.yaml"}
node.log:58752417:2024-04-08T19:52:12+09:00	INFO	Anonymized tracing enabled
node.log:58752418:2024-04-08T19:52:12+09:00	INFO	Operator email	{"Address": ""}
node.log:58752419:2024-04-08T19:52:12+09:00	INFO	Operator wallet	{"Address": ""}
node.log:58752420:2024-04-08T19:52:12+09:00	ERROR	failure during run	{"error": "Error opening database on storagenode: group:\n--- CreateFile D:\\blobs: The system cannot find the path specified.\n--- CreateFile D:\\temp: The system cannot find the path specified.\n--- CreateFile D:\\garbage: The system cannot find the path specified.\n--- CreateFile D:\\trash: The system cannot find the path specified.", "errorVerbose": "Error opening database on storagenode: group:\n--- CreateFile D:\\blobs: The system cannot find the path specified.\n--- CreateFile D:\\temp: The system cannot find the path specified.\n--- CreateFile D:\\garbage: The system cannot find the path specified.\n--- CreateFile D:\\trash: The system cannot find the path specified.\n\tmain.cmdRun:67\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:393\n\tstorj.io/common/process.cleanup.func1:411\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:77\n\tstorj.io/common/process.ExecWithCustomConfig:72\n\tstorj.io/common/process.Exec:62\n\tmain.(*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
node.log:58752421:2024-04-08T19:52:12+09:00	FATAL	Unrecoverable error	{"error": "Error opening database on storagenode: group:\n--- CreateFile D:\\blobs: The system cannot find the path specified.\n--- CreateFile D:\\temp: The system cannot find the path specified.\n--- CreateFile D:\\garbage: The system cannot find the path specified.\n--- CreateFile D:\\trash: The system cannot find the path specified.", "errorVerbose": "Error opening database on storagenode: group:\n--- CreateFile D:\\blobs: The system cannot find the path specified.\n--- CreateFile D:\\temp: The system cannot find the path specified.\n--- CreateFile D:\\garbage: The system cannot find the path specified.\n--- CreateFile D:\\trash: The system cannot find the path specified.\n\tmain.cmdRun:67\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:393\n\tstorj.io/common/process.cleanup.func1:411\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:77\n\tstorj.io/common/process.ExecWithCustomConfig:72\n\tstorj.io/common/process.Exec:62\n\tmain.(*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
node.log:58752453:2024-04-08T21:08:44+09:00	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "121RTSDU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "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: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
node.log:58752454:2024-04-08T21:08:44+09:00	INFO	pieces:trash	emptying trash started	{"Satellite ID": "12L9ZFwhUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs"}
node.log:58752455:2024-04-08T21:08:44+09:00	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "1wFTAgs9qKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "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: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
node.log:58752456:2024-04-08T21:08:45+09:00	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12EayRS2VU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "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: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
node.log:58752457:2024-04-08T21:08:45+09:00	INFO	pieces:trash	emptying trash started	{"Satellite ID": "121RTSDpyNZ84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6"}
node.log:58752458:2024-04-08T21:08:45+09:00	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12L9ZFuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "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: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
node.log:58752459:2024-04-08T21:08:45+09:00	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "121RTSDpyN4Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "attempts": 2, "error": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
node.log:58752460:2024-04-08T21:08:46+09:00	INFO	collector	deleted expired piece	{"Satellite ID": "12EayRS2V1kxKicsiFmxrsLZHeLUtdps3S", "Piece ID": "D74E3MTA6TVBJUJMCO5WDZG3FB37AFN4HQ"}
node.log:58752461:2024-04-08T21:08:46+09:00	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "1wFTAgs9CqKk4EAtmN5DpSxcs8EjT69tGE", "attempts": 2, "error": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}

[Alexey]

From your error it looks like you used a different identity for this node.
So, you may either:

• use a correct identity
• provide a correct path

In the first case, if data is not matching the previous identity - it will be deleted with a Garbage Collector. In the latest - it will recalculate the usage and continue run as before.

[Dr.Ko]

Since I run multiple nodes, I feel like I may have used it incorrectly without realizing it. The copying will be completed around Thursday, so I’ll give it a try then. If I succeed, I’ll write a reply. Thank you!!

[Alexey]

You need to move an identity to the disk with data to do not confuse identities and their data. The one disk - the one data location and the one identity, everything matching.
For you information: the identity without its data is useless, as a data without its identity.

[Dr.Ko]

2024-04-26T09:47:01Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “attempts”: 9, “error”: “ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: read tcp 10.25.11.2:42636->59.16.143.xx:28968: read: connection reset by peer”, “errorVerbose”: “ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: read tcp 10.25.11.2:42636->59.16.143.xx:28968: read: connection reset by peer\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78”}
2024-04-26T09:47:02Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “attempts”: 9, “error”: “ping satellite: check-in ratelimit: node rate limited by id”, “errorVerbose”: “ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:203\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78”}
2024-04-26T09:47:19Z INFO reputation:service node scores updated {“Process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “Total Audits”: 1643, “Successful Audits”: 1321, “Audit Score”: 1, “Online Score”: 0.7583558829514713, “Suspension Score”: 1, “Audit Score Delta”: 0, “Online Score Delta”: 0, “Suspension Score Delta”: 0}
2024-04-26T09:47:20Z INFO reputation:service node scores updated {“Process”: “storagenode”, “Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “Total Audits”: 22183, “Successful Audits”: 21902, “Audit Score”: 1, “Online Score”: 0.7818333853026281, “Suspension Score”: 1, “Audit Score Delta”: 0, “Online Score Delta”: 0, “Suspension Score Delta”: 0}

2024-04-26T09:51:16Z	ERROR	contact:service	ping satellite failed	{Process: storagenode, Satellite ID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE, attempts: 10, error: ping satellite: check-in ratelimit: node rate limited by id, errorVerbose: ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:203\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2024-04-26T09:51:16Z	ERROR	contact:service	ping satellite failed	{Process: storagenode, Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, attempts: 10, error: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: read tcp 10.85.1.5:37686->59.16.xx.xxx:28968: read: connection reset by peer, errorVerbose: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: read tcp 10.85.1.5:37686->59.16.xxx.xx:28968: read: connection reset by peer\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2024-04-26T09:51:18Z	ERROR	contact:service	ping satellite failed	{Process: storagenode, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, attempts: 10, error: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: read tcp 10.25.11.2:56990->59.16.xxx.xx:28968: read: connection reset by peer, errorVerbose: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: read tcp 10.25.11.2:56990->59.16.xx.xx:28968: read: connection reset by peer\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2024-04-26T09:51:20Z	ERROR	contact:service	ping satellite failed	{Process: storagenode, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, attempts: 10, error: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: read tcp 10.55.1.2:55154->59.16.xxx.xx:28968: read: connection reset by peer, errorVerbose: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: read tcp 10.55.1.2:55154->59.16.xx.xx:28968: read: connection reset by peer\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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}

2024-04-26T09:47:20Z INFO reputation:service node scores updated {“Process”: “storagenode”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Total Audits”: 18913, “Successful Audits”: 18656, “Audit Score”: 1, “Online Score”: 0.7807825638679708, “Suspension Score”: 1, “Audit Score Delta”: 0, “Online Score Delta”: 0, “Suspension Score Delta”: 0}
2024-04-26T09:47:21Z INFO reputation:service node scores updated {“Process”: “storagenode”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Total Audits”: 68135, “Successful Audits”: 60191, “Audit Score”: 0.9999761492296325, “Online Score”: 0.7586887821394176, “Suspension Score”: 1, “Audit Score Delta”: 0, “Online Score Delta”: 0, “Suspension Score Delta”: 0}

2024-04-26T09:52:56Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	used-space-filewalker completed	{Process: storagenode, satelliteID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, piecesContentSize: 3244703755512, Process: storagenode, piecesTotal: 3253596309752}
2024-04-26T09:52:56Z	INFO	lazyfilewalker.used-space-filewalker	subprocess finished successfully	{Process: storagenode, satelliteID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S}
2024-04-26T09:52:56Z	INFO	lazyfilewalker.used-space-filewalker	starting subprocess	{Process: storagenode, satelliteID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE}
2024-04-26T09:52:56Z	INFO	lazyfilewalker.used-space-filewalker	subprocess started	{Process: storagenode, satelliteID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE}
2024-04-26T09:52:56Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	Database started	{Process: storagenode, satelliteID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE, Process: storagenode}
2024-04-26T09:52:56Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	used-space-filewalker started	{Process: storagenode, satelliteID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE, Process: storagenode}
2024-04-26T09:52:57Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	used-space-filewalker completed	{Process: storagenode, satelliteID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE, Process: storagenode, piecesTotal: 20041386496, piecesContentSize: 20036137472}
2024-04-26T09:52:57Z	INFO	lazyfilewalker.used-space-filewalker	subprocess finished successfully	{Process: storagenode, satelliteID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE}
2024-04-26T09:52:57Z	INFO	lazyfilewalker.used-space-filewalker	starting subprocess	{Process: storagenode, satelliteID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6}
2024-04-26T09:52:57Z	INFO	lazyfilewalker.used-space-filewalker	subprocess started	{Process: storagenode, satelliteID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6}
2024-04-26T09:52:57Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	Database started	{Process: storagenode, satelliteID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, Process: storagenode}
2024-04-26T09:52:57Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	used-space-filewalker started	{Process: storagenode, satelliteID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, Process: storagenode}
2024-04-26T09:53:11Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	used-space-filewalker completed	{Process: storagenode, satelliteID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, Process: storagenode, piecesTotal: 97485591552, piecesContentSize: 97268875264}
2024-04-26T09:53:11Z	INFO	lazyfilewalker.used-space-filewalker	subprocess finished successfully	{Process: storagenode, satelliteID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6}
2024-04-26T09:53:11Z	INFO	lazyfilewalker.used-space-filewalker	starting subprocess	{Process: storagenode, satelliteID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs}
2024-04-26T09:53:11Z	INFO	lazyfilewalker.used-space-filewalker	subprocess started	{Process: storagenode, satelliteID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs}
2024-04-26T09:53:11Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	Database started	{Process: storagenode, satelliteID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Process: storagenode}
2024-04-26T09:53:11Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	used-space-filewalker started	{Process: storagenode, satelliteID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Process: storagenode}
2024-04-26T09:54:03Z	INFO	lazyfilewalker.used-space-filewalker.subprocess	used-space-filewalker completed	{Process: storagenode, satelliteID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Process: storagenode, piecesTotal: 1632915205632, piecesContentSize: 1632152514048}
2024-04-26T09:54:03Z	INFO	lazyfilewalker.used-space-filewalker	subprocess finished successfully	{Process: storagenode, satelliteID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs}

sudo docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28968:28967/tcp \
    -p 28968:28967/udp \
    -p 14003:14002 \
    -e WALLET="0xxxxxxxx" \
    -e EMAIL="xxxx@xxx.com" \
    -e ADDRESS="guga.xxxx.org:28968" \
    -e STORAGE="14.1TB" \
    --log-driver json-file \
    --log-opt max-size=10m \
    --log-opt max-file=5 \
    --user $(id -u):$(id -g) \
    --mount type=bind,source="/volume3/storj2/identity",destination=/app/identity \
    --mount type=bind,source="/volume3/storj2/data",destination=/app/config \
    --mount type=bind,source="/volume3/storj2/data/node.log",destination=/app/logs/node.log \
    --name storagenode2 storjlabs/storagenode:latest \
    --log.output=/app/logs/node.log \
    --operator.wallet-features=zksync

After copying to Synology, I run the second node, but it appears offline. I opened all the ports and set up the firewall, but it doesn’t work. Can you tell me what’s wrong?

[Alexey]

@Dr.Ko

connector failed: rpc: read tcp 10.25.11.2:42636->59.16.143.xx:28968: read: connection reset by peer”

This is mean that your local host is canceled the connection. Reasons are:

• you exhausted ephemeral ports
• you have a strict firewall (you need to check their logs)
• you have a network misconfigured (it’s not able to establish an external connections)
• a simple one - your contact address (and port) doesn’t available externally (you may check this using your advertised external address and port on your smartphone’s browser and a mobile internet).

Also, I would suggest to remove the decommissioned satellites:

How To Forget Untrusted Satellites

Following the announcement to decommission Europe-north-1 and US2 satellites, manually deleting the remaining data of these satellites from the node can be a tedious task as it requires finding the blobs folder name for each satellite, so we wanted to improve the storagenode CLI to semi-automate cleaning up a satellite data after it is marked as untrusted. The storagenode CLI (versions from 1.88.0) provides a forget-satellite subcommand to remove satellites from the trust cache and clean up the…

[Dr.Ko]

I only changed the port when setting up the first node, so the network connection seems to be working properly, but I don’t know what it means that the temporary ports have been used up…

@Alexey

a simple one - your contact address (and port) doesn’t available externally (you may check this using your advertised external address and port on your smartphone’s browser and a mobile internet).

Sorry, I don’t know what the above means. Does it mean to connect by entering the external address and port on the smartphone? 59.xx.xx.xx:28968 ??

I feel like my limits are being tested more and more…

[Alexey]

I mean that if you are able to open http://your-external-address-from-config-yaml:your-external-port-from-the-config-yaml from your mobile internet (not WiFi!), then it’s truly online.

[Dr.Ko]

28967 is connected, but 28968 is not connected…

[Alexey]

Then this is mean a misconfiguration.
What’s your port-forwarding rules? Do you use a DDNS or a current public IP in the node’s configuration?

[Dr.Ko]

Uploading: Screenshot_4.png…

I am using ddns provided by iptime.

[Alexey]

Have you configured to use a different ports for your second node?

[Dr.Ko]

@Dr.Ko

sudo docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28968:28967/tcp \
    -p 28968:28967/udp \
    -p 14003:14002 \
    -e WALLET="0xxxxxxxx" \
    -e EMAIL="xxxx@xxx.com" \
    -e ADDRESS="guga.xxxx.org:28968" \
    -e STORAGE="14.1TB" \

yes, i did…
That’s right, I changed the port. However, I created a new node and uploaded it once, and it works(port 28968). Since only the node transferred from Windows does not work, I wonder if there was a problem when moving from Windows to Docker. It seems that the data was moved well…

[Alexey]

The only problems that I can guess about:

• not the correct external port (or wrongly configured, seems like your case);
• not the correct identity

Please, provide your last 20 lines from the logs: How do I check my logs? - Storj Docs