btqueue-users

[btqueue-users] Timeouts

[Chris P. <ch...@ta...>]

Hi there

Why would I be getting the following:

I am running btqueue.py daemon to start btqueue.

I can run btqueue.py query, and it returns the results in under a
second.

When I run 
btqueue.py remote
>>> list

I get the following:
--------
Traceback (most recent call last):
  File "/usr/lib/python2.2/site-packages/BitQueue/manager.py", line
1502, in mainloop
    self.cmdloop()
  File "/usr/lib/python2.2/cmd.py", line 123, in cmdloop
    stop = self.onecmd(line)
  File "/usr/lib/python2.2/cmd.py", line 200, in onecmd
    return func(arg)
  File "/usr/lib/python2.2/site-packages/BitQueue/manager.py", line
1626, in do_list
    res = self.manager.do_list(line)
  File "/usr/lib/python2.2/site-packages/BitQueue/xmlrpc.py", line 124,
in __call__
    dict = self.__send(self.__name,(self.__id,)+args)
  File "/usr/lib/python2.2/site-packages/BitQueue/xmlrpc.py", line 164,
in __request
    verbose=self.__verbose
  File "/usr/lib/python2.2/xmlrpclib.py", line 842, in request
    errcode, errmsg, headers = h.getreply()
  File "/usr/lib/python2.2/httplib.py", line 1009, in getreply
    response = self._conn.getresponse()
  File "/usr/lib/python2.2/httplib.py", line 760, in getresponse
    response.begin()
  File "/usr/lib/python2.2/httplib.py", line 269, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python2.2/httplib.py", line 231, in _read_status
    line = self.fp.readline()
  File "/usr/lib/python2.2/site-packages/BitQueue/timeoutsocket.py",
line 381, in readline
    buf = self.recv(bufsize)
  File "/usr/lib/python2.2/site-packages/BitQueue/timeoutsocket.py",
line 298, in recv
    raise Timeout("Recv timed out")
Timeout: Recv timed out
------------


I get the same timeout for most commands run from btqueue.py remote

Any ideas

Chris

Re: [btqueue-users] Timeouts

[Sugree P. <su...@hp...>]

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.

Another possible problem is DNS. BTQueue will temporarily not response 
if it is querying DNS.

Hope this helps,

Chris Picton wrote:
> Hi there
> 
> Why would I be getting the following:
> 
> I am running btqueue.py daemon to start btqueue.
> 
> I can run btqueue.py query, and it returns the results in under a
> second.
> 
> When I run 
> btqueue.py remote
> 
>>>>list
> 
> 
> I get the following:
> --------
> Traceback (most recent call last):
>   File "/usr/lib/python2.2/site-packages/BitQueue/manager.py", line
> 1502, in mainloop
>     self.cmdloop()
>   File "/usr/lib/python2.2/cmd.py", line 123, in cmdloop
>     stop = self.onecmd(line)
>   File "/usr/lib/python2.2/cmd.py", line 200, in onecmd
>     return func(arg)
>   File "/usr/lib/python2.2/site-packages/BitQueue/manager.py", line
> 1626, in do_list
>     res = self.manager.do_list(line)
>   File "/usr/lib/python2.2/site-packages/BitQueue/xmlrpc.py", line 124,
> in __call__
>     dict = self.__send(self.__name,(self.__id,)+args)
>   File "/usr/lib/python2.2/site-packages/BitQueue/xmlrpc.py", line 164,
> in __request
>     verbose=self.__verbose
>   File "/usr/lib/python2.2/xmlrpclib.py", line 842, in request
>     errcode, errmsg, headers = h.getreply()
>   File "/usr/lib/python2.2/httplib.py", line 1009, in getreply
>     response = self._conn.getresponse()
>   File "/usr/lib/python2.2/httplib.py", line 760, in getresponse
>     response.begin()
>   File "/usr/lib/python2.2/httplib.py", line 269, in begin
>     version, status, reason = self._read_status()
>   File "/usr/lib/python2.2/httplib.py", line 231, in _read_status
>     line = self.fp.readline()
>   File "/usr/lib/python2.2/site-packages/BitQueue/timeoutsocket.py",
> line 381, in readline
>     buf = self.recv(bufsize)
>   File "/usr/lib/python2.2/site-packages/BitQueue/timeoutsocket.py",
> line 298, in recv
>     raise Timeout("Recv timed out")
> Timeout: Recv timed out
> ------------
> 
> 
> I get the same timeout for most commands run from btqueue.py remote
> 
> Any ideas
> 
> Chris


-- 
Sugree Phatanapherom
su...@hp...

Re: [btqueue-users] Timeouts

[Chris P. <ch...@ta...>]

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

Re: [btqueue-users] Timeouts

[Sugree P. <su...@hp...>]

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...

Re: [btqueue-users] Timeouts

[Sugree P. <su...@hp...>]

I have found timeout problem too. It seems like something went wrong 
during xmlrpc call and made xmlrpc interface to malfunction until 
restart. I am trying to dig into the code to find the problem.

Sugree Phatanapherom wrote:
> 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...