My node crashes after some minutes

Node Operators troubleshooting
1

Hi mates,
since some days I got problems with my node on a raspberry pi.
Its crashing all the time, after only few minutes up.

here is my log:

sudo docker logs --tail 20 storagenode
crypto/tls.(*cipherSuiteTLS13).extract(0x10704f0, 0x0, 0x0, 0x0, 0x182af40, 0x20, 0x20, 0x0, 0x182af40, 0x20)
/usr/local/go/src/crypto/tls/key_schedule.go:66 +0x78
crypto/tls.(*serverHandshakeStateTLS13).sendServerFinished(0x1ef6d08, 0x0, 0x0)
/usr/local/go/src/crypto/tls/handshake_server_tls13.go:658 +0x16c
crypto/tls.(*serverHandshakeStateTLS13).handshake(0x1ef6d08, 0x1992600, 0x0)
/usr/local/go/src/crypto/tls/handshake_server_tls13.go:62 +0xbc
crypto/tls.(*Conn).serverHandshake(0x1ce1600, 0x1, 0x275101)
/usr/local/go/src/crypto/tls/handshake_server.go:50 +0x68
crypto/tls.(*Conn).Handshake(0x1ce1600, 0x0, 0x0)
/usr/local/go/src/crypto/tls/conn.go:1362 +0xd0
crypto/tls.(*Conn).Read(0x1ce1600, 0x1bdf000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
/usr/local/go/src/crypto/tls/conn.go:1239 +0x48
bufio.(*Scanner).Scan(0x1ccf900, 0x0)
/usr/local/go/src/bufio/scan.go:214 +0x88
storj.io/drpc/drpcwire.(*Reader).ReadPacket(0x208f960, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x40000000, …)
/go/pkg/mod/storj.io/drpc@v0.0.16/drpcwire/transport.go:121 +0xc4
storj.io/drpc/drpcmanager.(*Manager).manageReader(0x1ba2210)
/go/pkg/mod/storj.io/drpc@v0.0.16/drpcmanager/manager.go:288 +0xec
created by storj.io/drpc/drpcmanager.NewWithOptions
/go/pkg/mod/storj.io/drpc@v0.0.16/drpcmanager/manager.go:78 +0x340

Can anyone help me out?
Thanks!
Alex

2

there should be a lot more if it was actually connected…

often the node will continually reset until connected…
https://documentation.storj.io/dependencies/port-forwarding

so i would guess portforwarding, firewall blocking ports, or ip address miss configuration.

i would have hoped i could read the log message… but looks very connection related…
best advice i can offer…

not always right tho… :slight_smile: these logs are kinda terrible for rookies…
i’ve been around a year and i can barely make sense of it…

3

I would recommend:

  1. Stop and remove the container
docker stop -t 300 storagenode
docker rm storagenode
  1. Prune images
docker image rm storjlabs/storagenode:latest
  1. Pull a new version
docker pull storjlabs/storagenode:latest
  1. Run the node with all your parameters back.
4

Hi Guys,
Thanks for your Help so far.

No ist seems running, but my certificate is not loaded properly. How can I use, / Import, /authorize my old cert File? I do Not get that…

Please Help
Alex

5

The part of the logs shows me that there is some more deep problem, on OS or docker level. The stack trace is unusual for the unloaded identity.
Have you performed steps which I suggested?

6

It says TLS Peer certificate Verifikation Error

7

Yes i Re installed the hole system

8

Ok, then get an authorization token from there: https://registration.storj.io/ and sign your identity: Identity - Storj

9

16169360896223335035149907100054
161693608962233350351499071000544000Ă—3000 2.91 MB

10

I have the token already. as I understand I Need the old certificate and Re authorize it gain. Ist that correct? The command identity authorize storagenode … Ist not working in my Machine…

11

It should work. What identity binary you have used? What is your current platform where you tried to authorize the identity? What’s the error?

12

did you do the grep thing that should say 2 and 3 rather than 1 and 2
i have on occasion had nodes where i could have sworn i did sign the identity, but then hadn’t…

under confirming identity.

image
image839Ă—701 45.9 KB

i know it doesn’t exactly solve anything… but it does confirm if the identity was signed… ofc it also has to be in the right location for node or whatever one is trying to do…

13

Yes, in the end i copied the 2 Files to the root directory and did this signing grep command again.
It returned 2 for both. No it works or seems to.

Thanks to both of you!!
Alex

1 Like