Why such low ingress

[Alexey]

@YuriyGavrilov

use of closed network connection

@YuriyGavrilov

connection reset by peer

@YuriyGavrilov

"error": "manager closed: unexpected EOF"

Usual long tail cancelation, your node is too slow to provide or accept the piece (the loosed race). The resulting error depends on what moment the client canceled the connection, so stack-trace would be different. But the reason is the same.

@YuriyGavrilov

2024-06-17T16:22:54Z	WARN	console:service	unable to get Satellite URL	{"Process": "storagenode", "Satellite ID": "12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo", "error": "console: trust: satellite is untrusted", "errorVerbose": "console: trust: satellite is untrusted\n\tstorj.io/storj/storagenode/trust.init:29\n\truntime.doInit1:6740\n\truntime.doInit:6707\n\truntime.main:249"}
2024-06-17T16:22:54Z	WARN	console:service	unable to get Satellite URL	{"Process": "storagenode", "Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "error": "console: trust: satellite is untrusted", "errorVerbose": "console: trust: satellite is untrusted\n\tstorj.io/storj/storagenode/trust.init:29\n\truntime.doInit1:6740\n\truntime.doInit:6707\n\truntime.main:249"}

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…

If regular restarts are related to

@YuriyGavrilov

timed out after 1m0s while verifying writability of storage directory

then the solution is provided there:

Fatal Error on my Node

Maybe worth to take a look on: