Custom Query (2449 matches)

This happens when I have a destination with low IO throughput

• Perhaps related to #994 -

Eg: My setup is basically:

• Download to SSD mountpoint (/data/fast/incomplete)
• Once finished, move to low rpm HDD big storage (/data/slow/new)

So, when this process happens, everything that Deluge is doing is stalled and waits for the copy to happens.

This issue happens when using 'Move to Storage' or when using 'Move Completed'. Anything related to copying the downloaded files will stall the current tasks.

Reproduce:

• Add various downloads and start them (around 10gb+ size)
• Move any finished downloads to a low IO mountpoint (eg: USB 2.0 External HDD)
• Notice the non-finished downloads stall

Related to move_storage() - ​http://www.rasterbar.com/products/libtorrent/manual.html

move_storage()

void move_storage(std::string const& save_path) const;
void move_storage(std::wstring const& save_path) const;

Moves the file(s) that this torrent are currently seeding from or downloading to. If the given save_path is not located on the same drive as the original save path, The files will be copied to the new drive and removed from their original location. This will block all other disk IO, and other torrents download and upload rates may drop while copying the file.

Can't Deluge implement it?

Plugins fail to load in web-ui on FreeBSD package "deluge-1.3.12,1" due to an inability to write to the default Python egg cache directory. This directory does not exist in the default installation, nor is there a documented dependency. Most visibly for me, this breaks labels in web-ui; you can't create them or assign torrents to them.

Creating a directory (I used "/usr/local/etc/deluge/.python-eggs") and adding export PYTHON_EGG_CACHE="/usr/local/etc/deluge/.python-eggs" to /usr/local/etc/rc.d/deluge_web resolved the issue.

[ERROR   ] 10:23:49 pluginmanagerbase:146 Unable to instantiate plugin!
[ERROR   ] 10:23:49 pluginmanagerbase:147 Can't extract file(s) to egg cache

The following error occurred while trying to extract file(s) to the Python egg
cache:

  [Errno 13] Permission denied: '/.python-eggs'

The Python egg cache directory is currently set to:

  /.python-eggs

Perhaps your account does not have write access to this directory?  You can
change the cache directory by setting the PYTHON_EGG_CACHE environment
variable to point to an accessible directory.
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/deluge/pluginmanagerbase.py", line 144, in enable_plugin
    instance = cls(plugin_name.replace("-", "_"))
  File "/usr/local/lib/python2.7/site-packages/deluge/plugins/Extractor-0.4-py2.7.egg/extractor/__init__.py", line 56, in __init__
    from webui import WebUI as _plugin_cls
  File "/usr/local/lib/python2.7/site-packages/deluge/plugins/Extractor-0.4-py2.7.egg/extractor/webui.py", line 47, in <module>
  File "/usr/local/lib/python2.7/site-packages/deluge/plugins/Extractor-0.4-py2.7.egg/extractor/webui.py", line 54, in WebUI
  File "/usr/local/lib/python2.7/site-packages/deluge/plugins/Extractor-0.4-py2.7.egg/extractor/common.py", line 38, in get_resource
    return pkg_resources.resource_filename("extractor", os.path.join("data", filename))
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1150, in resource_filename
    self, resource_name
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1863, in get_resource_filename
    return self._extract_resource(manager, zip_path)
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1892, in _extract_resource
    self.egg_name, self._parts(zip_path)
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1217, in get_cache_path
    self.extraction_error()
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1197, in extraction_error
    raise err
ExtractionError: Can't extract file(s) to egg cache

This is in reference to closed ticket ​http://dev.deluge-torrent.org/ticket/2677

I am running latest develop branch which includes the commits to fix this issue.

When configured as such (using --base or setting base in web.conf) I get nothing but a blank page when browsing to the web site.

I've tested the site in IE, FF, Chrome, and Edge, all have the same issue.

I can privately provide a URL which is publicly accessible for verification.