Skip to content
Snippets Groups Projects

Problem bootstrapping. Stuck at 45%: (Connection refused; CONNECTREFUSED)

    • Closed (moved) Issue created by Trac @tracbot

    Sebastian on IRC told me to open a bug report here.

    I've been having trouble with my Tor node, getting the above warning message. Even after cleaning cache/state information, Tor still cannot collect enough descriptor information.

    notice.log: http://pastebin.com/RuMMaCgJ Debian Lenny with Etch Xen Kernel (2.6.18-6-xen-686)

    "openssl s_client -connect 128.31.0.39:9101" works.

    You can find me on IRC (nickname "narr").

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

    Trac:
    Username: narr

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • Trac changed milestone to %Tor: unspecified

      changed milestone to %Tor: unspecified

    • Trac added component::core tor/tor milestone::Tor: unspecified priority::low reporter::narr resolution::wontfix severity::normal status::closed type::defect version::0.2.2.10-alpha labels

      added component::core tor/tor milestone::Tor: unspecified priority::low reporter::narr resolution::wontfix severity::normal status::closed type::defect version::0.2.2.10-alpha labels

    • S
      Sebastian Hahn @sebastian ·

      I'm especially puzzled because we're successfully testing reachability, before we have any descriptors.

    • Trac
      Trac @tracbot ·
      Author

      We've tried disabling server capabilities and enabling client functionality and letting Tor connect to the network through bridges, which worked fine. After that, even after reenabling server functionality (and clearing cache again), it suddenly was able to connect just fine. I am not aware of any differences in the config, but it looks as if it works...

      Judging from the first log that showed connectivity problems, it happened after a few hours of being connected to the network. I'm not sure if this report can be closed now.

      Trac:
      Username: narr

    • Roger Dingledine
      Roger Dingledine @arma ·

      Capturing the pastebin for posterity:

      Mar 16 15:23:52.950 [notice] Tor 0.2.2.10-alpha (git-e43253ba9e9430ea) opening log file. Mar 16 15:23:53.006 [notice] Parsing GEOIP file. Mar 16 15:23:53.704 [notice] OpenSSL OpenSSL 0.9.8g 19 Oct 2007 [90807f] looks like it's older than 0.9.8l, but some vendors have backported 0.9.8l's renegotiation code to earlier versions. I'll set SSL3_FLAGS just to be safe. Mar 16 15:23:53.753 [notice] Your Tor server's identity key fingerprint is 'xxxx XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' Mar 16 15:23:53.754 [notice] No current certificate known for authority moria1; launching request. Mar 16 15:23:53.754 [notice] No current certificate known for authority tor26; launching request. Mar 16 15:23:53.754 [notice] No current certificate known for authority dizum; launching request. Mar 16 15:23:53.754 [notice] No current certificate known for authority ides; launching request. Mar 16 15:23:53.754 [notice] No current certificate known for authority gabelmoo; launching request. Mar 16 15:23:53.754 [notice] No current certificate known for authority dannenberg; launching request. Mar 16 15:23:53.754 [notice] No current certificate known for authority urras; launching request. Mar 16 15:23:54.921 [warn] 0 unknown, 6 missing key, 0 good, 0 bad, 1 no signature, 4 required Mar 16 15:23:54.923 [notice] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus. Mar 16 15:23:56.753 [notice] We're missing a certificate from authority with signing key 36892827926E3BB068E8F9EDFA463C179162952F: launching request. Mar 16 15:23:56.753 [notice] We're missing a certificate from authority with signing key 805619341C7E0817219DF44E8C479988A15B9454: launching request. Mar 16 15:23:56.753 [notice] We're missing a certificate from authority with signing key B7A209B31ACDD633258D0F07715482BD04F88F4F: launching request. Mar 16 15:23:56.753 [notice] We're missing a certificate from authority with signing key 665711AF821C459DC59A8491FAD1B9D7A7800ECF: launching request. Mar 16 15:23:56.753 [notice] We're missing a certificate from authority with signing key 08D85E2B51D1962DF9EAB4DAF1F1A0061FF0E954: launching request. Mar 16 15:23:56.753 [notice] We're missing a certificate from authority with signing key 6584DF098CFC68ACBF5E551532C8A58674586820: launching request. Mar 16 15:23:56.753 [notice] No current certificate known for authority dannenberg; launching request. Mar 16 15:24:01.733 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Mar 16 15:24:09.593 [notice] Bootstrapped 10%: Finishing handshake with directory server. Mar 16 15:23:56.753 [notice] No current certificate known for authority dannenberg; launching request. Mar 16 15:24:01.733 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Mar 16 15:24:09.593 [notice] Bootstrapped 10%: Finishing handshake with directory server. Mar 16 15:25:42.158 [notice] Your DNS provider gave an answer for "vuav7bd5", which is not supposed to exist. Apparently they are hijacking DNS failures. Trying to correct for this. We've noticed 1 possibly bad address so far. Mar 16 15:25:47.220 [notice] Your DNS provider has given "67.215.65.132" as an answer for 11 different invalid addresses. Apparently they are hijacking DNS failures. I'll try to correct for this by treating future occurrences of "67.215.65.132" as 'not found'. Mar 16 15:25:55.202 [notice] We're missing a certificate from authority with signing key 36892827926E3BB068E8F9EDFA463C179162952F: launching request. Mar 16 15:25:55.202 [notice] We're missing a certificate from authority with signing key 805619341C7E0817219DF44E8C479988A15B9454: launching request. Mar 16 15:25:55.202 [notice] We're missing a certificate from authority with signing key B7A209B31ACDD633258D0F07715482BD04F88F4F: launching request. Mar 16 15:25:55.202 [notice] We're missing a certificate from authority with signing key 665711AF821C459DC59A8491FAD1B9D7A7800ECF: launching request. Mar 16 15:25:55.202 [notice] We're missing a certificate from authority with signing key 08D85E2B51D1962DF9EAB4DAF1F1A0061FF0E954: launching request. Mar 16 15:25:55.202 [notice] We're missing a certificate from authority with signing key 6584DF098CFC68ACBF5E551532C8A58674586820: launching request. Mar 16 15:25:55.202 [notice] No current certificate known for authority dannenberg; launching request. Mar 16 15:25:55.653 [notice] Bootstrapped 45%: Asking for relay descriptors. Mar 16 15:25:55.653 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1647 usable descriptors. Mar 16 15:27:59.974 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 10; recommendation warn) Mar 16 15:33:07.207 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 11; recommendation warn) Mar 16 15:33:11.567 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 12; recommendation warn) Mar 16 15:38:48.021 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 13; recommendation warn) Mar 16 15:38:48.421 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 14; recommendation warn) Mar 16 15:38:50.549 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 15; recommendation warn) Mar 16 15:38:53.561 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 16; recommendation warn) Mar 16 15:38:58.380 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 17; recommendation warn) Mar 16 15:39:02.500 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 18; recommendation warn) Mar 16 15:39:08.840 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 19; recommendation warn) Mar 16 15:39:10.217 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 20; recommendation warn) Mar 16 15:39:16.340 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 21; recommendation warn) Mar 16 15:39:21.508 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 22; recommendation warn) Mar 16 15:39:25.793 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 23; recommendation warn) Mar 16 15:39:31.335 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 24; recommendation warn) Mar 16 15:39:43.067 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 25; recommendation warn) Mar 16 15:39:55.615 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 26; recommendation warn) Mar 16 15:40:03.470 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (Connection refused; CONNECTREFUSED; count 27; recommendation warn) Mar 16 15:44:12.266 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (DONE; DONE; count 28; recommendation warn)

    • Roger Dingledine
      Roger Dingledine @arma ·

      Sebastian said: "I'm especially puzzled because we're successfully testing reachability, before we have any descriptors."

      router_orport_found_reachable() is called from onionskin_answer() when we let somebody extend their circuit to us.

      So if this Tor had been a published relay recently, and then restarted, some other client might have already had him in their list, and tried to use him, at which point we concluded we were reachable. That's separate from learning whether client functionality works.

      But note that we wait until client functionality works, and we're reachable, to do the bandwidth tests.

    • Roger Dingledine
      Roger Dingledine @arma ·

      It almost looks like your network is intercepting outgoing http requests, and then failing them.

      Since you're a relay, you're making plaintext http requests to the directory authorities (whereas when you're a client you're making TLS connections and tunneling the directory requests inside the TLS connection).

    • Trac
      Trac @tracbot ·
      Author

      Because I was also having memory problems with my node I compiled Tor with OpenSSH 1.0.0-beta5 and OpenBSD-malloc (see bugreport 1315). I still have trouble getting my node up, it always 'loses' its descriptor information. Excerpts from notice.log:

      04:29:20.706 [notice] I learned some more directory information, but not enough to build a circuit: We have only 341/1534 usable descriptors. (...) 14:06:56.918 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1614 usable descriptors.

      I've enabled info logging, and it shows a lot of connection_dir_request_failed(). I have trouble finding the relevant lines. Also a lot of

      TLS error while handshaking with [scrubbed]: unknown protocol (in SSL routines:SSL23_GET_CLIENT_HELLO:SSL23_ST_SR_CLNT_HELLO_A) TLS error: (errno=104: Connection reset by peer; state=SSL3_ST_SR_CERT_A)

      Full notice.log: http://pastebin.com/5Jhtjzq6 Longer excerpt from info.log: http://pastebin.com/UCkXFFBV

      Trac:
      Username: narr

    • Trac
      Trac @tracbot ·
      Author

      Update: No changes. Latest log:

      Mar 18 16:26:35.737 [notice] Tor 0.2.2.10-alpha (git-e43253ba9e9430ea) opening log file. Mar 18 16:28:12.570 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1650 usable descriptors. Mar 18 17:17:05.170 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1669 usable descriptors. Mar 18 18:26:11.867 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1678 usable descriptors. Mar 18 19:16:59.512 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1716 usable descriptors. Mar 18 20:24:10.375 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1751 usable descriptors. Mar 18 21:26:12.636 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1734 usable descriptors. Mar 18 22:11:51.371 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1748 usable descriptors. Mar 18 23:18:59.561 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1718 usable descriptors. Mar 19 00:23:02.452 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1659 usable descriptors. Mar 19 01:05:48.564 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1613 usable descriptors. Mar 19 02:17:55.539 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1589 usable descriptors. Mar 19 03:29:07.997 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1559 usable descriptors. Mar 19 04:24:02.198 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1543 usable descriptors. Mar 19 05:00:04.471 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1545 usable descriptors. Mar 19 05:00:05.031 [notice] I learned some more directory information, but not enough to build a circuit: We have only 48/1545 usable descriptors. Mar 19 05:00:05.300 [notice] I learned some more directory information, but not enough to build a circuit: We have only 95/1545 usable descriptors. Mar 19 05:00:05.409 [notice] I learned some more directory information, but not enough to build a circuit: We have only 152/1545 usable descriptors. Mar 19 05:00:05.514 [notice] I learned some more directory information, but not enough to build a circuit: We have only 207/1545 usable descriptors. Mar 19 05:00:05.582 [notice] I learned some more directory information, but not enough to build a circuit: We have only 266/1545 usable descriptors. Mar 19 05:00:05.706 [notice] I learned some more directory information, but not enough to build a circuit: We have only 320/1545 usable descriptors. Mar 19 05:00:05.950 [notice] I learned some more directory information, but not enough to build a circuit: We have only 372/1545 usable descriptors. Mar 19 05:00:06.039 [notice] We now have enough directory information to build circuits.

      Especially the last line puzzles me (after that no new entries since) - the node still generates no traffic and info logs look similar to the one posted above - connection_dir_request_failed(), and "TLS error while handshaking with [scrubbed]: unknown protocol (in SSL routines:SSL23_GET_CLIENT_HELLO:SSL23_ST_SR_CLNT_HELLO_A)".

      Mar 19 11:33:37.244 [info] connection_close_immediate(): fd 18, type Directory, state connecting, 420 bytes on outbuf. Mar 19 11:33:37.244 [info] connection_dir_request_failed(): Giving up on directory server at '86.59.21.38'; retrying Mar 19 11:33:37.244 [info] connection_close_immediate(): fd 10, type Directory, state connecting, 178 bytes on outbuf. Mar 19 11:33:37.244 [info] connection_dir_request_failed(): Giving up on directory server at '194.109.206.212'; retrying Mar 19 11:33:39.020 [info] connection_close_immediate(): fd 4, type Directory, state connecting, 57 bytes on outbuf. Mar 19 11:33:39.020 [info] connection_dir_request_failed(): Giving up on directory server at '194.109.206.212'; retrying Mar 19 11:33:42.020 [info] connection_close_immediate(): fd 4, type Directory, state connecting, 57 bytes on outbuf. Mar 19 11:33:42.020 [info] connection_dir_request_failed(): Giving up on directory server at '194.109.206.212'; retrying Mar 19 11:33:45.020 [info] connection_close_immediate(): fd 4, type Directory, state connecting, 57 bytes on outbuf. Mar 19 11:33:45.020 [info] connection_dir_request_failed(): Giving up on directory server at '194.109.206.212'; retrying Mar 19 11:33:48.020 [info] connection_close_immediate(): fd 4, type Directory, state connecting, 57 bytes on outbuf. Mar 19 11:33:48.020 [info] connection_dir_request_failed(): Giving up on directory server at '194.109.206.212'; retrying Mar 19 11:33:51.020 [info] connection_close_immediate(): fd 4, type Directory, state connecting, 57 bytes on outbuf. Mar 19 11:33:51.020 [info] connection_dir_request_failed(): Giving up on directory server at '194.109.206.212'; retrying Mar 19 11:33:52.712 [info] TLS error while handshaking with [scrubbed]: unknown protocol (in SSL routines:SSL23_GET_CLIENT_HELLO:SSL23_ST_SR_CLNT_HELLO_A) Mar 19 11:33:52.712 [info] connection_tls_continue_handshake(): tls error [misc error]. breaking connection. Mar 19 11:33:54.020 [info] connection_close_immediate(): fd 4, type Directory, state connecting, 57 bytes on outbuf.

      Trac:
      Username: narr

    • Trac
      Trac @tracbot ·
      Author

      The node was temporarily back up, without any changes in the configuration or restarts. Now, it "lost" all descriptors again.

      Trac:
      Username: narr

    • Trac
      Trac @tracbot ·
      Author

      no changes. when i restart tor, it looks like it's working, but after a few hours (without appearing on the nodelist) it again "loses" the descriptors. i have no idea what to do next; i can use other services without problem: i've tried http/torrent/i2p and others. my ISP says it isn't filtering anything.

      Trac:
      Username: narr

    • A
      Andrew Lewman @andrew ·

      Is this still true for 0.2.2.13-alpha?

      Trac:
      Keywords: N/A deleted, N/A added
      Description: Sebastian on IRC told me to open a bug report here.

      I've been having trouble with my Tor node, getting the above warning message. Even after cleaning cache/state information, Tor still cannot collect enough descriptor information.

      notice.log: http://pastebin.com/RuMMaCgJ Debian Lenny with Etch Xen Kernel (2.6.18-6-xen-686)

      "openssl s_client -connect 128.31.0.39:9101" works.

      You can find me on IRC (nickname "narr").

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

      to

      Sebastian on IRC told me to open a bug report here.

      I've been having trouble with my Tor node, getting the above warning message. Even after cleaning cache/state information, Tor still cannot collect enough descriptor information.

      notice.log: http://pastebin.com/RuMMaCgJ Debian Lenny with Etch Xen Kernel (2.6.18-6-xen-686)

      "openssl s_client -connect 128.31.0.39:9101" works.

      You can find me on IRC (nickname "narr").

      [Automatically added by flyspray2trac: Operating System: Other Linux]
      Milestone: N/A to Tor: 0.2.2.x-final

    • Roger Dingledine
      Roger Dingledine @arma ·

      My first thought is that your openssl has renegotiation disabled. More recent Tors try to workaround that bug in some openssl packages. It would be good to try a more recent Tor, and let us know if the problems are still persisting. You added several variables at once, and are experiencing 1 or 2 bugs, I'm not sure which, at least one of which is known.

      Trac:
      Parent: N/A to N/A
      Milestone: Tor: 0.2.2.x-final to Tor: post 0.2.2.x

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Hello? Any word on whether this works with newer Tors? We tried a lot to fix the openssl issues in the versions you were using, and it would be good to know whether it worked out or not.

      (Moving to "unspecified" milestone.)

      Trac:
      Milestone: Tor: post 0.2.2.x to Tor: unspecified

    • S
      Sebastian Hahn @sebastian ·

      Closing this as user disappeared. There's no sense in keeping dead tickets open. If someone has more info, please reopen or make a new ticket.

      Trac:
      Status: new to closed
      Points: N/A to N/A
      Resolution: None to user disappeared
      Actualpoints: N/A to N/A

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Trac:
      Component: Tor Relay to Tor

    • Trac
      Trac @tracbot ·
      Author

      Hello, I was running both tor 0.2.2.39-1 and 0.2.3.22-rc-1 on my dir-825 with OpenWRT firmware (ATTITUDE ADJUSTMENT (12.09, r36088)) and both versions were stuck at 45% with the following in the notices.log:

      Aug 27 02:07:01.000 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (IOERROR; IOERROR; count 432; recommendation warn)
Aug 27 02:07:02.000 [warn] 435 connections have failed:
Aug 27 02:07:02.000 [warn]  285 connections died in state connect()ing with SSL state (No SSL object)
Aug 27 02:07:02.000 [warn]  98 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN
Aug 27 02:07:02.000 [warn]  46 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
Aug 27 02:07:02.000 [warn]  6 connections died in state handshaking (TLS) with SSL state SSLv3 read finished A in HANDSHAKE
Aug 27 02:07:07.000 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as directory (unweighted was 352009000.000000)  [31 similar message(s) suppressed in last 15 seconds]
Aug 27 02:07:38.000 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as directory (unweighted was 87767000.000000)  [35 similar message(s) suppressed in last 15 seconds]
Aug 27 02:08:09.000 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as directory (unweighted was 62269000.000000)  [42 similar message(s) suppressed in last 15 seconds]
Aug 27 02:08:36.000 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as directory (unweighted was 3127000.000000)  [44 similar message(s) suppressed in last 15 seconds]
Aug 27 02:10:42.000 [warn] Problem bootstrapping. Stuck at 45%: Asking for relay descriptors. (DONE; DONE; count 433; recommendation warn)

      and in the debug.log:

      Aug 27 17:58:56.000 [debug] directory_initiate_command_rend(): anonymized 0, use_begindir 1.
Aug 27 17:58:56.000 [debug] directory_initiate_command_rend(): Initiating microdescriptor fetch
Aug 27 17:58:56.000 [info] connection_ap_make_link(): Making internal direct tunnel to [scrubbed]:9101 ...
Aug 27 17:58:56.000 [debug] connection_add_impl(): new conn type Socks, socket -1, address (Tor_internal), n_conns 22.
Aug 27 17:58:56.000 [debug] circuit_get_open_circ_or_launch(): one on the way!
Aug 27 17:58:56.000 [info] connection_ap_make_link(): ... application connection created and linked.
Aug 27 17:58:56.000 [debug] connection_add_impl(): new conn type Directory, socket -1, address 128.31.0.34, n_conns 23.
Aug 27 17:58:56.000 [debug] directory_initiate_command_rend(): anonymized 0, use_begindir 1.
Aug 27 17:58:56.000 [debug] directory_initiate_command_rend(): Initiating microdescriptor fetch
Aug 27 17:58:56.000 [info] connection_ap_make_link(): Making internal direct tunnel to [scrubbed]:80 ...
Aug 27 17:58:56.000 [debug] connection_add_impl(): new conn type Socks, socket -1, address (Tor_internal), n_conns 24.
Aug 27 17:58:56.000 [debug] circuit_get_open_circ_or_launch(): one on the way!
Aug 27 17:58:56.000 [info] connection_ap_make_link(): ... application connection created and linked.
Aug 27 17:58:56.000 [debug] connection_add_impl(): new conn type Directory, socket -1, address 208.83.223.34, n_conns 25.
Aug 27 17:58:56.000 [debug] directory_initiate_command_rend(): anonymized 0, use_begindir 1.
Aug 27 17:58:57.000 [debug] directory_initiate_command_rend(): Initiating microdescriptor fetch
Aug 27 17:58:57.000 [info] connection_ap_make_link(): Making internal direct tunnel to [scrubbed]:9101 ...
Aug 27 17:58:57.000 [debug] connection_add_impl(): new conn type Socks, socket -1, address (Tor_internal), n_conns 26.
Aug 27 17:58:57.000 [debug] circuit_get_open_circ_or_launch(): one on the way!
Aug 27 17:58:57.000 [info] connection_ap_make_link(): ... application connection created and linked.
Aug 27 17:58:57.000 [debug] connection_add_impl(): new conn type Directory, socket -1, address 128.31.0.34, n_conns 27.
Aug 27 17:58:57.000 [debug] directory_initiate_command_rend(): anonymized 0, use_begindir 1.
Aug 27 17:58:57.000 [debug] directory_initiate_command_rend(): Initiating microdescriptor fetch
Aug 27 17:58:57.000 [info] connection_ap_make_link(): Making internal direct tunnel to [scrubbed]:443 ...
Aug 27 17:58:57.000 [debug] connection_add_impl(): new conn type Socks, socket -1, address (Tor_internal), n_conns 28.
Aug 27 17:58:57.000 [debug] circuit_get_open_circ_or_launch(): one on the way!
Aug 27 17:58:57.000 [info] connection_ap_make_link(): ... application connection created and linked.
Aug 27 17:58:57.000 [debug] connection_add_impl(): new conn type Directory, socket -1, address 194.109.206.212, n_conns 29.
Aug 27 17:58:57.000 [debug] directory_initiate_command_rend(): anonymized 0, use_begindir 1.
Aug 27 17:58:57.000 [debug] directory_initiate_command_rend(): Initiating microdescriptor fetch
Aug 27 17:58:57.000 [info] connection_ap_make_link(): Making internal direct tunnel to [scrubbed]:443 ...
Aug 27 17:58:57.000 [debug] connection_add_impl(): new conn type Socks, socket -1, address (Tor_internal), n_conns 30.
Aug 27 17:58:57.000 [debug] circuit_get_open_circ_or_launch(): considering 1, $7BE683E65D48141321C5ED92F075C55364AC7123
Aug 27 17:58:57.000 [debug] onion_pick_cpath_exit(): Launching a one-hop circuit for dir tunnel.
Aug 27 17:58:57.000 [info] onion_pick_cpath_exit(): Using requested exit node '$7BE683E65D48141321C5ED92F075C55364AC7123~7BE683E65D48141321C at 193.23.244.244'
Aug 27 17:58:57.000 [debug] onion_extend_cpath(): Path is 0 long; we want 1
Aug 27 17:58:57.000 [debug] onion_extend_cpath(): Chose router $7BE683E65D48141321C5ED92F075C55364AC7123~7BE683E65D48141321C at 193.23.244.244 for hop 1 (exit is 7BE683E65D48141321C5ED92F075C55364AC7123)
Aug 27 17:58:57.000 [debug] onion_extend_cpath(): Path is complete: 1 steps long
Aug 27 17:58:57.000 [debug] circuit_handle_first_hop(): Looking for firsthop '193.23.244.244:443'
Aug 27 17:58:57.000 [debug] circuit_handle_first_hop(): Conn open. Delivering first onion skin.
Aug 27 17:58:57.000 [debug] circuit_send_next_onion_skin(): First skin; sending create cell.
Aug 27 17:58:57.000 [debug] circuit_deliver_create_cell(): Chosen circID 38144.
Aug 27 17:58:57.000 [debug] append_cell_to_circuit_queue(): Made a circuit active.
Aug 27 17:58:57.000 [info] circuit_send_next_onion_skin(): First hop: finished sending CREATE_FAST cell to '$7BE683E65D48141321C5ED92F075C55364AC7123=dannenberg at 193.23.244.244'
Aug 27 17:58:57.000 [info] connection_ap_make_link(): ... application connection created and linked.
Aug 27 17:58:57.000 [debug] connection_add_impl(): new conn type Directory, socket -1, address 193.23.244.244, n_conns 31.

      The debug.log grows in about 300mb per day with simmilar, but not completely the same messages.

      P.S.

      Package: libc       Version: 0.9.33.2-1
Package: libevent2  Version: 2.0.19-1
Package: libopenssl Version: 1.0.1e-1
Package: libpthread Version: 0.9.33.2-1
Package: librt      Version: 0.9.33.2-1

      Trac:
      Username: Grief
      Status: closed to reopened
      Cc: narr,Sebastian,nickm,arma to narr, Sebastian, nickm, arma
      Resolution: user disappeared to N/A

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Does this still happen with a supported version of Tor?

    • Trac
      Trac @tracbot ·
      Author

      Replying to nickm:

      Does this still happen with a supported version of Tor? This is the latest version available for openwrt. looks like that i must raise a bug on their bugtracker, don't I?

      Trac:
      Username: Grief

    • Nick Mathewson
      Nick Mathewson @nickm ·

      Closed because no current version of Tor affected; this wasn't on a supported version when last reported.

      Trac:
      Reviewer: N/A to N/A
      Sponsor: N/A to N/A
      Status: reopened to closed
      Severity: N/A to Normal
      Resolution: N/A to wontfix

    • Trac closed

      closed

    • Trac moved to tpo/core/tor#1314 (closed)

      moved to tpo/core/tor#1314 (closed)

    Please register or sign in to reply