I have searched the existing open and closed issues
Required Information
DietPi version | cat /boot/dietpi/.version
Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
Kernel version | uname --all
Architecture | dpkg --print-architecture
SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
Power supply used | (EG: 5V 1A RAVpower)
SD card used | (EG: SanDisk ultra)
Additional Information (if applicable)
Software title | (EG: Nextcloud)
Was the software title installed freshly or updated/migrated?
Can this issue be replicated on a fresh installation of DietPi?
ā If you sent a ādietpi-bugreportā, please paste the ID here ā
Bug report ID | echo $G_HW_UUID
Steps to reproduce
Just running qbittorrent-nox after a little while just hangs my PI
ā¦
Expected behaviour
Should keep running
ā¦
Actual behaviour
Crashes or hangs the PI
ā¦
Extra details
Logs do not show anything, the amount of time between reset and crash is pretty much random.
DietPI version 5.2.2
QBitTorrent version 5.1.0 64 bit
Anyone else having similar issues?
Which RPi model is it? Quick guess would be exhausted memory or low voltage during preak usage, e.g. when download and a flush from buffer to disk comes together or so. But it is difficult to know without logs. You do not have a screen attached to catch kernel errors at, do you?
I do have a screen attached, but nothing shows up on it. I have the logs going to a non-volatile disk space. I have looked in the logs, everything is pretty much normal tasks (torrents completing). The the start up tasks start listing off in the log. No other error messages in the logs.
I ran what you suggested. Will post the logs here as soon as something gets written.
Relevant would be the kernel logs, i.e. the systemd journal, or rsyslog to fetch and store them in plain text log files.
But if the HDMI screen is not showing anything, then the system logs most likely wonāt either, as systemd feeds both from the kernel ring buffer.
You could monitor things like RAM usage and CPU temperature on a dedicated SSH session or so. Also check for kernel errors earlier, like when a download started, so some disk I/O happened already:
EDIT: What boot media are you using, and what drive is qBittorrent downloading to? Maybe the shared 1.2A USB power limit causes issues, if you are using a larger (than a stick/thumb) USB drive.
Right thanks, a typo my end. The missing Bluetooth firmware blob is interesting (if firmware-brcm80211 is installed, which is from RPi Ltdās own APT repository), but unrelated.
Could be a memory issue. I have slowly increased the swap size, and the crashing is less frequent. Did confirm the PI has 1GB of memory, so out of memory would make sense.