[SOLVED] Unidentified download flow

[mpiter]

Hello,

When I use qbittorrent, I have a download rate about a quarter of the capacity of my line limit but when I check the real data flow coming to my computer I can see a full download charge.  For example, when I connect my computer to a 1000 KB/s line, qbittorent downloads stuff at around 250 KB/s.  When I check with a network utility my download speed, I can see around 1000 KB/s.  If I move to another place with a 500 KB/s line, qbittorrent download flow is around 125 KB/s while my network utility shows 500 KB/s.

I have used qbittorrent for a long time with various Linux distributions such as gentoo, Ubuntu, Linux Mint, and now with Linux Mint Debian Edition 201303 Mate version with kernel 3.2.0-4-amd64.  I have no ideas what could cause that problem or when it started.  This is pretty annoying because I always saturate my internal network while downloading very slowly data when I use qbittorrent.  Any hint where to look for would be welcome.  Thanks in advance,

[loki]

Are you using a wireless connection? This is the only thing I can think that might cause this problem.

[sledgehammer_999]

Does this network utility show how much bandwidth each process consumes? Does it show that qbt actually consumes 1000KB/s ? Or is it spilt among other things?
Also what version of qbt and libtorrent-rasterbar do you use?

[mpiter]

[quote="loki"]
Are you using a wireless connection?
[/quote]

Yes.  I have just followed your suggestion and tested qbittorrent with Wifi down and with a cable connection.  I had exactly the same problem :-(

[sledgehammer_999]

Can you answer my question too? You can use nethogs. Install it from your package manager of course.

[mpiter]

[quote="sledgehammer_999"]
Does this network utility show how much bandwidth each process consumes? Does it show that qbt actually consumes 1000KB/s ? Or is it spilt among other things?
Also what version of qbt and libtorrent-rasterbar do you use?
[/quote]

No it does not.  That is why I could not answer your request.  I did not find anything good, but thanks to your last post I am using nethogs right now.  I am on a 600 KB/s line, qbittorrent shows me in its bottom line a total of 150 KB/s, nethogs reports that qbittorrent receives 270 KB/s and that around 30 other processes called 192.168.1.18:6881-other_ip_addresses_with_port_number receives a few KB/s each (my NAT IP address is of course 192...18 and I use the usual 6881 port number for qbittorrent), and the total download speed is shown by the other global network monitor: 590 KB/s.  Summing the downloading speed of the processes shown by nethogs should amount the 590 KB/s.  There are no processes unrelated to qbittorrent shown by nethogs.  When I quit qbittorrent, nethogs shows no processes at all.

I use qbittorrent 2.9.8-1 with libtorrent-rasterbar 6.0.0.  Thanks a lot for your support.  Nethogs is a great tool :-)

[sledgehammer_999]

Just so you know, qbt 2.9.8 is really old and not supported anymore. Also what version of libtorrent-rasterbar (6.0.0 isn't a valid version for it)?
Could you post a screenshot of nethogs' output?

[mpiter]

OK, I am going to install a more recent version of qbt.  In /usr/lib I only have:

Code: Select all

lilas ~ $ ll /usr/lib/libtorrent-rasterbar.so.6*
lrwxrwxrwx 1 root root      29 Apr  6  2012 /usr/lib/libtorrent-rasterbar.so.6 -> libtorrent-rasterbar.so.6.0.0
-rw-r--r-- 1 root root 2729088 Apr  6  2012 /usr/lib/libtorrent-rasterbar.so.6.0.0

Here is the output of nethogs:

Code: Select all

NetHogs version 0.8.0

  PID USER     PROGRAM                                        DEV        SENT      RECEIVED       
30377 mpiter   qbittorrent                                    wlan0     58.826     384.791 KB/sec
?     root     192.168.1.18:6881-142.166.238.210:65232                   0.469       9.112 KB/sec
?     root     192.168.1.18:6881-81.170.214.41:44516                     0.427       8.876 KB/sec
?     root     192.168.1.18:6881-142.166.238.210:65171                   0.338       7.080 KB/sec
?     root     192.168.1.18:6881-196.203.217.34:6103                     0.467       6.908 KB/sec
?     root     192.168.1.18:6881-207.161.186.28:52623                    0.283       6.471 KB/sec
?     root     192.168.1.18:6881-196.203.217.34:25303                    0.462       6.046 KB/sec
?     root     192.168.1.18:6881-41.106.4.146:55513                      0.252       5.983 KB/sec
?     root     192.168.1.18:6881-85.17.73.202:64405                      0.351       5.959 KB/sec
?     root     192.168.1.18:6881-82.226.63.232:54078                     0.297       5.893 KB/sec
?     root     192.168.1.18:6881-46.193.0.244:52089                      0.255       5.305 KB/sec
?     root     192.168.1.18:6881-137.186.92.252:55735                    0.234       4.727 KB/sec
?     root     192.168.1.18:6881-85.240.102.186:56765                    0.310       4.505 KB/sec
?     root     192.168.1.18:6881-85.17.73.213:62612                      0.262       4.407 KB/sec
?     root     192.168.1.18:6881-207.38.210.79:59042                     0.215       4.221 KB/sec
?     root     192.168.1.18:6881-87.1.231.177:55127                      0.272       4.221 KB/sec
?     root     192.168.1.18:6881-184.75.214.34:52903                     0.224       4.171 KB/sec
?     root     192.168.1.18:6881-75.156.161.236:1057                     0.388       4.159 KB/sec
?     root     192.168.1.18:6881-82.232.146.161:57091                    0.283       3.963 KB/sec
?     root     192.168.1.18:6881-108.214.171.136:47670                   0.256       3.802 KB/sec
?     root     192.168.1.18:6881-41.45.97.42:57466                       0.168       3.738 KB/sec
?     root     192.168.1.18:6881-74.4.32.75:13777                        0.171       3.540 KB/sec
?     root     192.168.1.18:6881-201.246.96.131:13108                    0.181       3.124 KB/sec
?     root     192.168.1.18:6881-108.207.113.194:55037                   0.320       2.996 KB/sec
?     root     192.168.1.18:6881-179.235.202.32:63832                    0.337       2.969 KB/sec
?     root     192.168.1.18:6881-180.249.129.138:19456                   0.148       2.850 KB/sec
?     root     192.168.1.18:6881-107.203.23.131:50956                    0.128       2.660 KB/sec
?     root     192.168.1.18:6881-121.254.121.116:62860                   0.115       2.353 KB/sec
?     root     192.168.1.18:6881-190.59.25.184:57570                     0.108       2.059 KB/sec
?     root     192.168.1.18:6881-84.109.19.60:16623                      0.081       1.777 KB/sec
?     root     192.168.1.18:6881-174.92.60.38:62664                      0.166       1.613 KB/sec
?     root     192.168.1.18:6881-178.199.168.254:62568                   0.119       1.531 KB/sec

This probably amounts for the 590 KB/s reported by the other network monitoring tool.  At that moment, qbt downloaded at around 110 KB/s.

I must go right now but I will install a more recent qbt version today.  Thanks again for your suggestions, it gives hope.

[sledgehammer_999]

About libtorrent: See the version from the package manager (eg synaptic). What you are showing me is just the API/ABI version in the soname.

[mpiter]

It was 0.15.10-1+b1, but do not mind, you solved the problem.  I installed qbittorent 3.0.11 and libtorrent-rasterbar 0.16.10 from the source and it has worked well since then.  I am just surprised that the previous version did not work.  It was in the stable Debian Weezy tree.  Anyway, many thanks for your time and competence, you made my day :-)

[sledgehammer_999]

No problem. Just so you know, you can pull 0.16.10 from sid and 3.0.9 from experimental.

[mpiter]

I built the Debian packages from the sid and experimental sources then I installed them.  I prefer to build the packages from sources than pull in the binaries to avoid problems stemming from their dependencies.  It works well.  My only complain is that quitting qbittorrent leaves the program in a <defunct> state.  The program dies when I exit my session and then, qbittorrent checks all the files again.  Except this problem, it looks like working well.  Thanks again for all your comments.

[Peter]

If you are on Debian, just stick to apt-pinning. Most comfy method.