[tor-bugs] #16992 [Tor]: "[warn] Failure from drain_fd" in Tor v0.2.7.2-alpha (git-36c0ae6f7834af16) running on Windows XP

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Sep 7 06:15:33 UTC 2015


#16992: "[warn] Failure from drain_fd" in Tor v0.2.7.2-alpha (git-36c0ae6f7834af16)
running on Windows XP
---------------------+------------------------------------
 Reporter:  TORques  |          Owner:
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:  Tor: 0.2.7.x-final
Component:  Tor      |        Version:  Tor: 0.2.7.2-alpha
 Keywords:           |  Actual Points:
Parent ID:           |         Points:
---------------------+------------------------------------
 What exactly means this warning? My OS can't handle the multithreading
 nonblocking reads from a circuit stream? I use "NumCPUs 2" in torrc file.
 My OS settings are raised to performance (tcpsys changed to 256
 connections, 1 Gbit internet, MTU 1492, tcp window raised,...).

 I run a non-exit relay from a cmd command line window with Tor
 v0.2.7.2-alpha (git-36c0ae6f7834af16) running on Windows XP with Libevent
 2.0.22-stable, OpenSSL 1.0.2d and Zlib 1.2.8. compiled by myself.

 {{{
 Sep 07 07:59:01.000 [info] evaluate_evp_for_aes(): This version of OpenSSL
 has a known-good EVP counter-mode implementation. Using it.
 }}}
 Also, my router seems to be very restrictive even though I have opened the
 required ports in firewall and the port forwarding was done.
 {{{
 Starting Nmap 6.47 ( http://nmap.org ) at 2015-09-07 09:07 GTB Daylight
 Time
 Initiating SYN Stealth Scan at 09:08
 Scanning torques.ed25519.edu (109.103.57.102) [65535 ports]
 Discovered open port 53/tcp on 109.103.57.102
 Discovered open port 80/tcp on 109.103.57.102
 Discovered open port 9001/tcp on 109.103.57.102
 Discovered open port 7547/tcp on 109.103.57.102 (this port is reserved by
 router for updates, etc.)
 Discovered open port 9030/tcp on 109.103.57.102
 Completed SYN Stealth Scan at 09:08, 23.97s elapsed (65535 total ports)
 }}}
 The relay server looks to work as expected only from the router DMZ.

 {{{
 Sep 07 07:59:00.000 [notice] Tor 0.2.7.2-alpha (git-36c0ae6f7834af16)
 opening log file.
 Sep 07 07:59:00.437 [notice] Tor v0.2.7.2-alpha (git-36c0ae6f7834af16)
 running on Windows XP with Libevent 2.0.22-stable, OpenSSL 1.0.2d and Zlib
 1.2.8.
 Sep 07 07:59:00.437 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Sep 07 07:59:00.437 [notice] This version is not a stable Tor release.
 Expect more bugs than usual.
 Sep 07 07:59:00.546 [notice] Read configuration file "path".
 Sep 07 07:59:00.562 [notice] Based on detected system memory,
 MaxMemInQueues is set to 2048 MB. You can override this by setting
 MaxMemInQueues by hand.
 Sep 07 07:59:00.750 [notice] Opening Socks listener on 127.0.0.1:9050
 Sep 07 07:59:00.750 [notice] Opening DNS listener on 127.0.0.1:53
 Sep 07 07:59:00.750 [notice] Opening Control listener on 127.0.0.1:9151
 Sep 07 07:59:00.765 [notice] Opening OR listener on 0.0.0.0:9001
 Sep 07 07:59:00.796 [notice] Opening Directory listener on 0.0.0.0:9030
 Sep 07 07:59:00.000 [warn] Your log may contain sensitive information -
 you're logging more than "notice". Don't log unless it serves an important
 reason. Overwrite the log afterwards.
 Sep 07 07:59:01.000 [notice] Parsing GEOIP IPv4 file "path".
 Sep 07 07:59:01.000 [notice] Parsing GEOIP IPv6 file "path".
 Sep 07 07:59:01.000 [notice] Your Tor server's identity key fingerprint is
 'TORques CD0EB85333B9A20F6D676605F01CC5143E69F82F'
 Sep 07 07:59:01.000 [notice] Bootstrapped 0%: Starting
 Sep 07 07:59:14.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network
 Sep 07 07:59:15.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop
 Sep 07 07:59:15.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
 Sep 07 07:59:17.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Sep 07 07:59:17.000 [notice] Bootstrapped 100%: Done
 Sep 07 07:59:17.000 [notice] Now checking whether ORPort
 109.103.57.102:9001 and DirPort 109.103.57.102:9030 are reachable... (this
 may take up to 20 minutes -- look for log messages indicating success)
 Sep 07 07:59:18.000 [notice] Self-testing indicates your DirPort is
 reachable from the outside. Excellent.
 Sep 07 07:59:18.000 [info] connection_free_(): Freeing linked Directory
 connection [client finished] with 0 bytes on inbuf, 0 on outbuf.
 Sep 07 07:59:18.000 [info] channel_tls_process_versions_cell(): Negotiated
 version 4 with [scrubbed]:50560; Sending cells: VERSIONS CERTS
 AUTH_CHALLENGE NETINFO
 Sep 07 07:59:18.000 [info] router_pick_published_address(): Success: chose
 address '109.103.57.102'.
 Sep 07 07:59:18.000 [info] router_rebuild_descriptor(): Rebuilding relay
 descriptor
 Sep 07 07:59:18.000 [info] router_pick_published_address(): Success: chose
 address '109.103.57.102'.
 Sep 07 07:59:18.000 [info] channel_tls_process_certs_cell(): Got some good
 certificates from [scrubbed]:50560: Waiting for AUTHENTICATE.
 Sep 07 07:59:18.000 [info] channel_tls_process_authenticate_cell(): Got an
 AUTHENTICATE cell from [scrubbed]:9001: Looks good.
 Sep 07 07:59:18.000 [info] channel_tls_process_netinfo_cell(): Got good
 NETINFO cell from [scrubbed]:9001; OR connection is now open, using
 protocol version 4. Its ID digest is
 4FBE3430F3A583463BA4E961B8AADF0CD3C71D24. Our address is apparently
 109.103.57.102.

 Sep 07 07:59:18.000 [warn] Failure from drain_fd

 Sep 07 07:59:18.000 [notice] Self-testing indicates your ORPort is
 reachable from the outside. Excellent.
 Sep 07 07:59:22.000 [notice] Performing bandwidth self-test...done.

 Sep 07 08:30:51.000 [notice] New control connection opened from 127.0.0.1.
 Sep 07 08:30:52.000 [info] handle_control_authenticate(): Authenticated
 controlconnection (1392)
 Sep 07 08:30:52.000 [notice] Heartbeat: It seems like we are not in the
 cached consensus.
 Sep 07 08:30:52.000 [notice] Heartbeat: Tor's uptime is 0:31 hours, with 6
 circuits open. I've sent 951 kB and received 4.34 MB.
 Sep 07 08:30:52.000 [info] log_heartbeat(): Average packaged cell
 fullness: 96.311%. TLS write overhead: 3%
 Sep 07 08:30:52.000 [notice] Circuit handshake stats since last time: 0/0
 TAP, 0/0 NTor.
 Sep 07 08:30:52.000 [notice] Since startup, we have initiated 0 v1
 connections,0 v2 connections, 0 v3 connections, and 28 v4 connections; and
 received 0 v1 connections, 0 v2 connections, 0 v3 connections, and 4 v4
 connections.
 }}}
 This is my torrc:

 {{{
 Address 109.103.57.102
 AvoidDiskWrites 1
 Nickname TORques
 ContactInfo <torques at gooqle.com>

 ORPort 9001
 DirPort 9030
 SocksPort 9050
 ControlPort 9151

 DNSPort 53
 AutomapHostsOnResolve 1
 AutomapHostsSuffixes .onion,.com,.net,.exit

 DataDirectory "path"
 GeoIPFile "path"
 GeoIPv6File "path"
 Log info stdout
 Log notice file "path"

 ## tor --hash-password ***********************
 HashedControlPassword 16:***********************

 NumEntryGuards 8
 RelayBandwidthRate 5 MB
 RelayBandwidthBurst 7 MB
 BandwidthRate 10 MB
 BandwidthBurst 20 MB
 NumCPUs 2

 NewCircuitPeriod 1
 CircuitIdleTimeout 2700
 LearnCircuitBuildTimeout 1
 MaxCircuitDirtiness 600
 KeepalivePeriod 600

 ExitRelay 0
 ExitPolicy reject *:*

 FetchUselessDescriptors 1
 ProtocolWarnings 1
 HeartbeatPeriod 1800
 ShutdownWaitLength 60

 PublishServerDescriptor 0
 DirReqStatistics 0
 EntryStatistics 0
 CellStatistics 0
 ExitPortStatistics 0
 ExtraInfoStatistics 0
 }}}

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


More information about the tor-bugs mailing list