Opened 12 years ago

Closed 12 years ago

#1712 closed Bug (duplicate)

hang & no response when adding a torrent via transmission-remote

Reported by: shijun.wu Owned by: charles
Priority: Normal Milestone: None Set
Component: Daemon Version: 1.42+
Severity: Normal Keywords:
Cc:

Description

transmission-remote: (127.0.0.1:9092) server returned nothing (no headers, no data) this issue exists 1.5b2 & 1.4x

Change History (8)

comment:1 Changed 12 years ago by shijun.wu

found another issue when add torrent

transmission-remote: Unable to parse response " ?L?? `i?w?I??Dhl>?????????}?_j??RG?G??s?&??3?A?4?t?A????h???=s>??X??o??)?p???|??q?K'?K)??? ?us ?i?N???D

I]`?|????"Db/??e?W??l~?b?8?1?*?? ??h?w:?:q?w??}?4??m?6?"

comment:2 Changed 12 years ago by charles

works for me... if you're having problems you'll need to provide more information than this.

Can you log "transmission-remote --debug -a ${torrent-filename}" and attach that log to this ticket? That might shed some more information on the problem.

comment:3 Changed 12 years ago by shijun.wu

/usr/local/bin/transmission-remote 127.0.0.1:9092 --debug -l
posting:
--------
{
    "arguments": {
        "fields": [
            "eta", 
            "id", 
            "leftUntilDone", 
            "name", 
            "peersGettingFromUs", 
            "peersSendingToUs", 
            "rateDownload", 
            "rateUpload", 
            "sizeWhenDone", 
            "status", 
            "uploadRatio"
        ]
    }, 
    "method": "torrent-get", 
    "tag": 0
}

--------
* About to connect() to 127.0.0.1 port 9092 (#0)
*   Trying 127.0.0.1... * connected
* Connected to 127.0.0.1 (127.0.0.1) port 9092 (#0)
> POST /transmission/rpc HTTP/1.1
User-Agent: transmission-remote/1.50b2 (7735)
Host: 127.0.0.1:9092
Accept: */*
Content-Length: 473
Content-Type: application/x-www-form-urlencoded

comment:4 Changed 12 years ago by charles

I'm not understanding you here. what does the "transmission-remote -l" log have to do with the "add torrent failed" bug?

comment:5 Changed 12 years ago by shijun.wu

I think it's same bug, there are some issues in rpc communication. sounds like transmission-remote only get http header, there is no data part, then transmission-remote hungs.

comment:6 Changed 12 years ago by shijun.wu

call start a torrent, also hungs, it's same.

transmission-remote 127.0.0.1:9092 --debug -t35 --start
posting:
--------
{
    "arguments": {
        "ids": 35
    }, 
    "method": "torrent-start"
}

--------
* About to connect() to 127.0.0.1 port 9092 (#0)
*   Trying 127.0.0.1... * connected
* Connected to 127.0.0.1 (127.0.0.1) port 9092 (#0)
> POST /transmission/rpc HTTP/1.1
User-Agent: transmission-remote/1.50b2 (7735)
Host: 127.0.0.1:9092
Accept: */*
Content-Length: 79
Content-Type: application/x-www-form-urlencoded

comment:7 Changed 12 years ago by charles

hm. This sounds like it might be the same bug as in #1316...

comment:8 Changed 12 years ago by charles

  • Resolution set to duplicate
  • Status changed from new to closed
  • Summary changed from transmission remote add torrent failed to hang & no response when adding a torrent via transmission-remote
Note: See TracTickets for help on using tickets.