begbie
22 September 2025 12:53
1
Not quite sure what is happening here, but it seems every few days, my Qbittorrent client stops working. When looking in the logs I’m seeing:
× qbittorrent.service - qBittorrent (DietPi)
Loaded: loaded (/etc/systemd/system/qbittorrent.service; enabled; preset: enabled)
Active: failed (Result: signal) since Sat 2025-09-20 01:21:38 BST; 2 days ago
Duration: 3d 4h 8min 21.448s
Docs: man:qbittorrent-nox(1)
Process: 1148431 ExecStart=/usr/bin/qbittorrent-nox (code=killed, signal=SEGV)
Main PID: 1148431 (code=killed, signal=SEGV)
CPU: 38min 12.942s
Notice: journal has been rotated since unit was started, output may be incomplete.
Any ideas on this one?
you need to check service log and maybe kernel error messages
journalctl -u qbittorrent.service
dmesg -l 0,1,2,3
begbie
22 September 2025 13:20
3
This is what I see:
root@DietPi:\~# journalctl -u qbittorrent.service
– No entries –
root@DietPi:\~# dmesg -l 0,1,2,3
\[ 0.640675\] bcm2708_fb soc:fb: Unable to determine number of FBs. Disabling driver.
\[ 0.640689\] bcm2708_fb soc:fb: probe with driver bcm2708_fb failed with error -2
without log its nearly impossible to see what happened.
begbie
22 September 2025 13:35
5
What is the best way to get the log? I assume it is time bound before it gets purged or something? Maybe I’ll upgrade to Trixie and get the new QBittorrent client installed and see what happens
Jappe
22 September 2025 13:42
6
By default it should log into /var/log/qbittorrent/qbittorrent.log.
If not, log into the web UI and in the preferences you can specify a path./home/qbittorrent/.config/qBittorrent/qBittorrent.conf
begbie
22 September 2025 14:00
7
I’ve checked in the UI and there is no option to specify the log directly
Jappe
22 September 2025 16:24
8
I checked it also before I wrote my answer, I will make a screenshot, it’s right in the first tab of the settings window:
begbie
23 September 2025 09:51
9
That’s new in V5, but isn’t there in V4
Jappe
23 September 2025 17:54
10
Oh, alright then!
1 Like
