Hi,
Stat receiving strange bug with QUIC few days ago. Already have a node with 6tb and never saw such error about QUIC miscoonfigured.
Some pice of log:
rock64@rockpro64:~$ sudo docker logs --tail 10000 storagenode | grep QUIC
2023-12-10T20:14:01Z WARN contact:service Your node is still considered to be online but encountered an error. {"process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
2023-12-10T20:14:17Z WARN contact:service Your node is still considered to be online but encountered an error. {"process": "storagenode", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
2023-12-10T20:14:33Z WARN contact:service Your node is still considered to be online but encountered an error. {"process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
2023-12-10T20:15:04Z WARN contact:service Your node is still considered to be online but encountered an error. {"process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
2023-12-10T20:23:02Z WARN contact:service Your node is still considered to be online but encountered an error. {"process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
2023-12-10T20:23:03Z WARN contact:service Your node is still considered to be online but encountered an error. {"process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
2023-12-10T20:23:16Z WARN contact:service Your node is still considered to be online but encountered an error. {"process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
2023-12-10T20:23:34Z WARN contact:service Your node is still considered to be online but encountered an error. {"process": "storagenode", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Error": "contact: failed to ping storage node using QUIC, your node indicated error code: 0, rpc: quic: timeout: no recent network activity"}
Port is open and online. Tested it with online tools. Tried to reboot and restart. Nothings help.
Version v1.92.1
There is also find such messages as strange:
2023-12-10 20:48:07,271 INFO spawned: 'storagenode-updater' with pid 13
2023-12-10T20:48:07Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.address"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "contact.external-address"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.email"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.private-address"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "console.address"}
2023-12-10T20:48:07Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet"}
2023-12-10T20:48:07Z INFO Invalid configuration file value for key {"Process": "storagenode-updater", "Key": "log.level"}
2023-12-10T20:48:07Z INFO Invalid configuration file value for key {"Process": "storagenode-updater", "Key": "log.output"}
2023-12-10T20:48:07Z INFO Invalid configuration file value for key {"Process": "storagenode-updater", "Key": "log.stack"}
2023-12-10T20:48:07Z INFO Invalid configuration file value for key {"Process": "storagenode-updater", "Key": "log.caller"}
2023-12-10T20:48:07Z INFO Invalid configuration file value for key {"Process": "storagenode-updater", "Key": "log.development"}
2023-12-10T20:48:07Z INFO Anonymized tracing enabled {"Process": "storagenode-updater"}
2023-12-10T20:48:07Z INFO Running on version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.92.1"}
Br,
Yuriy Gavrilov