Core temperature is 36☌, and it has active fan cooling and copper dissipators, I've never seen temperatures above 50☌-55☌ during a stress test. Right now htop shows that the Pi resources are barely used: core 4 is the most used one at an average of 3.2% load, memory used 357M out of 3.81G, swap is not being used. The Fail2Ban access log looks clean (I'm the only one that tried to access it) and I've just tested Fail2Ban, and it works as expected. The only people accessing it are myself and my brother (he barely uses it anyway).

This is obviously a bit of an inconvenience, especially if I'm not in the house to restart it.

The only thing I can do is manually restart it from the plug. If that happens I can't SSH into it, I can't remote on via TeamViewer nor I can keep transfering files. The system is not headless, I'm running Raspbian with the default desktop manager.Įvery now and then, but especially in the morning after not having been accessed for the night, if I start a file transfer to/from the Pi (whether via SMB or the Owncloud website), the Pi just stops responding.

On it I'm running Owncloud (running on Apache and MariaDB), SMB service to access the drives from within my network without having to login onto the Owncloud website, Fail2Ban as a brute force attack protection and TeamViewer (because of reasons). So, I have a Pi 4 4GB with Raspbian Buster installed, kernel version 4.19.97-v7l+, that I use as a storage server. Hello all, this is yet another cry for help for a Raspberry Pi crashing.

Raspberry pi teamviewer freeze