Re: [btqueue-users] Timeouts
Status: Beta
Brought to you by:
xgie
From: Sugree P. <su...@hp...> - 2004-12-01 17:34:46
|
What about repeatly calling "btqueue.py query"? If you get timeout, the problem might be connectivity to some of tracker to refresh scrape since 0.0.17 has a bug to get all scrapes including waiting ones. Chris Picton wrote: > Hi Sugree, thanks for the quick reply. > > On Tue, 2004-11-30 at 20:38, Sugree Phatanapherom wrote: > >>Timeout usually causes by the queue being locked by schedule thread. >>Normally, the schedule thread should release the lock quickly but it >>might be slower if you have lots of torrent in the queue. Major delay >>are of gathering scrape. There is a minor bug here. BTQueue older than >>0.0.18 will still try to get scrape information of all torrents in queue >>including finished ones. > > > I am using BTQueue-0.0.17-242.2.3. This seems to be the latest version. > Is 0.0.18 going to be released soon? > > I currently have in my queue: > 1 finished > 1 seeding > 3 downloading > 21 waiting. > > > >>Another possible problem is DNS. BTQueue will temporarily not response >>if it is querying DNS. > > My DNS is fine - All resolutions happen quickly. > > > My real issue (and it may help you fix the problem as well), is that > 'btqueue query' is quick, but running 'list' inside the remote shell > times out. > > Chris > -- Sugree Phatanapherom su...@hp... |