Opened 16 years ago
Closed 15 years ago
#709 closed bug
ENOSPACE gets reported as "invalid bencoding" tracker problem
| Reported by: | anonymous | Owned by: | andar |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | 1.2.0_rc4 |
| Keywords: | Cc: | arvid@cs.umu.se |
Description (last modified by )
I kept getting an error condition on a torrent, the condition being reported as an invalid tracker ("invalid bencoding" etcetc was the Status message). After wasting an hour or so playing with trackers and so forth, I discovered that the problem was just that the partition the torrent is on had filled up.
Change History (7)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
comment:3 by , 15 years ago
| Component: | other → core |
|---|---|
| Resolution: | invalid |
| Status: | closed → reopened |
| Version: | 1.1.0_RC3 → 1.2.0_rc4 |
Still 100% reproducable on Debian Sid, deluged 1.2.0~rc4
comment:4 by , 15 years ago
Could you try wiresharking the tracker connection and post the full tracker response?
The only place this error can be reported is if the data that comes back from the tracker doesn't parse. The invalid response could perhaps be triggered by something related to the disk being full.
comment:5 by , 15 years ago
| Cc: | added |
|---|
comment:6 by , 15 years ago
| Status: | reopened → pending |
|---|
comment:7 by , 15 years ago
| Status: | pending → closed |
|---|
This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.
Ran into it again. Completely reproducible on current Debian:
thepiratebay.org: Error: invalid bencoding of tracker response: "d8:completei23e10:incompletei2e8:intervali1" Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb9 76896316 72990108 8 100% /big