[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #3731 [Tor Client]: fetch_from_evbuffer_socks claims to be borken

To: undisclosed-recipients:;
Subject: [tor-bugs] #3731 [Tor Client]: fetch_from_evbuffer_socks claims to be borken
From: "Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>
Date: Sun, 14 Aug 2011 10:44:26 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Sun, 14 Aug 2011 06:44:35 -0400
List-archive: <http://lists.torproject.org/pipermail/tor-bugs>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: Tor bug tracker status mails <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
Reply-to: tor-assistants@xxxxxxxxxxxxxx
Sender: tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx

#3731: fetch_from_evbuffer_socks claims to be borken
--------------------------+-------------------------------------------------
 Reporter:  rransom       |          Owner:                    
     Type:  defect        |         Status:  new               
 Priority:  normal        |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client    |        Version:                    
 Keywords:  bufferevents  |         Parent:                    
   Points:                |   Actualpoints:                    
--------------------------+-------------------------------------------------
 Using Firefox 5.0.1 for Windows with `vidalia-bundle-0.2.3.2-alpha-
 bufferevents-0.3.0-alpha.exe`:
 {{{
 Aug 14 03:29:24.498 [Notice] Tor v0.2.3.2-alpha (git-bceb136840815bf5).
 This is experimental software. Do not rely on it for strong anonymity.
 (Running on Windows 7  [workstation])
 Aug 14 03:29:24.498 [Notice] Read configuration file
 "C:\Users\rransom\AppData\Roaming\Vidalia\torrc".
 Aug 14 03:29:24.498 [Notice] Initialized libevent version 2.0.13-stable
 using method win32. Good.
 Aug 14 03:29:24.498 [Notice] Opening Socks listener on 127.0.0.1:9050
 Aug 14 03:29:24.498 [Notice] Opening Control listener on 127.0.0.1:9051
 Aug 14 03:29:24.716 [Notice] Based on 100 circuit times, it looks like we
 don't need to wait so long for circuits to finish. We will now assume a
 circuit is too slow to use after waiting 4 seconds.
 Aug 14 03:29:24.716 [Notice] Parsing GEOIP file
 C:\Users\rransom\AppData\Roaming\tor\geoip.
 Aug 14 03:29:24.934 [Notice] Configured to measure statistics. Look for
 the *-stats files that will first be written to the data directory in 24
 hours from now.
 Aug 14 03:29:28.117 [Notice] OpenSSL OpenSSL 1.0.0d 8 Feb 2011 looks like
 version 0.9.8m or later; I will try SSL_OP to enable renegotiation
 Aug 14 03:29:28.117 [Notice] Reloaded microdescriptor cache.  Found 0
 descriptors.
 Aug 14 03:29:28.117 [Notice] We now have enough directory information to
 build circuits.
 Aug 14 03:29:28.117 [Notice] Bootstrapped 80%: Connecting to the Tor
 network.
 Aug 14 03:29:28.117 [Notice] New control connection opened.
 Aug 14 03:29:28.460 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 2
 circuits open. I've pushed 0 kB and received 0 kB.
 Aug 14 03:29:29.006 [Notice] Bootstrapped 85%: Finishing handshake with
 first hop.
 Aug 14 03:29:31.658 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
 Aug 14 03:29:32.064 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:29:34.092 [Notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Aug 14 03:29:34.092 [Notice] Bootstrapped 100%: Done.
 Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:29:45.510 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:30:13.871 [Notice] Based on 108 circuit times, it looks like we
 need to wait longer for circuits to finish. We will now assume a circuit
 is too slow to use after waiting 5 seconds.
 Aug 14 03:30:50.235 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:30:57.052 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:30:57.083 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:30:58.472 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:31:32.792 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:31:42.464 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:31:42.511 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:31:51.419 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:31:52.230 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:35:44.499 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:35:53.703 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:35:53.781 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:39:51.014 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 Aug 14 03:40:06.286 [Warning] fetch_from_evbuffer_socks(): Bug: We seem to
 be caught in a parse loop; breaking out
 }}}

 The `fetch_from_evbuffer_socks` 'Bug' messages are still occurring.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3731>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Follow-Ups:
- Re: [tor-bugs] #3731 [Tor Client]: fetch_from_evbuffer_socks claims to be borken
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #3731 [Tor Client]: fetch_from_evbuffer_socks claims to be borken
  - From: Tor Bug Tracker & Wiki

Prev by Author: Re: [tor-bugs] #3245 [Tor Relay]: When using TOR as Windows Service, torrc options are NOT loaded
Next by Author: Re: [tor-bugs] #2342 [Tor bundles/installation]: polipo sample config dnsUseGethostbyname=yes obsolete?
Previous by thread: Re: [tor-bugs] #3245 [Tor Relay]: When using TOR as Windows Service, torrc options are NOT loaded
Next by thread: Re: [tor-bugs] #3731 [Tor Client]: fetch_from_evbuffer_socks claims to be borken
Index(es):
- Author
- Thread