Node restarting (Docker)

Node Operators troubleshooting
,
1

Hello. I’m using Docker (4.22.1) for windows. Storj version is 1.86.1. I’ve been a node operator since May.

I have two nodes, one of them is ok. The other one is endlessly restarting, after around 10 seconds. I can’t look up the log in terminal (“error from daemon in stream: Error grabbing logs: invalid character ‘\x00’ looking for beginning of value”).

What should I do? Thanks in advance.

2

Wasn,t docker for windows unstable?
There is an gui version. All i know.

3

Please post the last 20 lines from the logs: How do I check my logs? - Storj Docs

@daki82 it is stable enough, if you use WSL2 engine, or more old version, if you use Hyper-V. But requires more attention unfortunately, like create a scheduler task to run the Docker Desktop on start, or check it more frequently regarding various network issues on some systems.
I’m running 2 nodes in the Docker Desktop for Windows (WSL2 engine) and have had issues only after some Docker Desktop updates, but they working stable for the last 3 years.

4

Big thanks, what is your docker version?

5 
PS C:\> docker version
Client:
 Cloud integration: v1.0.29
 Version:           20.10.21
 API version:       1.41
 Go version:        go1.18.7
 Git commit:        baeda1f
 Built:             Tue Oct 25 18:08:16 2022
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.14.1 (91661)
 Engine:
  Version:          20.10.21
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.7
  Git commit:       3056208
  Built:            Tue Oct 25 18:00:19 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.9
  GitCommit:        1c90a442489720eec95342e1789ee8a5e1b9536f
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
6

Thank you, here it is:

2023-09-15T05:27:47Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {“process”: “storagenode”}
Error: trust: malformed cache: invalid character ‘\x00’ looking for beginning of value
2023-09-15 05:27:48,540 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-15 05:27:48,540 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-15 05:27:48,540 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-09-15 05:27:48,541 INFO exited: storagenode (exit status 1; not expected)
2023-09-15 05:27:49,544 INFO spawned: ‘storagenode’ with pid 43
2023-09-15 05:27:49,544 WARN received SIGQUIT indicating exit request
2023-09-15 05:27:49,545 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2023-09-15T05:27:49Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2023-09-15 05:27:49,547 INFO stopped: storagenode-updater (exit status 0)
2023-09-15T05:27:49Z INFO Configuration loaded {“process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-09-15T05:27:49Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-09-15T05:27:49Z INFO Operator email {“process”: “storagenode”, “Address”: “xxxx”}
2023-09-15T05:27:49Z INFO Operator wallet {“process”: “storagenode”, “Address”: “yyyy”}
2023-09-15T05:27:49Z INFO server kernel support for server-side tcp fast open remains disabled. {“process”: “storagenode”}
2023-09-15T05:27:49Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {“process”: “storagenode”}
Error: trust: malformed cache: invalid character ‘\x00’ looking for beginning of value
2023-09-15 05:27:50,487 INFO stopped: storagenode (exit status 1)
2023-09-15 05:27:50,488 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)

7

maybe this helps:

2 Likes
8

I provide you with the post where they explain the solution to the problem you have with the cache, I hope it helps you.

2 Likes
9

Simple as that. It worked, thanks!
Now I hope my node doesn’t get disqualified.

10

for4 days off? no ti won’t get disqued,
losein a bit of data, yes, recoveriy in 30 days possible: yes.

Good luck.

2 Likes