Running Docker on macos.
the node stopped and could not be restarted. Normally Docker restarts it but this
time I had to quit Docker and restart Docker to restart the node.
The log file had these lines plus about 26000 more of go backtraces.
SIGBUS: bus error
PC=0xe1ede3 m=250 sigcode=2
signal arrived during cgo execution
This has happend twice in the last week. Any ideas on what to check?
Maybe part of the backtrace?
Did you already search the forum? Such like Fatal error: unexpected signal during runtime execution
Sounds familiar, including some pointers…
Looks like a me key error, it is trying to address memory that isn’t there. Like a physical address that is not available. This kind of thing is usually due to a bug. I would check for a docker update or check docker help for people having similar issues.
Yeah, there are some bugs lately in the MacOS version of Docker. As is also mentioned in the STORJ manual: Docker - Storj Docs
I looked at that and it is interesting but no solutions.
It is interesting because their error happens in the same function in the sqlite library doing the same thing to the same database (bandwidth) called by the same go function. My machine is old, docker is old, and the OS is old. Everything is different except the storj executable.
Maybe storj should look at it again.
You may try to remove the image and pull it again:
docker stop -t 300 storagenode
docker rm storagenode
docker rmi storjlabs/storagenode:latest
docker pull storjlabs/storagenode:latest
then run your usual full docker run command.