Problem docker in logs

Node Operators troubleshooting
,
1

Hi i haver this error in logs, and my docker it up and ok…

6\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2022-05-22T07:19:53.362Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 6, "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:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2022-05-22T07:20:23.552Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "attempts": 7, "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:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2022-05-22T07:20:25.883Z        ERROR   contact:service ping satellite failed   {"Process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 7, "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:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}


STATUS

Online

QUIC

OK

UPTIME

2m

LAST CONTACT

2m ago

VERSION

v1.55.1

PERIOD

May

and this error… in my docker

2022-05-22T07:46:18.132Z        INFO    Configuration loaded    {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "console.address"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.email"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "contact.external-address"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.private-address"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.address"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2022-05-22T07:46:18.132Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2

This error is happening when your node tried to check-in on the satellite too often. This is usually happen if your node is not reachable for this satellite and the node will try to check-in over and over again.
So, if you fixed an offline issue, then these errors should not appear after that.

these informational messages from the storagenode-updater, because it uses the same config.yaml as a storagenode to get some configuration parameters, but it doesn’t support all of them, so it adds complaints about that to the log. Can be ignored.

3

so, i have this:

sudo docker run --rm -e SETUP="true" \
    --user $(id -u):$(id -g) \
    --mount type=bind,source="/mnt/storj1/storagenode/identity",destination=/app/identity \
    --mount type=bind,source="/mnt/storj1/",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest

and before i run this:

sudo docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28967:28967/tcp \
    -p 28967:28967/udp \
    -p 14002:14002 \
    -e WALLET="xxx" \
    -e EMAIL="xxx" \
    -e ADDRESS="xxx:28967" \
    -e STORAGE="xxTB" \
    --user $(id -u):$(id -g) \
    --mount type=bind,source="/mnt/storj1/storagenode/identity",destination=/app/identity \
    --mount type=bind,source="/mnt/storj1",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest
4

The setup step should be done only once for entire node’s life, please do not run in a second time.
Your docker run looks correct, and if I understand correctly - your node is online and even QUIC is configured properly. So, it should work.

5

yea but in command

docker exec -it storagenode /app/dashboard.sh

Storage Node Dashboard ( Node Version: v1.55.1 )

======================

ID 1gqZfYf868fWSx4Mv7xxxxx
Status ONLINE
Uptime 12m12s

               Available         Used     Egress     Ingress
 Bandwidth           N/A          0 B        0 B         0 B (since May 1)
      Disk       6.94 TB     61.96 GB

Internal 127.0.0.1:7778
External xxxx:28967

6

In my experience these may still appear for a while after the problem is fixed, which makes sense. The rate limit still applies. They should disappear after a while though if the underlying problem is solved.

It can be a little confusing, since the error makes you think there is still a problem. And if you keep restarting and trying things because you think it’s still broken, you keep running into that rate limit. If your node is online, but has this error, I recommend just giving it some time and leaving it alone for a bit.

2 Likes