[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #11562 [meek]: meek browser stops working after many idle hours

Subject: Re: [tor-bugs] #11562 [meek]: meek browser stops working after many idle hours
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Sat, 19 Apr 2014 02:12:27 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Fri, 18 Apr 2014 22:12:38 -0400
In-reply-to: <043.877a9250924dd8de2d739e2013c55c4e@xxxxxxxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-bugs/>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: 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>
References: <043.877a9250924dd8de2d739e2013c55c4e@xxxxxxxxxxxxxx>
Reply-to: tor-assistants@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>
#11562: meek browser stops working after many idle hours
------------------------+-----------------
     Reporter:  dcf     |      Owner:  dcf
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:
    Component:  meek    |    Version:
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-----------------

Comment (by dcf):

 Log files. meek-client, meek-client-torbrowser, and the headless firefox
 were all still running. The browser extension helper port was open.
 Important lines seem to be:
 {{{
 04/16/2014 00:05:30.355 [NOTICE] Your system clock just jumped 871 seconds
 forward; assuming established circuits no longer work.
 04/16/2014 00:05:30.665 [NOTICE] Ignoring directory request, since no
 bridge nodes are available yet.
 04/16/2014 00:05:31.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 00:29:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 }}}
 It was running in a VM and it's possible the clock jumped.

 meek-client-torbrowser.log
 {{{
 2014/04/15 16:29:15 running firefox command ["Browser/firefox" "-no-
 remote" "-profile" "/home/user/tor-browser_en-US/Data/Browser/profile
 .meek-http-helper"]
 2014/04/15 16:29:15 firefox started with pid 3337
 2014/04/15 16:29:16 running meek-client command
 ["./Tor/PluggableTransports/meek-client" "--url=https://meek-
 reflect.appspot.com/" "--front=www.google.com" "--log" "meek-client.log" "
 --helper" "127.0.0.1:33731"]
 2014/04/15 16:29:16 meek-client started with pid 3349
 }}}

 meek-client.log
 {{{
 2014/04/14 12:26:40 error in handling request: EOF
 2014/04/14 12:41:40 error in handling request: EOF
 2014/04/14 13:00:21 error in handling request: EOF
 2014/04/15 16:29:16 using helper on 127.0.0.1:33731
 2014/04/15 16:29:16 listening on 127.0.0.1:40774
 2014/04/15 16:39:29 error in AcceptSocks: read tcp 127.0.0.1:34813:
 connection reset by peer
 2014/04/15 17:05:30 error in handling request: status code was 500, not
 200
 }}}

 tor log
 {{{
 04/15/2014 23:29:17.922 [NOTICE] Bootstrapped 5%: Connecting to directory
 server.
 04/15/2014 23:29:17.923 [NOTICE] Bootstrapped 10%: Finishing handshake
 with directory server.
 04/15/2014 23:29:18.509 [NOTICE] Learned fingerprint
 86FA348B038B6A04F2F50135BF84BB74EF63485B for bridge 0.0.2.0:1 (with
 transport 'meek').
 04/15/2014 23:29:18.509 [NOTICE] Bootstrapped 15%: Establishing an
 encrypted directory connection.
 04/15/2014 23:29:18.870 [NOTICE] Bootstrapped 20%: Asking for
 networkstatus consensus.
 04/15/2014 23:29:19.460 [NOTICE] Bootstrapped 50%: Loading relay
 descriptors.
 04/15/2014 23:29:19.216 [NOTICE] Bridge '3VXRyxz67OeRoqHn' has both an
 IPv4 and an IPv6 address.  Will prefer using its IPv4 address (0.0.2.0:1).
 04/15/2014 23:29:19.216 [NOTICE] new bridge descriptor '3VXRyxz67OeRoqHn'
 (fresh): $86FA348B038B6A04F2F50135BF84BB74EF63485B~3VXRyxz67OeRoqHn at
 0.0.2.0
 04/15/2014 23:29:19.216 [NOTICE] I learned some more directory
 information, but not enough to build a circuit: We have no usable
 consensus.
 04/15/2014 23:29:22.563 [NOTICE] I learned some more directory
 information, but not enough to build a circuit: We need more
 microdescriptors: we have 4297/5496, and can only build 53% of likely
 paths. (We have 82% of guards bw, 81% of midpoint bw, and 79% of exit bw.)
 04/15/2014 23:29:23.140 [NOTICE] I learned some more directory
 information, but not enough to build a circuit: We need more
 microdescriptors: we have 4297/5496, and can only build 53% of likely
 paths. (We have 82% of guards bw, 81% of midpoint bw, and 79% of exit bw.)
 04/15/2014 23:29:23.796 [NOTICE] I learned some more directory
 information, but not enough to build a circuit: We need more
 microdescriptors: we have 4297/5496, and can only build 53% of likely
 paths. (We have 82% of guards bw, 81% of midpoint bw, and 79% of exit bw.)
 04/15/2014 23:29:24.926 [NOTICE] We now have enough directory information
 to build circuits.
 04/15/2014 23:29:24.926 [NOTICE] Bootstrapped 80%: Connecting to the Tor
 network.
 04/15/2014 23:29:24.927 [NOTICE] Bootstrapped 90%: Establishing a Tor
 circuit.
 04/15/2014 23:29:26.695 [NOTICE] Tor has successfully opened a circuit.
 Looks like client functionality is working.
 04/15/2014 23:29:26.695 [NOTICE] Bootstrapped 100%: Done.
 04/15/2014 23:29:27.503 [NOTICE] New control connection opened.
 04/15/2014 23:35:35.152 [WARN] Rejecting SOCKS request for anonymous
 connection to private address [scrubbed].
 04/15/2014 23:39:29.626 [NOTICE] New control connection opened.
 04/15/2014 23:39:38.434 [NOTICE] New control connection opened.
 04/15/2014 23:39:40.954 [WARN] Socks version 106 not recognized. (Tor is
 not an http proxy.)
 04/15/2014 23:39:40.955 [WARN] Fetching socks handshake failed. Closing.
 04/15/2014 23:39:43.568 [WARN] Socks version 72 not recognized. (Tor is
 not an http proxy.)
 04/15/2014 23:40:03.888 [NOTICE] New control connection opened.
 04/15/2014 23:41:08.921 [NOTICE] New control connection opened.
 04/15/2014 23:41:11.180 [WARN] Socks version 106 not recognized. (Tor is
 not an http proxy.)
 04/15/2014 23:41:11.180 [WARN] Fetching socks handshake failed. Closing.
 04/15/2014 23:41:12.758 [WARN] Socks version 72 not recognized. (Tor is
 not an http proxy.)
 04/16/2014 00:05:30.355 [NOTICE] Your system clock just jumped 871 seconds
 forward; assuming established circuits no longer work.
 04/16/2014 00:05:30.665 [NOTICE] Ignoring directory request, since no
 bridge nodes are available yet.
 04/16/2014 00:05:31.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 00:29:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 00:44:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 00:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 01:59:19.255 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 02:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 03:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 04:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 05:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 5:45 hours,
 with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/16/2014 05:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/16/2014 05:29:15.256 [NOTICE] TLS write overhead: 11%
 04/16/2014 05:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 06:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 07:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 08:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 09:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 10:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 11:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 11:45 hours,
 with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/16/2014 11:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/16/2014 11:29:15.256 [NOTICE] TLS write overhead: 11%
 04/16/2014 11:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 12:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 13:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 14:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 15:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 16:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 17:29:15.255 [NOTICE] Heartbeat: Tor's uptime is 17:45 hours,
 with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/16/2014 17:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/16/2014 17:29:15.256 [NOTICE] TLS write overhead: 11%
 04/16/2014 17:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 18:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 19:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 20:59:19.257 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 21:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 22:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 23:45 hours,
 with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/16/2014 23:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/16/2014 23:29:15.256 [NOTICE] TLS write overhead: 11%
 04/16/2014 23:35:27.190 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:35:27.260 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:35:27.270 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:35:27.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:35:52.270 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:35:52.268 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:35:52.268 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:35:53.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:36:17.330 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:36:17.265 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:36:17.266 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:36:18.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:36:42.410 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:36:42.265 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:36:42.266 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:36:43.255 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:37:07.490 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:37:07.266 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:37:07.266 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:37:08.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:37:27.120 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:37:27.200 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:37:27.200 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:37:27.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:37:32.580 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:37:32.269 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:37:32.269 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:37:33.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:37:52.680 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:37:52.271 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:37:52.272 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:37:53.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:37:57.680 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:37:57.266 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:37:57.266 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:37:58.255 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:38:17.760 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:38:17.266 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:38:17.267 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:38:18.255 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:38:22.770 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:38:22.270 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:38:22.271 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:38:23.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:38:42.830 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:38:42.267 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:38:42.267 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:38:43.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:38:47.840 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:38:47.260 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:38:48.258 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:38:49.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:39:07.910 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:39:07.265 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:39:07.265 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:39:08.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:39:12.940 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:39:12.267 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:39:12.267 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:39:13.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:39:32.101 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:39:32.268 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:39:32.268 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:39:33.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:39:37.127 [WARN] Rejecting SOCKS request for anonymous
 connection to private address [scrubbed]. [3 similar message(s) suppressed
 in last 300 seconds]
 04/16/2014 23:39:37.127 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:39:37.129 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:39:37.129 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:39:37.129 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:39:37.129 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:39:37.267 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:39:37.268 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:39:38.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:39:57.108 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:39:57.269 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:39:57.269 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:39:58.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:40:03.119 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:40:03.119 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:40:03.119 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:40:03.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:40:22.116 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:40:22.272 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:40:22.272 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:40:23.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:40:28.128 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:40:28.128 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:40:28.128 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:40:28.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:40:47.126 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:40:47.268 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:40:47.268 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:40:48.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:40:53.135 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:40:53.135 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:40:53.136 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:40:53.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:41:12.134 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:41:12.268 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:41:12.268 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:41:13.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:41:18.142 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/16/2014 23:41:18.142 [NOTICE] We now have enough directory information
 to build circuits.
 04/16/2014 23:41:18.143 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/16/2014 23:41:18.256 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We have no usable consensus.
 04/16/2014 23:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/17/2014 00:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/17/2014 01:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/17/2014 02:59:19.256 [WARN] The connection to the pluggable transports
 SOCKS proxy server at 127.0.0.1:40774 just failed. Make sure that the
 proxy server is up and running.
 04/17/2014 05:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 1 day 5:45
 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/17/2014 05:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/17/2014 05:29:15.256 [NOTICE] TLS write overhead: 11%
 04/17/2014 11:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 1 day 11:45
 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/17/2014 11:29:15.257 [NOTICE] Average packaged cell fullness: 64.821%
 04/17/2014 11:29:15.257 [NOTICE] TLS write overhead: 11%
 04/17/2014 17:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 1 day 17:45
 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/17/2014 17:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/17/2014 17:29:15.256 [NOTICE] TLS write overhead: 11%
 04/17/2014 23:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 1 day 23:45
 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/17/2014 23:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/17/2014 23:29:15.256 [NOTICE] TLS write overhead: 11%
 04/17/2014 23:37:27.660 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying known bridges again.
 04/17/2014 23:37:27.670 [NOTICE] Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 04/17/2014 23:39:27.256 [NOTICE] Ignoring directory request, since no
 bridge nodes are available yet.
 04/17/2014 23:39:37.177 [WARN] Rejecting SOCKS request for anonymous
 connection to private address [scrubbed]. [3 similar message(s) suppressed
 in last 300 seconds]
 04/18/2014 05:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 2 days 5:45
 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/18/2014 05:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/18/2014 05:29:15.256 [NOTICE] TLS write overhead: 11%
 04/18/2014 11:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 2 days 11:45
 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/18/2014 11:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/18/2014 11:29:15.256 [NOTICE] TLS write overhead: 11%
 04/18/2014 17:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 2 days 17:45
 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/18/2014 17:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/18/2014 17:29:15.256 [NOTICE] TLS write overhead: 11%
 04/18/2014 23:29:15.256 [NOTICE] Heartbeat: Tor's uptime is 2 days 23:45
 hours, with 0 circuits open. I've sent 0 kB and received 0 kB.
 04/18/2014 23:29:15.256 [NOTICE] Average packaged cell fullness: 64.821%
 04/18/2014 23:29:15.256 [NOTICE] TLS write overhead: 11%
 04/18/2014 23:39:37.226 [WARN] Rejecting SOCKS request for anonymous
 connection to private address [scrubbed]. [3 similar message(s) suppressed
 in last 300 seconds]
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11562#comment:1>
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
References:
- [tor-bugs] #11562 [meek]: meek browser stops working after many idle hours
  - From: Tor Bug Tracker & Wiki
Prev by Author: [tor-bugs] #11562 [meek]: meek browser stops working after many idle hours
Next by Author: Re: [tor-bugs] #9957 [Tor]: Tor should consider stderr output of transport proxies
Previous by thread: [tor-bugs] #11562 [meek]: meek browser stops working after many idle hours
Next by thread: Re: [tor-bugs] #11562 [meek]: meek browser stops working after many idle hours
Index(es):
- Author
- Thread