Docker update v1.71.2 - auto stopped docker and didnt restart

Node Operators troubleshooting
, ,
21

OOT, but I just checked docker logs and …

2023-02-03T19:15:23.775Z        INFO    Configuration loaded    {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2023-02-03T19:15:23.776Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet"}
... (more of this)
2023-02-03T19:15:23.778Z        INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2023-02-03T19:15:23.778Z        INFO    Invalid configuration file value for key        {"Process": "storagenode-updater", "Key": "log.output"}

Is this normal?

22

no, you can just start it (what’s usually docker daemon do, if it is instructed with --restart policy, by default it’s no):

docker start storagenode

However, if it’s created when the mounts were not available, then you need to remove the container and create a new one with full docker run command.

yes, these warnings on the INFO level. This is storagenode-updater complains for unknown to it options from the config.yaml, you may ignore them.

2 Likes