Jump to content

Extremly high cpu usage after I start the torrent download..


easyyu

Recommended Posts

Hi.

I'm on Ubuntu 16.04 x64 (VPS)

I downloaded the latest version from a site (with date x.Sept.2019) for Ubintu 13 (since there are not compiled for higher version???).

After aprox of 10min or around of 3,8-4% of torrent till I monitor with htop command the processes, one of the uttorrent pid get totally crazy and strat to eat all cpu's and in 20sec it reaches out 160! (average of cpu usage 1minute, left value of three about stat of cpu)

Whats happenng? How can I prevent this?

I tried in desperation to use even the cpulimit but somehow on of child process always born and start to eat the cpu.

I din't change nothing in config only the download location and download speed to 7Mbps, and disable the DHT checkboxs.

I'm starting my torrent in script with next parameters:

-settingspath $UTORRENT_DIR/ -configfile $UTORRENT_DIR/utserver.conf -logfile $LOGFILE -daemon

Log file do not giving me to much information:

[01:19:24] Locale C
[20190909 01:19:24] GetNodeID failed, using /dev/random
[20190909 01:19:24] computer id: DBCA8xxxxxxxxxxxxxF46A6C7EA16566B4
[20190909 01:19:24] total physical memory 536870912 max disk cache 33554432
[20190909 01:19:24] Using IP address 127.0.0.2
[20190909 01:19:24] IPv6 is installed
[20190909 01:19:29] File not found during integrity check: /emu/utorrent//webcache.dat
[20190909 01:19:29] File not found during integrity check: /emu/utorrent//webcache.dat.new
[20190909 01:19:29] File not found during integrity check: /emu/utorrent//webcache.dat.old
[20190909 01:21:40] uT HTTP torrent add of '/home/utorrent/0000155a-0001.utt' succeeded
[20190909 01:21:53] Unable to load "0000155a-0003.utt": Torrent is already loaded!
[20190909 01:21:53] uT HTTP torrent add of '/home/utorrent/0000155a-0003.utt' succeeded
[20190909 01:22:03] uT HTTP torrent add of '/home/utorrent/0000155a-0004.utt' succeeded
[20190909 01:34:17] uT HTTP torrent add of '/home/utorrent/0000155a-0006.utt' succeeded
[20190909 01:35:55] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 3076 FAILED HASH CHECK
[20190909 01:36:20] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 3489 FAILED HASH CHECK
[20190909 01:36:22] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 1250 FAILED HASH CHECK
[20190909 01:36:26] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 3291 FAILED HASH CHECK
[20190909 01:36:26] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 1946 FAILED HASH CHECK
[20190909 01:36:26] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 908 FAILED HASH CHECK
[20190909 01:36:49] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 1250 FAILED HASH CHECK
[20190909 01:36:51] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 3489 FAILED HASH CHECK
[20190909 01:36:57] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 3590 FAILED HASH CHECK
[20190909 01:36:58] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 3649 FAILED HASH CHECK
[20190909 01:36:58] Banned xxx.1xx.2xx.2xx:64010 until forever
[20190909 01:37:06] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 215 FAILED HASH CHECK
[20190909 01:37:21] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 3747 FAILED HASH CHECK
[20190909 01:37:27] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 2926 FAILED HASH CHECK
[20190909 01:37:38] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 1291 FAILED HASH CHECK
[20190909 01:38:23] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 1820 FAILED HASH CHECK
[20190909 01:38:39] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 908 FAILED HASH CHECK
[20190909 01:38:52] *** xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: PIECE 3751 FAILED HASH CHECK

Thx

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...