New torrent added -- cryptic error message; gui no longer works

[GoogleCodeExporter]

I am using 4.1.

I downloaded a torrent file from my browser and sent it to trans-gui as always.

But when it went to do a status update,
(and still), I get:

Error at line 1, Pos 2037: Expected, or ], got token "{"...

And that's all I get now.  

I can look via the command line and see things are still running, but the GUI 
seems MIA.

The last 2 lines from listing things with 
the cmd-line transmission-remote (trm) are:
 444   100%   383.2 MB  8 hrs       35.0     0.0   0.26  Seeding      [gg]_Shingeki_no_Kyojin_-_03v3_[4F3140DA].mkv
 446   100%   422.5 MB  Done        66.0     0.0   0.31  Seeding      [Anime-Koi] Karneval - 04 [h264-720p][FC7501E6].mkv
Sum:           2.46 TB             798.0     0.0

There doesn't seem to be anything weird in those names anymore than other 
names...??  Ideas?

transmission version:
transmission-daemon 2.75 (13675)
transmission-remote 2.75 (13675)

Original issue reported on code.google.com by astara.a...@gmail.com on 26 Apr 2013 at 5:56

[GoogleCodeExporter]

Attached is the conversation as seen by wireshark -- I think it's the last line 
it may be complaining about since no other line is >2000 chars long.

Unfortunately, 2037 ends in the middle of a word -- maybe a buffer overflow 
somewhere?

Original comment by astara.a...@gmail.com on 26 Apr 2013 at 9:25

Attachments:

• conv2.txt

[GoogleCodeExporter]

Is web interface working for you? Try select the torrent in the web ui and 
click on all property tabs.
It may be due to this issue:
https://trac.transmissionbt.com/ticket/4882

Original comment by j...@cp-lab.com on 27 Apr 2013 at 8:54

• Changed state: Feedback

[GoogleCodeExporter]

What do the symptoms look like?

I.e. when I connect to it w/a browser I get a partial interface, but I also get
a Connection failed message and that it could not connect to the server -- with 
the transmission icon next to the message.   If that's the way it manifests on 
the rpc server... then yes, if I should see some similar message about some 
illegal char or something, then no.   

That said -- transmission-remote (from the CLI) DOES work for listing and 
control.  Since the symptom appeared after I added 2 new torrents, I tried 
deleting those torrents from the CLI -- made no difference.

It wasn't clear in that bug report, but doesn't the CLI use the RPC as well to 
talk to the server?  Shouldn't it be similarly affected?

Original comment by astara.a...@gmail.com on 27 Apr 2013 at 5:40

[GoogleCodeExporter]

If the web ui is also experiencing problems then it is indeed wrong JSON passed 
by the daemon via RPC.

According to the bug report https://trac.transmissionbt.com/ticket/4882 the 
problem is in a error string received from a tracker. Transmission daemon does 
not properly encode the string.
Try to request trackers status for all torrents in transmission-remote and I 
suppose it also produce parsing errors.

Original comment by j...@cp-lab.com on 27 Apr 2013 at 7:54

[GoogleCodeExporter]

Not the same problem ... but still a problem in transmission:
This was the output of "trm -t 1 -it":
(trm=tr-remote)
-------------------------------------
[13:14:07.306] JSON parse failed at pos 1582: STRAY_TOKEN -- remaining text 
""result""success"
[13:14:07.306] transmission-remote: Unable to parse response 
"{"arguments":{"torrents":[{"trackerStats":[{"announce":"http://tracker.bakabt.m
e:2710/0123456789abcdef0123456789abcdef/announce.php","announceState":1,"downloa
dCount":-1,"hasAnnounced":true,"hasScraped":true,"host":"http://tracker.bakabt.m
e:2710","id":0,"isBackup":false,"lastAnnouncePeerCount":3,"lastAnnounceResult":"
Success","lastAnnounceStartTime":1367092974,"lastAnnounceSucceeded":true,"lastAn
nounceTime":1367092976,"lastAnnounceTimedOut":false,"lastScrapeResult":"Tracker 
gave HTTP response code 0 (No 
Response)","lastScrapeStartTime":1367093500,"lastScrapeSucceeded":true,"lastScra
peTime":1367093501,"lastScrapeTimedOut":0,"leecherCount":8,"nextAnnounceTime":13
67094776,"nextScrapeTime":1367096510,"scrape":"http://tracker.bakabt.me:2710/012
3456789abcdef0123456789abcdef/scrape.php","scrapeState":1,"seederCount":33,"tier
":0},{"announce":"http://tracker.bakabt.me:2710/announce.php?0123456789abcdef012
3456789abcdef","announceState":1,"downloadCount":-1,"hasAnnounced":true,"hasScra
ped":tru

-----------------------------------

Note there is no UTF-8.  but also note that the amount of text from the 
beginning of the first argument to where it cuts off is exactly 1024 bytes.  
Looks like they didn't allocate enough space for the response.

Original comment by astara.a...@gmail.com on 27 Apr 2013 at 8:19

[GoogleCodeExporter]

I've inspected the conv2.txt file and indeed, the daemon returns wrong JSON. It 
misses commas in some places. And I don't know why.
Since it's a daemon issue it is better to post your findings here:
https://trac.transmissionbt.com/ticket/4882 

I am closing the issue here.

Original comment by j...@cp-lab.com on 27 Apr 2013 at 8:29

• Changed state: NoChange