Node Issue after a down

Node Operators troubleshooting
1

good morning, I have a node that runs on a raspberry pi 3B + with a 4.0Tb USB HD (3.5Tb are assigned to the node) this morning I received a notification from uptimerobot that my node was offline, I tried to relaunch it but it does not start
this is the output of the docker logs --tail 20 storagenode command

/usr/local/go/src/runtime/panic.go:826 +0x44 fp=0x222dd84 sp=0x222dd6c pc=0x40c90
runtime.throw(0xb185ba, 0x19)
/usr/local/go/src/runtime/panic.go:774 +0x5c fp=0x222dd98 sp=0x222dd84 pc=0x40adc
runtime.panicCheck1(0x5e7c8, 0xb185ba, 0x19)
/usr/local/go/src/runtime/panic.go:21 +0xb8 fp=0x222ddac sp=0x222dd98 pc=0x3edfc
runtime.goPanicSliceB(0x23d84e5, 0x5d2d75)
/usr/local/go/src/runtime/panic.go:102 +0x2c fp=0x222ddd0 sp=0x222ddac pc=0x3f2f8
runtime.pcvalue(0x11e1014, 0x12cdf00, 0x23d84e5, 0x74e628, 0x0, 0x5cf00, 0xcd3d28)
/usr/local/go/src/runtime/symtab.go:671 +0x458 fp=0x222de1c sp=0x222ddd0 pc=0x5e7c8
runtime.funcline1(0x11e1014, 0x12cdf00, 0x74e628, 0x0, 0x1bea4, 0x2153b20, 0x70)
/usr/local/go/src/runtime/symtab.go:760 +0x4c fp=0x222de4c sp=0x222de1c pc=0x5e9e0
runtime.(*Frames).Next(0x2153b20, 0x74e628, 0x11e1014, 0xcd3d28, 0x3, 0x0, 0x0, 0x0, 0x24ba788, 0x11e1014, …)
/usr/local/go/src/runtime/symtab.go:145 +0x49c fp=0x222ded8 sp=0x222de4c pc=0x5d260
github.com/spacemonkeygo/monkit/v3.callerPackage(0x1, 0x4ef58, 0x12c62c0)
/go/pkg/mod/github.com/spacemonkeygo/monkit/v3@v3.0.6/callers.go:27 +0xb0 fp=0x222df4c sp=0x222ded8 pc=0x420cb4
github.com/spacemonkeygo/monkit/v3.Package(0x17)
/go/pkg/mod/github.com/spacemonkeygo/monkit/v3@v3.0.6/registry.go:236 +0x1c fp=0x222df60 sp=0x222df4c pc=0x429634
invalid spdelta �; 0x24ba788 0x74e628 0xa8 3891
fatal error: slice bounds out of range
stack trace unavailable

I have checked all the db with sqlite and they are ok

what can I do?

2

Welcome to the forum @FedeSNOita!

Here’s a checklist you can try.

3

ok, i follow the steps the port is open but when i try to check with docker exec -it storagenode ls -l /app/identity this is the response
Error response from daemon: Container b555406e16f766902c6c8a80da01574d36776df47531c444b8662bc6494baa61 is restarting, wait until the container is running

it seem that the node still always on restart

4

Show your docker run command and remove any personal info from it.

5

I would like to suggest you to check the SD card for errors.
Also, it could be easy to just flash the OS after format the SD.
Make sure that your identity is saved to the safe place. I would suggest to copy it to the same HDD.
If the HDD would fail, you will loose the node anyway, so it makes no sense to store the identity somewhere else.

6

talk about this?
docker run -d --restart unless-stopped -p 28967:28967
-p 14002:14002
-e WALLET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-e EMAIL=xxxxxxxxxxxxxxxxxxxx
-e ADDRESS=xxxxxx.xxxxxdns.biz:28967
-e STORAGE=3.5TB
–mount type=bind,source=/home/rpi3_storjnode/.local/share/storj/identity/storagenode,destination=/app/identity
–mount type=bind,source=/mnt/storagenode,destination=/app/config
–name storagenode storjlabs/storagenode:beta

7

ok now try to flash a new os in a new sd , I will write to you when I am done

8

Please, copy the identity first to you HDD

9

yes i have copied the identity

10

ok I reinstalled everything on a new SD and now everything works perfectly, probably the previous SD had degraded
thank you very much!!! :heart_eyes:

2 Likes