[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 09:51:56 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
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+--------------------------------

Comment (by TORques):

 Replying to [comment:7 yawning]:

 > Replying to [comment:6 TORques]:
 >
 >
 >
 > > However, this non-exit relay can easily reach **5 MB/sec or more** on
 my tweaked Windows XP platform. Not bad for the TOR network, isn't it? My
 Ookla test says 24 MB/s download and 10 MB/s upload and my CPU can process
 easily a TOR stream of 5 MB/s.
 > >
 > >
 > >
 >
 > Bulk single connection throughput is not why I brought that up. See #98
 among other issues. If your router/relay can't handle a large number of
 simultaneous connections, it'll end up underutilized and be bad for the
 network.  Past that if it works, great.  If it breaks, patches accepted.>

 Thanks for your replay. My router/relay can handle a large number of
 simultaneous connections (tcpsys changed to 256 connections). I just built
 the latest tor from your github and I see the modified message related to
 "Failure from drain_fd"

 {{{
 Sep 07 12:34:25.000 [notice] Tor 0.2.7.2-alpha-dev opening new log file.
 Sep 07 12:34:25.781 [notice] Tor v0.2.7.2-alpha-dev running on Windows XP
 with Libevent 2.0.22-stable, OpenSSL 1.0.2d and Zlib 1.2.8.
 Sep 07 12:34:27.000 [notice] This version of Tor (0.2.7.2-alpha-dev) is
 newer than any recommended version, according to the directory
 authorities. Recommended versions are:
 0.2.4.23,0.2.4.24,0.2.4.25,0.2.4.26,0.2.4.27,0.2.5.8-rc,0.2.5.9-rc,0.2.5.10,0.2.5.11,0.2.5.12,0.2.6.5-rc,0.2.6.6,0.2.6.7,0.2.6.8,0.2.6.9,0.2.6.10,0.2.7.1-alpha,0.2.7.2-alpha
 Sep 07 12:34:42.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 12:34:43.000 [notice] Self-testing indicates your DirPort is
 reachable from the outside. Excellent.

 Sep 07 12:34:43.000 [warn] Failure from drain_fd: No error

 Sep 07 12:34:43.000 [notice] Self-testing indicates your ORPort is
 reachable from the outside. Excellent. Publishing server descriptor.
 Sep 07 12:34:47.000 [notice] Performing bandwidth self-test...done.
 }}}
 Also, I used bench.exe to see the tor performances on my PC but I have no
 idea if those values are good or bad for a relay. Can you look into and
 write your opinion about?

 {{{
 Microsoft Windows XP [Version 5.1.2600]
 (C) Copyright 1985-2001 Microsoft Corp.

 C:\tor-0.2.7.2-alpha\src\test>bench.exe
 ===== dmap =====
 nbits=65536
 digestmap_set: 500.68 ns per element
 digestmap_get: 488.52 ns per element
 digestset_add: 422.00 ns per element
 digestset_contains: 416.99 ns per element.
 Hits == 32825344
 False positive rate on digestset: 0.22%
 ===== siphash =====
 siphash24g(7): 260.42 ns per call
 siphash24g(8): 312.50 ns per call
 siphash24g(15): 312.50 ns per call
 siphash24g(16): 416.67 ns per call
 siphash24g(20): 364.58 ns per call
 siphash24g(32): 520.83 ns per call
 siphash24g(111): 989.58 ns per call
 siphash24g(128): 1197.92 ns per call
 ===== aes =====
 1 bytes: 70.78 nsec per byte
 2 bytes: 47.50 nsec per byte
 4 bytes: 36.32 nsec per byte
 8 bytes: 29.80 nsec per byte
 16 bytes: 23.28 nsec per byte
 32 bytes: 21.42 nsec per byte
 64 bytes: 21.42 nsec per byte
 128 bytes: 21.42 nsec per byte
 256 bytes: 23.28 nsec per byte
 512 bytes: 21.42 nsec per byte
 1024 bytes: 19.56 nsec per byte
 2048 bytes: 20.49 nsec per byte
 4096 bytes: 20.49 nsec per byte
 8192 bytes: 20.49 nsec per byte
 ===== onion_TAP =====
 Client-side, part 1: 2349.853516 usec.
 Server-side, key guessed right: 6164.550781 usec
 Server-side, key guessed wrong: 7995.605469 usec.
 Client-side, part 2: 1953.125000 usec.
 ===== onion_ntor =====
 Ed25519-based basepoint multiply = disabled.
 Client-side, part 1: 1495.361328 usec.
 Server-side: 4531.860352 usec
 Client-side, part 2: 3021.240234 usec.
 Ed25519-based basepoint multiply = enabled.
 Client-side, part 1: 442.504883 usec.
 Server-side: 3494.262695 usec
 Client-side, part 2: 3005.981445 usec.
 ===== ed25519 =====
 Ed25519-donna = disabled.
 Generate public key: 476.84 usec
 Sign a short message: 484.47 usec
 Verify signature: 1602.17 usec
 Convert public point from curve25519: 95.37 usec
 Blind a public key: 1399.99 usec
 Ed25519-donna = enabled.
 Generate public key: 442.50 usec
 Sign a short message: 457.76 usec
 Verify signature: 1514.43 usec
 Convert public point from curve25519: 91.55 usec
 Blind a public key: 1373.29 usec
 ===== cell_aes =====
 509 bytes, misaligned by 0: 20.61 nsec per byte
 509 bytes, misaligned by 1: 20.14 nsec per byte
 509 bytes, misaligned by 2: 20.61 nsec per byte
 509 bytes, misaligned by 3: 20.14 nsec per byte
 509 bytes, misaligned by 4: 20.61 nsec per byte
 509 bytes, misaligned by 5: 20.14 nsec per byte
 509 bytes, misaligned by 6: 20.14 nsec per byte
 509 bytes, misaligned by 7: 20.61 nsec per byte
 509 bytes, misaligned by 8: 20.14 nsec per byte
 509 bytes, misaligned by 9: 20.61 nsec per byte
 509 bytes, misaligned by 10: 20.14 nsec per byte
 509 bytes, misaligned by 11: 20.14 nsec per byte
 509 bytes, misaligned by 12: 20.61 nsec per byte
 509 bytes, misaligned by 13: 20.14 nsec per byte
 509 bytes, misaligned by 14: 20.61 nsec per byte
 509 bytes, misaligned by 15: 20.14 nsec per byte
 ===== cell_ops =====
  Inbound cells: 10490.42 ns per cell. (20.61 ns per byte of payload)
 Outbound cells: 10490.42 ns per cell. (20.61 ns per byte of payload)
 ===== dh =====
 Complete DH handshakes (1024 bit, public and private ops):
       7.980347 millisec each.
 ===== ecdh_p256 =====
 Complete ECDH P-256 handshakes (2 public and 2 private ops):
       9.048462 millisec each.
 ===== ecdh_p224 =====
 Complete ECDH P-224 handshakes (2 public and 2 private ops):
       6.301880 millisec each.
 }}}

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


More information about the tor-bugs mailing list