Deluge 1.3.12 / libtorrent 1.1.0.0 Error

[Wallabee19]

I'm currently testing this on a shared box without root access as I wanted to try the latest Deluge and latest libtorrent together. I built Deluge 1.3.12 just fine using Develop so I could specify a folder I had access to and it ran fine with the already installed libtorrent 1.0.5.0.

I then built libtorrent 1.1.0.0 into a directory I had access to using the --prefix flag for ./configure. This all went fine. I then copied the resulting libtorrent.so to Deluge's folder with the source file.

I ran "export LD_LIBRARY_PATH=/pathtolibtorrentlibrary". I then went to my deluge folder that had the actual executables and ran "./deluged --version". The output came back just fine as:

deluged: 1.3.12
libtorrent: 1.1.0.0

All good so far. So now to run deluge i did "./deluged -c ~/.config/delugeTest" (I created another config folder for this specific version of deluge)

And I get this error: (I removed the names of top level directories since this is on shared box)

Code: Select all

[ERROR   ] 01:25:09 component:118 [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'dict' object has no attribute 'peer_tos'
/****/****/****/deluge/deluge/main.py:230:start_daemon
/****/****/****/deluge/deluge/core/daemon.py:161:__init__
/****/****/****/deluge/deluge/component.py:296:start
/****/****/****/deluge/deluge/component.py:124:_component_start
--- <exception caught here> ---
/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:139:maybeDeferred
/****/****/****/deluge/deluge/core/preferencesmanager.py:170:start
/****/****/****/deluge/deluge/config.py:312:register_set_function
/****/****/****/deluge/deluge/core/preferencesmanager.py:290:_on_set_peer_tos
/****/****/****/deluge/deluge/core/preferencesmanager.py:237:session_set_setting
]
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
  File "/****/****/****/deluge/deluge/main.py", line 230, in start_daemon
    Daemon(options, args)
  File "/****/****/****/deluge/deluge/core/daemon.py", line 161, in __init__
    component.start("PreferencesManager")
  File "/****/****/****/deluge/deluge/component.py", line 296, in start
    deferreds.append(self.components[name]._component_start())
  File "/****/****/****/deluge/deluge/component.py", line 124, in _component_start
    d = maybeDeferred(self.start)
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 139, in maybeDeferred
    result = f(*args, **kw)
  File "/****/****/****/deluge/deluge/core/preferencesmanager.py", line 170, in start
    self._on_set_peer_tos)
  File "/****/****/****/deluge/deluge/config.py", line 312, in register_set_function
    function(key, self.__config[key])
  File "/****/****/****/deluge/deluge/core/preferencesmanager.py", line 290, in _on_set_peer_tos
    self.session_set_setting("peer_tos", chr(int(value, 16)))
  File "/****/****/****/deluge/deluge/core/preferencesmanager.py", line 237, in session_set_setting
    setattr(settings, key, value)
exceptions.AttributeError: 'dict' object has no attribute 'peer_tos'
[ERROR   ] 01:25:09 component:118 [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'dict' object has no attribute 'peer_tos'
/****/****/****/deluge/deluge/main.py:230:start_daemon
/****/****/****/deluge/deluge/core/daemon.py:169:__init__
/****/****/****/deluge/deluge/component.py:296:start
/****/****/****/deluge/deluge/component.py:124:_component_start
--- <exception caught here> ---
/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:139:maybeDeferred
/****/****/****/deluge/deluge/core/preferencesmanager.py:170:start
/****/****/****/deluge/deluge/config.py:312:register_set_function
/****/****/****/deluge/deluge/core/preferencesmanager.py:290:_on_set_peer_tos
/****/****/****/deluge/deluge/core/preferencesmanager.py:237:session_set_setting
]

Any ideas what could be wrong?

[Cas]

We will not be changing anything in 1.3 code to support lt 1.1.

[highvoltage]

Cas is there any estimate of when we will have a compatible Deluge + lt 1.1?

Best Regards,

[tugurlann]

Hello,

I'm on Ubuntu 16.04 which has renamend network interfaces to eno[x].

I have set speed limits, however, the daemon seems to ignore them and saturates my bandwidth.

Pasted output from deluge-console status bar:

Code: Select all

C: 163 (250) D: 33.7 MiB (25000.0 KiB/s) U: 5.6 MiB (20000.0 KiB/s) DHT: 0

I'm also connecting via a thin client, this is a screen capture:

thin client screen cap

deluge.png (4.29 KiB) Viewed 14879 times

Any ideas why, what should I look for in the log?

Some configuration settings, as listed by deluge-console:

Code: Select all

max_active_downloading: 17
  max_active_limit: 25
  max_active_seeding: 25
  max_connections_global: 250
  max_connections_per_second: 20
  max_connections_per_torrent: 120
  max_download_speed: 25000.0
  max_download_speed_per_torrent: -1
  max_half_open_connections: 50
  max_upload_slots_global: 4
  max_upload_slots_per_torrent: 8
  max_upload_speed: 20000.0
  max_upload_speed_per_torrent: -1

Any thoughts?

[tugurlann]

After downgrading to libtorrent 1.0.9 the problem went away.

[dare_v]

After upgrading libtorrent to 1.1.0 I get the following error when starting the deamon

[ERROR ] 15:59:38 component:118 [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'dict' object has no attribute 'peer_tos'
/usr/local/lib/python2.7/dist-packages/deluge-1.3.12-py2.7.egg/deluge/main.py:230:start_daemon
/usr/local/lib/python2.7/dist-packages/deluge-1.3.12-py2.7.egg/deluge/core/daemon.py:161:__init__
/usr/local/lib/python2.7/dist-packages/deluge-1.3.12-py2.7.egg/deluge/component.py:296:start
/usr/local/lib/python2.7/dist-packages/deluge-1.3.12-py2.7.egg/deluge/component.py:124:_component_start
--- <exception caught here> ---

There are a lot more errors like this, but did not copied them all. I can, if you want.

Otherwise it seems it works fine, the client, so maybe this is due to deluge not being fully libtorrent 1.1.0 compatible and these errors can be ignored? On this matter which other libtorrent version do you recommend?

[dare_v]

update: no...its not working fine. It failed to report any stats to the tracker.

[Shryp]

1.0.9 is working fine for me. The developer has stated that the new 1.1 versions of libtorrent have made a lot of changes so it probably isn't going to work well. I think the plan is a small 1.3.13 bugfix release and then work libtorrent 1.1 into the new deluge 2.0.

[adziahel]

Confirming, got same issue after my distro upgrade to lt 1.1.

[adziahel]

I think the plan is a small 1.3.13 bugfix release and then work libtorrent 1.1 into the new deluge 2.0.

Not according to http://forum.deluge-torrent.org/viewtop ... 39#p223925.