[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #31527 [Core Tor/Tor]: In Tor Browser nightly, Tor fails to boostrap, hangs at 50%

To: undisclosed-recipients: ;
Subject: Re: [tor-bugs] #31527 [Core Tor/Tor]: In Tor Browser nightly, Tor fails to boostrap, hangs at 50%
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Mon, 26 Aug 2019 22:34:43 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Mon, 26 Aug 2019 18:34:53 -0400
In-reply-to: <049.ba4a881a25c003ba58e9a388c428bf63@torproject.org>
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: <049.ba4a881a25c003ba58e9a388c428bf63@torproject.org>
Reply-to: no-reply@xxxxxxxxxxxxxx, tor-assistants@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>

#31527: In Tor Browser nightly, Tor fails to boostrap, hangs at 50%
--------------------------+--------------------------------
 Reporter:  pospeselr     |          Owner:  nickm
     Type:  defect        |         Status:  assigned
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  tbb-needs     |  Actual Points:
Parent ID:  #29211        |         Points:
 Reviewer:                |        Sponsor:  Sponsor31-must
--------------------------+--------------------------------

Comment (by sysrqb):

 It seems like this is the conversation between tor browser and tor:
 {{{
 $ ./tor-browser_en-US/Browser/start-tor-browser -v
 Gtk-Message: 18:28:44.476: Failed to load module "canberra-gtk-module"
 Gtk-Message: 18:28:44.477: Failed to load module "canberra-gtk-module"
 [08-26 22:28:44] Torbutton INFO: Torbutton debug output ready
 [08-26 22:28:44] Torbutton INFO: Component Load 5: New CookieJarSelector
 @torproject.org/cookie-jar-selector;1
 [08-26 22:28:44] Torbutton INFO: Cookie jar selector got profile-after-
 change
 [08-26 22:28:44] Torbutton INFO: domain isolator: set up isolating
 circuits by domain
 [08-26 22:28:44] Torbutton INFO: Component Load 0: New DragDropFilter.
 [08-26 22:28:44] Torbutton INFO: Startup Observer created
 [08-26 22:28:44] Torbutton INFO: This is a Tor Browser's XPCOM
 [08-26 22:28:44] TorLauncher INFO: debug output ready
 [08-26 22:28:44] TorLauncher INFO: SOCKS port type: TCP
 [08-26 22:28:44] TorLauncher INFO: SOCKS host: 127.0.0.1
 [08-26 22:28:44] TorLauncher INFO: SOCKS port: 9150
 [08-26 22:28:44] Torbutton INFO: Reset socks host to 127.0.0.1
 [08-26 22:28:44] Torbutton INFO: Reset socks port to 9150
 [08-26 22:28:44] Torbutton INFO: Synced network settings to environment.
 [08-26 22:28:44] Torbutton INFO: Listening for message from NoScript.
 [08-26 22:28:44] Torbutton INFO: Reset socks host to 127.0.0.1
 [08-26 22:28:44] Torbutton INFO: Reset socks port to 9150
 [08-26 22:28:44] Torbutton INFO: Synced network settings to environment.
 Fontconfig warning: "/home/user/tor-browser_en-
 US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 145: blank doesn't
 take any effect anymore. please remove it from your fonts.conf
 [08-26 22:28:44] TorLauncher DBUG: Starting /home/user/tor-browser_en-
 US/Browser/TorBrowser/Tor/tor
 [08-26 22:28:44] TorLauncher DBUG:   --defaults-torrc
 [08-26 22:28:44] TorLauncher DBUG:   /home/user/tor-browser_en-
 US/Browser/TorBrowser/Data/Tor/torrc-defaults
 [08-26 22:28:44] TorLauncher DBUG:   -f
 [08-26 22:28:44] TorLauncher DBUG:   /home/user/tor-browser_en-
 US/Browser/TorBrowser/Data/Tor/torrc
 [08-26 22:28:44] TorLauncher DBUG:   DataDirectory
 [08-26 22:28:44] TorLauncher DBUG:   /home/user/tor-browser_en-
 US/Browser/TorBrowser/Data/Tor
 [08-26 22:28:44] TorLauncher DBUG:   GeoIPFile
 [08-26 22:28:44] TorLauncher DBUG:   /home/user/tor-browser_en-
 US/Browser/TorBrowser/Data/Tor/geoip
 [08-26 22:28:44] TorLauncher DBUG:   GeoIPv6File
 [08-26 22:28:44] TorLauncher DBUG:   /home/user/tor-browser_en-
 US/Browser/TorBrowser/Data/Tor/geoip6
 [08-26 22:28:44] TorLauncher DBUG:   HashedControlPassword
 [08-26 22:28:44] TorLauncher DBUG:
 16:4b446c03a1b054976099156ab91beca2c4eab46a864f634587b61b89b4
 [08-26 22:28:44] TorLauncher DBUG:   +__ControlPort
 [08-26 22:28:44] TorLauncher DBUG:   9151
 [08-26 22:28:44] TorLauncher DBUG:   +__SocksPort
 [08-26 22:28:44] TorLauncher DBUG:   127.0.0.1:9150 IPv6Traffic PreferIPv6
 KeepAliveIsolateSOCKSAuth
 [08-26 22:28:44] TorLauncher DBUG:   __OwningControllerProcess
 [08-26 22:28:44] TorLauncher DBUG:   12907
 Aug 26 22:28:44.657 [notice] Tor 0.4.2.0-alpha-dev (git-6ba05eea8efcfc1f)
 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1c, Zlib 1.2.11,
 Liblzma N/A, and Libzstd N/A.
 Aug 26 22:28:44.657 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Aug 26 22:28:44.657 [notice] This version is not a stable Tor release.
 Expect more bugs than usual.
 Aug 26 22:28:44.657 [notice] Tor is running with Rust integration. Please
 report any bugs you encounter.
 Aug 26 22:28:44.657 [notice] Read configuration file "/home/user/tor-
 browser_en-US/Browser/TorBrowser/Data/Tor/torrc-defaults".
 Aug 26 22:28:44.658 [notice] Read configuration file "/home/user/tor-
 browser_en-US/Browser/TorBrowser/Data/Tor/torrc".
 Aug 26 22:28:44.658 [notice] Opening Socks listener on 127.0.0.1:9150
 Aug 26 22:28:44.658 [notice] Opened Socks listener on 127.0.0.1:9150
 Aug 26 22:28:44.659 [notice] Opening Control listener on 127.0.0.1:9151
 Aug 26 22:28:44.659 [notice] Opened Control listener on 127.0.0.1:9151
 Aug 26 22:28:44.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.
 Aug 26 22:28:44.000 [notice] Parsing GEOIP IPv4 file /home/user/tor-
 browser_en-US/Browser/TorBrowser/Data/Tor/geoip.
 [08-26 22:28:44] TorLauncher DBUG: Opening control connection to
 127.0.0.1:9151
 [08-26 22:28:44] TorLauncher DBUG: Sending Tor command: AUTHENTICATE
 416f714a60283371427c3c287b3c7a49
 Aug 26 22:28:44.000 [notice] Parsing GEOIP IPv6 file /home/user/tor-
 browser_en-US/Browser/TorBrowser/Data/Tor/geoip6.
 Aug 26 22:28:44.000 [notice] Bootstrapped 0% (starting): Starting
 Aug 26 22:28:44.000 [notice] Starting with guard context "default"
 Aug 26 22:28:44.000 [notice] New control connection opened from 127.0.0.1.
 [08-26 22:28:44] TorLauncher DBUG: Command response: 250 OK
 [08-26 22:28:44] TorLauncher DBUG: Sending Tor command: TAKEOWNERSHIP
 [08-26 22:28:44] TorLauncher DBUG: Command response: 250 OK
 [08-26 22:28:44] TorLauncher DBUG: Sending Tor command: RESETCONF
 __OwningControllerProcess
 Aug 26 22:28:44.000 [notice] All routers are down or won't exit or are
 Excluded -- choosing a doomed exit at random.
 Aug 26 22:28:44.000 [warn] No exits in ExitNodes, except possibly those
 excluded by your configuration,  seem to be running: can't choose an exit.
 Aug 26 22:28:44.000 [warn] Failed to choose an exit server
 Aug 26 22:28:44.000 [notice] Our circuit 0 (id: 1) died due to an invalid
 selected path, purpose General-purpose client. This may be a torrc
 configuration issue, or a bug.
 [08-26 22:28:44] TorLauncher DBUG: Command response: 250 OK
 [08-26 22:28:44] TorLauncher DBUG: Opening control connection to
 127.0.0.1:9151
 [08-26 22:28:44] TorLauncher DBUG: Sending Tor command: AUTHENTICATE
 416f714a60283371427c3c287b3c7a49
 Aug 26 22:28:45.000 [notice] New control connection opened from 127.0.0.1.
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 OK
 [08-26 22:28:45] TorLauncher DBUG: Sending Tor command: SETEVENTS
 STATUS_CLIENT NOTICE WARN ERR
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 OK
 [08-26 22:28:45] TorLauncher DBUG: Sending Tor command: GETINFO status
 /bootstrap-phase
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250-status/bootstrap-
 phase=NOTICE BOOTSTRAP PROGRESS=0 TAG=starting SUMMARY="Starting"
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 OK
 [08-26 22:28:45] TorLauncher DBUG: readTorSettings
 ----------------------------------------------
 [08-26 22:28:45] TorLauncher DBUG: Sending Tor command: GETCONF UseBridges
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 UseBridges=0
 [08-26 22:28:45] TorLauncher DBUG: Sending Tor command: GETCONF Bridge
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 Bridge
 [08-26 22:28:45] TorLauncher DBUG: Sending Tor command: GETCONF
 Socks4Proxy
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 Socks4Proxy
 [08-26 22:28:45] TorLauncher DBUG: Sending Tor command: GETCONF
 Socks5Proxy
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 Socks5Proxy
 [08-26 22:28:45] TorLauncher DBUG: Sending Tor command: GETCONF HTTPSProxy
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 HTTPSProxy
 [08-26 22:28:45] TorLauncher DBUG: readTorSettings done; didSucceed: true
 [08-26 22:28:45] TorLauncher DBUG: Sending Tor command: GETINFO status
 /bootstrap-phase
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250-status/bootstrap-
 phase=NOTICE BOOTSTRAP PROGRESS=0 TAG=starting SUMMARY="Starting"
 [08-26 22:28:45] TorLauncher DBUG: Command response: 250 OK
 [08-26 22:28:45] TorLauncher DBUG: initDialog done
 Aug 26 22:28:45.000 [warn] Could not find a node that matches the
 configured _HSLayer2Nodes set
 Aug 26 22:28:46.000 [warn] Failed to find node for hop #2 of our path.
 Discarding this circuit.
 [08-26 22:28:46] TorLauncher DBUG: Event response: 650 WARN Could not find
 a node that matches the configured _HSLayer2Nodes set
 [08-26 22:28:46] TorLauncher DBUG: Event response: 650 WARN Failed to find
 node for hop #2 of our path. Discarding this circuit.
 Aug 26 22:28:47.000 [warn] Failed to find node for hop #2 of our path.
 Discarding this circuit.
 [08-26 22:28:47] TorLauncher DBUG: Event response: 650 WARN Failed to find
 node for hop #2 of our path. Discarding this circuit.
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31527#comment:8>
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] #31527 [Applications/Tor Browser]: In Tor Browser nightly, Tor fails to boostrap, hangs at 50%
  - From: Tor Bug Tracker & Wiki

Prev by Author: [tor-bugs] #31382 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for federico (OONI)
Next by Author: Re: [tor-bugs] #31252 [Circumvention/BridgeDB]: Equip BridgeDB with anti-bot mechanism
Previous by thread: Re: [tor-bugs] #31527 [Core Tor/Tor]: In Tor Browser nightly, Tor fails to boostrap, hangs at 50%
Next by thread: Re: [tor-bugs] #31527 [Core Tor/Tor]: In Tor Browser nightly, Tor fails to boostrap, hangs at 50%
Index(es):
- Author
- Thread