Adding torrents in list doesn't work, but download starts

General support for problems installing or using Deluge
Post Reply
Boten

Adding torrents in list doesn't work, but download starts

Post by Boten »

I use Deluge 1.1.0 in Ubuntu 8.10. Before yesterday everything was good, but yesterday I saw a big trouble: when I add torrents, download successfully starts, but this torrent doesn't add in torrents list. (I detected download by increasing speed in status bar). I've cleaned everywhere in ~/.config/deluge except state/ and torrentfiles/ directories, my problem was not solved. Today I've updated Deluge to 1.1.1, however, adding torrents still doesn't work. Moreover, I saw that new torrents in torrentfiles/ directory don't create.
Here are some strings from debug log of deluged when I'm trying to add the torrent:

Code: Select all

[WARNING ] 13:18:05 signalmanager:103 Unable to emit signal to client <ServerProxy for my-ip:47169/RPC2>: (111, 'Connection refused') (30)
There are very many messages like that, but after these there is one info message appears:

Code: Select all

[INFO    ] 13:18:05 signalmanager:107 Removing http://my-ip:47169 because it couldn't be reached..
Seems like the daemon cannot connect to GUI client. But I don't know how it can happen.
How can I fix this problem? Cleaning torrentfiles/ directory is not a true variant. Help me!
Top
Specs
New User
New User
Posts: 3
Joined: Thu Feb 05, 2009 2:35 pm

Re: Adding torrents in list doesn't work, but download starts

Post by Specs »

I can also confirm i am having the problem of:

Code: Select all

[WARNING ] 17:44:21 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (23)
[WARNING ] 17:44:21 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (23)
[WARNING ] 17:44:21 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (23)
[WARNING ] 17:44:24 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (24)
[WARNING ] 17:44:24 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (24)
[WARNING ] 17:44:24 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (24)
[WARNING ] 17:44:27 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (24)
[WARNING ] 17:44:27 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (24)
[WARNING ] 17:44:27 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (25)
[WARNING ] 17:44:30 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (25)
[WARNING ] 17:44:30 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (25)
[WARNING ] 17:44:30 signalmanager:103 Unable to emit signal to client <ServerProxy for 192.168.1.131:54986/RPC2>: (113, 'No route to host') (25)
It just goes on and on :(
Is there anyway to fix this?
Top
Post Reply

Return to “Support”