[1.10RC1] Deluge hangs while retrieving .torrent from URL

[Agent ME]

If you try to add a torrent from an URL, Deluge appears to stop completely until it gets a response from the server. I'm not sure if this causes other torrents being downloaded/uploaded to hiccup. This can be demonstrated with the Ubuntu torrents - http://www.ubuntu.com/getubuntu/downloadmirrors#bt - at least for me, right now, the server takes forever to retrieve any .torrent file.

If you try to add a torrent from a slow server through the webui, deluge doesn't seem to add the torrent at all.
EDIT: Seems like I'm having trouble adding torrents at all, even from a local file. For example, I just tried to add two torrents. Only one got added. I tried to add the other one. Nothing happens. I quit, start Deluge up again, and try to add the one again and it works. Looking at terminal output with debug logging on doesn't look like there's anything useful. It says "client:257 attempting to open *files*", and if one or more of them worked, for those ones it says "signals:89 torrent_added signal received.." and then "signals:90 torrent id: ...". Nothing about the failed torrents.

Also, if there's an error in retrieving the torrent from an URL (like a 404), Deluge doesn't tell you and just silently fails at adding the torrent.

Lastly, related to Deluge hanging - it seems in the gtkui the whole thing stops while its waiting for a response when you press "Test Active Port".

[andar]

Yea, these are known issues.. Work needs to be done to make them non-blocking, but I just haven't got around to fixing it yet.

[peakshysteria]

Just installed Deluge 1.1.0-RC1. Impossible to add any torrents at all. All torrents running in the previous version (1.0.7) loads seemingly without any visible problems. Adding .torrent's from links or drag and drop from folders doesn't help. The only .torrent's loaded are the one before the latest upgrade.

What gives? How can I add new files to Deluge?

[andar]

Just installed Deluge 1.1.0-RC1. Impossible to add any torrents at all. All torrents running in the previous version (1.0.7) loads seemingly without any visible problems. Adding .torrent's from links or drag and drop from folders doesn't help. The only .torrent's loaded are the one before the latest upgrade.

What gives? How can I add new files to Deluge?

Can you please take a look at the logs? I cannot reproduce this behaviour here.

[peakshysteria]

What is the command for viewing the logs?

[markybob]

What is the command for viewing the logs?

they're saved to ~/.config/deluge/deluge.log and ~/.config/deluge/deluged.log

[peakshysteria]

There is no deluge.log file in .config/deluge. deluged.log is empty.

[markybob]

There is no deluge.log file in .config/deluge. deluged.log is empty.

you could do:
deluged -d -L debug -l daemon.log
and deluge -L debug -l ui.log

[peakshysteria]

~/.config/deluge/deluge.log and ~/.config/deluge/deluged.log gives:

bash: /root/.config/deluge/deluge.log: No such file or directory
root@peaks-desktop:/home/peaks# deluged -d -L debug -l daemon.log
[DEBUG ] 00:16:27 configmanager:36 ConfigManager started..
[INFO ] 00:16:27 daemon:36 Deluge daemon 1.1.0-RC1
[DEBUG ] 00:16:27 daemon:37 options: {'loglevel': 'debug', 'quiet': False, 'logfile': 'daemon.log', 'config': None, 'port': None, 'pidfile': None, 'donot': True}
[DEBUG ] 00:16:27 daemon:38 args: []
[DEBUG ] 00:16:27 core:79 Core init..
[DEBUG ] 00:16:27 component:94 Registered Core with ComponentRegistry..
[DEBUG ] 00:16:27 component:94 Registered PreferencesManager with ComponentRegistry..
[DEBUG ] 00:16:27 configmanager:79 Getting config 'core.conf'
[WARNING ] 00:16:27 config:242 Unable to load config file: /root/.config/deluge/core.conf
[DEBUG ] 00:16:27 config:244 Config /root/.config/deluge/core.conf loaded: {'info_sent': 0.0, 'lsd': True, 'max_download_speed': -1.0, 'send_info': False, 'torrentfiles_location': '/root', 'state_location': '/root/.config/deluge/state', 'stop_seed_at_ratio': False, 'max_active_limit': 8, 'enc_in_policy': 1, 'queue_new_to_top': False, 'ignore_limits_on_local_network': True, 'rate_limit_ip_overhead': True, 'peer_tos': '0x00', 'daemon_port': 58846, 'natpmp': True, 'autoadd_enable': False, 'upnp': True, 'utpex': True, 'max_download_speed_per_torrent': -1, 'max_active_seeding': 5, 'allow_remote': False, 'outgoing_ports': [0, 0], 'max_half_open_connections': -1, 'enabled_plugins': [], 'plugins_location': '/root/.config/deluge/plugins', 'download_location': '/root', 'compact_allocation': False, 'max_upload_speed': -1.0, 'max_connections_global': 200, 'enc_prefer_rc4': True, 'listen_ports': [6881, 6891], 'dht': True, 'move_completed_path': '/root', 'stop_seed_ratio': 2.0, 'max_active_downloading': 3, 'prioritize_first_last_pieces': False, 'max_upload_speed_per_torrent': -1, 'auto_managed': True, 'enc_level': 2, 'copy_torrent_file': False, 'max_connections_per_second': 20, 'max_connections_per_torrent': -1, 'move_completed': False, 'proxies': {'peer': {'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}, 'web_seed': {'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}, 'tracker': {'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}, 'dht': {'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}}, 'dont_count_slow_torrents': False, 'add_paused': False, 'random_outgoing_ports': True, 'max_upload_slots_per_torrent': -1, 'new_release_check': True, 'enc_out_policy': 1, 'seed_time_ratio_limit': 7.0, 'remove_seed_at_ratio': False, 'autoadd_location': '/root', 'max_upload_slots_global': 4, 'config_location': '/root/.config/deluge', 'seed_time_limit': 180, 'share_ratio_limit': 2.0, 'random_port': True}
[DEBUG ] 00:16:27 configmanager:79 Getting config 'core.conf'
[INFO ] 00:16:27 core:98 Starting XMLRPC server on port 58846
[INFO ] 00:16:27 core:104 Daemon already running or port not available..

deluge -L debug -l ui.log gives:

1.1.0-RC1

[markybob]

well...obviously dont do it when there's already a deluge instance running and you shouldnt run deluge as root. ever. ever.
i think i see your problem. you were looking in root's config folder instead of whatever user you ran deluge with. then you stayed root and tried to run it as root