did you have any sort of issues and is the node still suspended on that satellite…
its not to difficult to offend the suspension score but that usually recovers very quickly…
had my system stall out a few days ago and got a few suspensions, but when i noticed and checked it a few days later it was all fine again.
yeah it surprise me to, apparently there are two stages or kinds of suspensions… one can be really short and is cause by a lot of intermittent issues in a short time, and the score will jump right back.
the other is the one we are more familiar with and usually lasts a lot longer.
don’t really know the exacts of it… i think it was @Alexey that was taking about it at one point.
So, I know you know but if the docker container restarted, your logs will be reset and the information prior to that lost.
docker ps -a
and look at the uptime for the container, if it’s about the same then your container restarted - #1 suspect would be the out of mem killer, probably due to disk stall.
have a look at
dmesg | grep -i error
see if anything obvious jumps out.
I can also add, last night at 00:00 UTC someone started a huge upload ! my disks nearly took off the packets per second jumped from the normal 3 per second, to 98 per second for my node.
It is probably unrelated, but if you had the blip last night, this traffic could of played a part.
#Edit : also your docker, what version ? and what repo are you pulling from ? if it happens to be Debian / Ubuntu there are some breaking changes not back ported yet \o/ - you would be better updating apt repos to point to Docker Repos and pull the latest.
Hmm - so… If you happen to be running on an LXC container on Proxmox, or another KVM based hypervisor, there is a regression in docker I’m afraid - it been patched in 20.10.12 so upgrade when you can [make sure storj is down]
oh interesting, I thought nothing of it, but the I/O packet graphs shows the anomaly well - would be interesting to know if others saw the same thing ?