[tor-bugs] Re: #1357 [Tor - Relay]: Generated a synthetic timeout LESS than the current timeout

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#1357: Generated a synthetic timeout LESS than the current timeout
--------------------------+-------------------------------------------------
  Reporter:  stars        |       Owner:  mikeperry         
      Type:  defect       |      Status:  closed            
  Priority:  minor        |   Milestone:  Tor: 0.2.2.x-final
 Component:  Tor - Relay  |     Version:  0.2.2.10-alpha    
Resolution:  fixed        |    Keywords:                    
    Parent:               |  
--------------------------+-------------------------------------------------
Changes (by mikeperry):

  * status:  new => closed
  * resolution:  None => fixed


Old description:

> Hello,
>
> I think have spoke a few months ago about this bug but don't find any
> report, so i make one now.
>
> If the FAI have trouble and i.e the network are done a few second, Tor
> must recalculate the timeout when resume and at this time it create the
> warning about " Generated a synthetic timeout LESS than the current
> timeout: 50089ms vs 60000.000000ms using Xm: 1275 a: 0.467440, q:
> 0.800000".
>
> I running kubuntu karmic 9.10 x86 64  2.6.31-21-generic #59-Ubuntu SMP
> Wed Mar 24 07:28:27 UTC 2010 x86_64 GNU/Linux
>
> Tor: commit 7221d15acc87d2438aba7e3c261c2fc460479a01   0.2.2.10 alpha-dev
> but previous version contain the same bug
> Libevent: commit 3cbca8661f2ad267ca890304a3dc5acefb8ba630
>

> avr. 13 17:08:59.534 [Notice] Network is flaky. No activity for 96
> seconds. Temporarily raising timeout to 60s.
> avr. 13 17:09:19.616 [Notice] Tried for 120 seconds to get a connection
> to [scrubbed]:0. Giving up. (waiting for circuit)
> avr. 13 17:09:48.839 [Notice] Network activity has resumed. Resuming
> circuit timeout calculations.
> avr. 13 17:09:48.840 [Warning] Generated a synthetic timeout LESS than
> the current timeout: 50089ms vs 60000.000000ms using Xm: 1275 a:
> 0.467440, q: 0.800000
>
> Best Regards
>
> SwissTorExit
>
> [Automatically added by flyspray2trac: Operating System: Other Linux]

New description:

 Hello,

 I think have spoke a few months ago about this bug but don't find any
 report, so i make one now.

 If the FAI have trouble and i.e the network are done a few second, Tor
 must recalculate the timeout when resume and at this time it create the
 warning about " Generated a synthetic timeout LESS than the current
 timeout: 50089ms vs 60000.000000ms using Xm: 1275 a: 0.467440, q:
 0.800000".

 I running kubuntu karmic 9.10 x86 64  2.6.31-21-generic #59-Ubuntu SMP Wed
 Mar 24 07:28:27 UTC 2010 x86_64 GNU/Linux

 Tor: commit 7221d15acc87d2438aba7e3c261c2fc460479a01   0.2.2.10 alpha-dev
 but previous version contain the same bug
 Libevent: commit 3cbca8661f2ad267ca890304a3dc5acefb8ba630


 avr. 13 17:08:59.534 [Notice] Network is flaky. No activity for 96
 seconds. Temporarily raising timeout to 60s.
 avr. 13 17:09:19.616 [Notice] Tried for 120 seconds to get a connection to
 [scrubbed]:0. Giving up. (waiting for circuit)
 avr. 13 17:09:48.839 [Notice] Network activity has resumed. Resuming
 circuit timeout calculations.
 avr. 13 17:09:48.840 [Warning] Generated a synthetic timeout LESS than the
 current timeout: 50089ms vs 60000.000000ms using Xm: 1275 a: 0.467440, q:
 0.800000

 Best Regards

 SwissTorExit

 [Automatically added by flyspray2trac: Operating System: Other Linux]

--

Comment:

 Fix should appear in 0.2.2.14.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1357#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online