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

Re: [tor-bugs] #4953 [Tor Support]: Tor no longer starts



#4953: Tor no longer starts
-------------------------+--------------------------------------------------
 Reporter:  tomorrow     |          Owner:  runa
     Type:  defect       |         Status:  new 
 Priority:  normal       |      Milestone:      
Component:  Tor Support  |        Version:      
 Keywords:               |         Parent:      
   Points:               |   Actualpoints:      
-------------------------+--------------------------------------------------

Comment(by tomorrow):

 Sorry, full log file did not copy in. Here is is. I am running on Centos
 5.


 Jan 24 10:12:21.390 [notice] Tor 0.2.1.19 opening new log file.
 Jan 24 10:12:21.390 [notice] Parsing GEOIP file.
 Jan 24 10:12:21.728 [notice] No current certificate known for authority
 moria1; launching request.
 Jan 24 10:12:21.729 [notice] Bootstrapped 5%: Connecting to directory
 server.
 Jan 24 10:12:21.737 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no recent network-status
 consensus.
 Jan 24 10:12:21.754 [notice] Bootstrapped 10%: Finishing handshake with
 directory server.
 Jan 24 10:12:21.881 [notice] Bootstrapped 15%: Establishing an encrypted
 directory connection.
 Jan 24 10:12:21.960 [notice] Bootstrapped 20%: Asking for networkstatus
 consensus.
 Jan 24 10:12:21.984 [notice] Bootstrapped 25%: Loading networkstatus
 consensus.
 Jan 24 10:12:22.072 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '146.185.23.180:443' while fetching consensus directory.
 Jan 24 10:12:22.448 [warn] Received http status code 404 ("Not found")
 from server '82.165.193.175:9001' while fetching
 "/tor/keys/fp/E2A2AF570166665D738736D0DD58169CC61D8A8B".
 Jan 24 10:13:22.783 [notice] No current certificate known for authority
 moria1; launching request.
 Jan 24 10:13:23.242 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '85.25.108.113:9001' while fetching consensus directory.
 Jan 24 10:13:24.031 [warn] Received http status code 404 ("Not found")
 from server '38.229.70.53:443' while fetching
 "/tor/keys/fp/E2A2AF570166665D738736D0DD58169CC61D8A8B".
 Jan 24 10:14:07.112 [warn] Your application (using socks5 to port 80) is
 giving Tor only an IP address. Applications that do DNS resolves
 themselves may leak information. Consider using Socks4A (e.g. via privoxy
 or socat) instead. For more information, please see
 http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS.
 Jan 24 10:14:07.112 [notice] Application request when we're believed to be
 offline. Optimistically trying directory fetches again.
 Jan 24 10:14:07.938 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '77.247.181.163:443' while fetching consensus directory.
 Jan 24 10:15:25.575 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '77.40.164.50:9123' while fetching consensus directory.
 Jan 24 10:16:07.896 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4953#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