Hello,
two of my nodes upgraded themselves to v1.67.1 and now have QUIC Misconfigured. Of course, there are no changes on the routers, the TCP and UDP ports are still open.
Docker restart does not help. Any other suggestions?
Thanks
2 Likes
Got the same problem. 2 nodes with 1.66.1 running fine, one node with 1.67.1 QUIC is misconfigured too. No changes made to the node.
2 Likes
I confirm same situation.
2 Likes
In my case a stop/start of the container seems to have resolved the problem at least for now.
my Storage Node Stats show QUIC misconfigured. when I restart node, no this error. later there is.
I have set UDP config, like it:
cat /etc/sysctl.conf
kernel.panic = 3
net.core.somaxconn = 65535
net.ipv4.tcp_tw_reuse = 1
net.core.rmem_max=2500000
curl domain:28967
{
"Statuses": null,
"Help": "To access Storagenode services, please use DRPC protocol!",
"AllHealthy": true
}
The QUIC status checked only on start. So if you changed something, you need to restart the node to apply the changes.
I restarted. at first, QUIC showed OK, but later showed Misconfigured
Do you have errors in the log?
2022-11-17T11:35:58.148Z INFO orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S sending {"Process": "storagenode", "count": 374}
2022-11-17T11:35:58.148Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs sending {"Process": "storagenode", "count": 226}
2022-11-17T11:35:58.148Z INFO orders.121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6 sending {"Process": "storagenode", "count": 4}
2022-11-17T11:37:38.865Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "attempts": 1, "error": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 108.160.172.200:7777: connect: connection timed out", "errorVerbose": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 108.160.172.200:7777: connect: connection timed out\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189"}
2022-11-17T11:37:38.866Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo", "attempts": 1, "error": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 31.13.70.13:7777: connect: connection timed out", "errorVerbose": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 31.13.70.13:7777: connect: connection timed out\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189"}
2022-11-17T11:37:38.866Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "attempts": 1, "error": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 108.160.165.211:7777: connect: connection timed out", "errorVerbose": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 108.160.165.211:7777: connect: connection timed out\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189"}
2022-11-17T11:37:38.867Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "attempts": 1, "error": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 50.23.209.199:7777: connect: connection timed out", "errorVerbose": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 50.23.209.199:7777: connect: connection timed out\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189"}
2022-11-17T11:38:05.489Z INFO orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S finished {"Process": "storagenode"}
2022-11-17T11:38:05.489Z INFO orders.121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6 finished {"Process": "storagenode"}
2022-11-17T11:38:05.490Z ERROR orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S failed to settle orders for satellite {"Process": "storagenode", "satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "error": "order: failed to start settlement: rpc: tcp connector failed: rpc: dial tcp 108.160.162.102:7777: connect: connection timed out", "errorVerbose": "order: failed to start settlement: rpc: tcp connector failed: rpc: dial tcp 108.160.162.102:7777: connect: connection timed out\n\tstorj.io/storj/storagenode/orders.(*Service).settleWindow:254\n\tstorj.io/storj/storagenode/orders.(*Service).SendOrders.func1:205\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2022-11-17T11:38:05.489Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs finished {"Process": "storagenode"}
2022-11-17T11:38:05.490Z ERROR orders.121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6 failed to settle orders for satellite {"Process": "storagenode", "satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "error": "order: failed to start settlement: rpc: tcp connector failed: rpc: dial tcp 31.13.95.34:7777: connect: connection timed out", "errorVerbose": "order: failed to start settlement: rpc: tcp connector failed: rpc: dial tcp 31.13.95.34:7777: connect: connection timed out\n\tstorj.io/storj/storagenode/orders.(*Service).settleWindow:254\n\tstorj.io/storj/storagenode/orders.(*Service).SendOrders.func1:205\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2022-11-17T11:38:05.490Z ERROR orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs failed to settle orders for satellite {"Process": "storagenode", "satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "error": "order: failed to start settlement: rpc: tcp connector failed: rpc: dial tcp 199.16.156.11:7777: connect: connection timed out", "errorVerbose": "order: failed to start settlement: rpc: tcp connector failed: rpc: dial tcp 199.16.156.11:7777: connect: connection timed out\n\tstorj.io/storj/storagenode/orders.(*Service).settleWindow:254\n\tstorj.io/storj/storagenode/orders.(*Service).SendOrders.func1:205\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
Seems you have problems with your network.
Could you please try to reboot your router?
my network only connect to tardigrade.io, not connect to storj.io directly.
QUIC Misconfigured ERROR came out recently
Accordingly your previous picture, it’s not ok.
It cannot connect to the satellites, and your statistics is not updated.
I also had a node operating with QUIC configured correctly - after auto-update to 1.67.1 I am seeing a misconfigured status. node restart didn’t help
2 Likes
Not everyone. I have never seen this error on my node. So, there is that.
Secondly, the issue is likely elsewhere, but because the quic connectivity check is made on node start, the whatever issue has happened is only discovered when the node is restarted following the update. Correlation vs causation. Maybe related to how docker image starts? (Is the network dependency specified for the storage node service?)
1 Like
wait for Version v1.67.3
1 Like
I have also confirmed the same. One node updated to 1.67.1. and has Misconfigured QUIC. It never had issues on the previous versions. No changes on my network. The other 2 existing nodes not yet updated still have QUIC OK as status.
2 Likes
This happens to v1.67.1
What is your node version?