Opened 15 years ago

Closed 14 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:

Description (last modified by andar)

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 Changed 15 years ago by anonymous

Ran into it again. Completely reproducible on current Debian: 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

comment:2 Changed 15 years ago by andar

  • Description modified (diff)
  • Resolution set to invalid
  • Status changed from new to closed

comment:3 Changed 14 years ago by punkoff

  • Component changed from other to core
  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Version changed from 1.1.0_RC3 to 1.2.0_rc4

Still 100% reproducable on Debian Sid, deluged 1.2.0~rc4

comment:4 Changed 14 years ago by arvid

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 Changed 14 years ago by arvid

  • Cc added

comment:6 Changed 14 years ago by andar

  • Status changed from reopened to pending

comment:7 Changed 14 years ago by trac-robot

  • Status changed from pending to 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.

Note: See TracTickets for help on using tickets.