Corrupt/blank/missing torrent information

[enigma]

Recently, all of my torrents have become blank, as seen in this screenshot:



When this occurred, I was running Deluge 1.0.4, installed from the deb package from the Deluge website. (I've since upgraded to 1.0.5 without effect.) I'm running Ubuntu 8.10 32-bit on a fairly new system (Core 2 Quad Q6600, 2GiB RAM.)

Is there anyway I can force a rebuild of the pickled data in the torrent.state file?

Thanks,

--E

(Edited to add OS and system information.)

[enigma]

I've just noticed something curious: The 'details' tab still shows the correct information for all torrents.

I'm guessing the main list is cached somewhere, while the 'details' are looked up directly.

I'm guessing I somehow need to force that cache to rebuild.

Any ideas?

[markybob]

see if there are any errors shown in ~/.config/deluge/deluged.log
also, start deluge's gtkui from a command prompt, and see if it outputs any errors when that happens.

[enigma]

Several errors of this form appear in the daemon log:

Code: Select all

[DEBUG   ] 22:48:32 torrentmanager:664 on_alert_tracker_reply
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 57156)
Traceback (most recent call last):
  File "/usr/lib/python2.5/SocketServer.py", line 464, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib/python2.5/SocketServer.py", line 254, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python2.5/SocketServer.py", line 522, in __init__
    self.handle()
  File "/usr/lib/python2.5/BaseHTTPServer.py", line 316, in handle
    self.handle_one_request()
  File "/usr/lib/python2.5/BaseHTTPServer.py", line 310, in handle_one_request
    method()
  File "/var/lib/python-support/python2.5/deluge/SimpleXMLRPCServer.py", line 485, in do_POST
    self.connection.shutdown(1)
  File "<string>", line 1, in shutdown
error: (107, 'Transport endpoint is not connected')
----------------------------------------
[DEBUG   ] 22:48:56 torrent:555 Saving fastresume file: /home/[redacted]/.config/deluge/state/c6[redacted]11.fastresume

Several errors such as the following appear in the gtk client stderr:

Code: Select all

[WARNING ] 00:19:37 client:103 Multi-call Exception: not well-formed (invalid token): line 3189, column 20:not well-formed (invalid token): line 3189, column 20

I'm happy to send the logs to whatever address you'd like, but I'm not comfortable posting them where the Internet at large can see them.

Thanks for looking into this!

--E.

[andar]

Several errors of this form appear in the daemon log:

Code: Select all

[DEBUG   ] 22:48:32 torrentmanager:664 on_alert_tracker_reply
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 57156)
Traceback (most recent call last):
  File "/usr/lib/python2.5/SocketServer.py", line 464, in process_request_thread
    self.finish_request(request, client_address)
  File "/usr/lib/python2.5/SocketServer.py", line 254, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python2.5/SocketServer.py", line 522, in __init__
    self.handle()
  File "/usr/lib/python2.5/BaseHTTPServer.py", line 316, in handle
    self.handle_one_request()
  File "/usr/lib/python2.5/BaseHTTPServer.py", line 310, in handle_one_request
    method()
  File "/var/lib/python-support/python2.5/deluge/SimpleXMLRPCServer.py", line 485, in do_POST
    self.connection.shutdown(1)
  File "<string>", line 1, in shutdown
error: (107, 'Transport endpoint is not connected')
----------------------------------------
[DEBUG   ] 22:48:56 torrent:555 Saving fastresume file: /home/[redacted]/.config/deluge/state/c6[redacted]11.fastresume

Several errors such as the following appear in the gtk client stderr:

Code: Select all

[WARNING ] 00:19:37 client:103 Multi-call Exception: not well-formed (invalid token): line 3189, column 20:not well-formed (invalid token): line 3189, column 20

I'm happy to send the logs to whatever address you'd like, but I'm not comfortable posting them where the Internet at large can see them.

Thanks for looking into this!

--E.

Maybe there is some sort of weird encoding used in one of the torrents name.. Anything you can see in your torrent list that looks unusual?

[enigma]

Paydirt!

One of the torrent names had extended ASCII character 0xB4 in place of an apostrophe. (Normal <128 ASCII characters follow.)

Renaming the .torrent and .fastresume files ~/.config/deluge/state "solved" the problem.

Thanks for the help!

Shall I file a separate bug report, or will you take care of this in trunk?

--E.

[andar]

Paydirt!

One of the torrent names had extended ASCII character 0xB4 in place of an apostrophe. (Normal <128 ASCII characters follow.)

Renaming the .torrent and .fastresume files ~/.config/deluge/state "solved" the problem.

Thanks for the help!

Shall I file a separate bug report, or will you take care of this in trunk?

--E.

Could you send me the torrent so I can reproduce it?

[enigma]

Of course.

Can I ask for an e-mail address, or some other non-public way of sending it?

--E.

[andar]

Of course.

Can I ask for an e-mail address, or some other non-public way of sending it?

--E.

andrewresch@gmail.com

[enigma]

Done. Cheers!

--E.