On 2/1/08, Chris Lawrence <[EMAIL PROTECTED]> wrote:
> After debtorrent-client has been up for a while and a mirror pulse has
> occurred, requests for newly-available packages appear to get stuck
> (it appears they are not handed off to be downloaded).  The following
> messages are repeated ad nauseum in debtorrent-client.log:
>
> 2008-02-02 01:26:13,381 MainThread DebTorrent.BT1.AptListener DEBUG
> pieces needed: [30009, 29878, 30085, 30086, 30087, 30088, 29916,
> 30114, 30115, 30116, 30117, 30118, 30119, 30120, 30121, 30122, 30015,
> 30016, 30017, 30018, 30019, 30020, 30021, 30022, 30002, 30073, 29965,
> 29966]
> 2008-02-02 01:26:13,381 MainThread DebTorrent.BT1.AptListener DEBUG
> pieces needed: [29623, 29624, 29630, 29631]
> 2008-02-02 01:26:13,382 MainThread DebTorrent.BT1.AptListener DEBUG
> file needed: 13364288 from [29623, 29624, 29630, 29631]

Unfortunately, I can't tell what's going on from these messages. If
possible, could you find the relevant section of the log file,
starting from where the download begins, and somehow get it to me. I
know it's probably large, so compressing is probably needed.

> My suspicion is that something (the available pieces map, maybe?)
> isn't getting internally refreshed when the torrent gets bigger due to
> updated packages being available.  Restarting debtorrent-client
> resolves the problem.

The torrent only gets bigger due to an apt-get update, which causes
the old (smaller) torrent to be stopped and the new (larger) one to be
started. That's similar to restarting the client, so I'm not sure
that's the source of the problem. Unless you have done an apt-get
update while a download was under way, which would probably cause
problems.

The problem might lie in the HTTPDownloader getting stuck, which has
been reported once by another user. There are currently no time-outs
in it, so if it gets stuck, the pieces you are waiting for might never
download. I should be able to tell from the log file if that's the
case.

Thanks,
Cameron



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to