Custom Query (26254 matches)


Show under each result:

Results (46 - 48 of 26254)

Ticket Resolution Summary Owner Reporter
#1882 fixed "Failed to find node for hop 0 of our path. Discarding this circuit." log spam after guard went down Sebastian

I noticed this issue with my torperf setup. A tor client that is started with a single node allowed as entry node will freak out if that entry guard goes offline, however briefly.

It keeps logging "Failed to find node for hop 0 of our path. Discarding this circuit." repeatedly, and doesn't seem to recover well at all. I wonder if that means that we are also willing to give up on guards in a regular setup as soon as they go down once, and stop using them.

This might be related to issue #675

#11855 worksforme "Failed to open reporter" might mean "the collector refused my report" hellais arma

In running OONI for a new test, running the new test will likely fail, perhaps because the collector doesn't allow reports for that test type.

You the user get a complaint of the form "Failed to open reporter", which doesn't at all help you understand what went wrong.

We should add whatever error checking and error passing mechanisms are needed to be able to tell the user a useful plan of action here.

#16992 duplicate "Failure from drain_fd: no error" in Tor v0.2.7.2-alpha-dev running on Windows XP TORques

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 ( ) at 2015-09-07 09:07 GTB Daylight Time
Initiating SYN Stealth Scan at 09:08
Scanning ( [65535 ports]
Discovered open port 53/tcp on
Discovered open port 80/tcp on
Discovered open port 9001/tcp on
Discovered open port 7547/tcp on (this port is reserved by router for updates, etc.)
Discovered open port 9030/tcp on
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 (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
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
Sep 07 07:59:00.750 [notice] Opening DNS listener on
Sep 07 07:59:00.750 [notice] Opening Control listener on
Sep 07 07:59:00.765 [notice] Opening OR listener on
Sep 07 07:59:00.796 [notice] Opening Directory listener on
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 and DirPort 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 ''.
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 ''.
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

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

AvoidDiskWrites 1
Nickname TORques
ContactInfo <>

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
Note: See TracQuery for help on using queries.