Hello,
Every time I quit qBittorrent it is turning into a process that can't be killed normally. I have to use `killall --signal=KILL qbittorrent` in order to shut it down. This causes the torrents that I have added before I shut it down to be lost.
I am using Arch Linux x64. Is there some way I could debug this properly and post the results? Any ideas?
Thank you!
qBittorrent process always turns into zombie on quit
-
Switeck
Re: qBittorrent process always turns into zombie on quit
If you back up qBitTorrent's settings before killing its process it might at least retain the torrents you added since last start.
There may be more than 1 bug at work here...
1.Also, how much ram is qBT using just before you try to shut it down?
2.Lots of torrents loaded already?
3.Are you binding qBT to a network interface (for VPN, proxy, or just to avoid it going through wifi)?
4.The shutdown process for qBT may require it sending a "safe" break connection command for every tcp/ip link it has and wait for the all clear+done reply, so if there's 100's of them and some are already not responding...this could take a long time even if it doesn't lock up on trying. Would you say there's at least 50 peer/seed connections when you try to close?
5.DHT, LPD/LSD, uTP, or UPnP/NAT-PMP used?
6.Speed settings might be helpful if none of this gets anywhere.
There may be more than 1 bug at work here...
1.Also, how much ram is qBT using just before you try to shut it down?
2.Lots of torrents loaded already?
3.Are you binding qBT to a network interface (for VPN, proxy, or just to avoid it going through wifi)?
4.The shutdown process for qBT may require it sending a "safe" break connection command for every tcp/ip link it has and wait for the all clear+done reply, so if there's 100's of them and some are already not responding...this could take a long time even if it doesn't lock up on trying. Would you say there's at least 50 peer/seed connections when you try to close?
5.DHT, LPD/LSD, uTP, or UPnP/NAT-PMP used?
6.Speed settings might be helpful if none of this gets anywhere.
-
zombee
Re: qBittorrent process always turns into zombie on quit
Thanks so much for the reply, Switeck!
I should definitely note this, I was using Linux Mint before switching over to Arch yesterday and everything was fine. I backed up my config and data directories and transferred them over.
1. Not sure how to accurately find this info. I did `echo 0 $(awk '/TYPE/ {print "+", $2}' /proc/`pidof PROCESS`/smaps) | bc` and got back 919910. qBittorrent has been running for about 45-60 minutes.
2. Yeah, over 1300.
3. Nope, haven't touched anything like that.
4. Probably, yeah. But it *never* did this on Linux Mint.
5. Just UPNP I believe.
6. No speed settings, just unlimited.
I should definitely note this, I was using Linux Mint before switching over to Arch yesterday and everything was fine. I backed up my config and data directories and transferred them over.
1. Not sure how to accurately find this info. I did `echo 0 $(awk '/TYPE/ {print "+", $2}' /proc/`pidof PROCESS`/smaps) | bc` and got back 919910. qBittorrent has been running for about 45-60 minutes.
2. Yeah, over 1300.
3. Nope, haven't touched anything like that.
4. Probably, yeah. But it *never* did this on Linux Mint.
5. Just UPNP I believe.
6. No speed settings, just unlimited.
-
zombee
Re: qBittorrent process always turns into zombie on quit
Alright so I think we figured this out.
First off, 2 of my hard drives have become read-only filesystems for some reason. It is possible that the torrent client was trying to write to the hard drive and got caught up. The second issue may have been relating to the open file limit in Linux. I upped this from 1024 to 4096. Read this topic a bit for more info: https://bbs.archlinux.org/viewtopic.php?id=69239 Restarting the computer after editing that file allowed the limit to go up.
I'll keep an eye on it for the next few days and hopefully this can be solved. Thank you so much for your help, Switeck!
First off, 2 of my hard drives have become read-only filesystems for some reason. It is possible that the torrent client was trying to write to the hard drive and got caught up. The second issue may have been relating to the open file limit in Linux. I upped this from 1024 to 4096. Read this topic a bit for more info: https://bbs.archlinux.org/viewtopic.php?id=69239 Restarting the computer after editing that file allowed the limit to go up.
I'll keep an eye on it for the next few days and hopefully this can be solved. Thank you so much for your help, Switeck!