Opened 11 years ago

Last modified 7 years ago

#852 closed defect (Fixed)

Ubuntu Intrepid fresh install - fails to find authority certificate 250A21E163A25851BB574E80DC4E41A

Reported by: grizzly Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.0.31
Severity: Keywords:
Cc: grizzly, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

tail -f /var/log/tor/log

What does it mean and how to help it?

[and so forth]
Nov 07 21:26:02.935 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:27:03.178 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:28:04.411 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:29:05.699 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:30:06.939 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:31:07.167 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
[and so forth]

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

Child Tickets

Change History (6)

comment:1 Changed 11 years ago by grizzly

Does this help?

sudo /etc/init.d/tor start

Raising maximum number of filedescriptors (ulimit -n) to 32768.
Starting tor daemon: tor...
Nov 07 21:35:08.784 [notice] Tor v0.2.0.31 (r16744). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Nov 07 21:35:08.787 [notice] Initialized libevent version 1.3e using method epoll. Good.
Nov 07 21:35:08.787 [notice] Opening OR listener on 0.0.0.0:9001
Nov 07 21:35:08.787 [notice] Opening Directory listener on 0.0.0.0:9030
Nov 07 21:35:08.788 [notice] Opening Socks listener on 127.0.0.1:9050
Nov 07 21:35:08.788 [notice] Opening Socks listener on 192.168.2.4:9050
done.

tail -f /var/log/tor/log

Nov 07 21:35:09.070 [notice] Your Tor server's identity key fingerprint is ""
Nov 07 21:35:09.431 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:35:10.122 [notice] We now have enough directory information to build circuits.
Nov 07 21:35:10.128 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:35:10.131 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:35:10.238 [notice] Guessed our IP address as ""
Nov 07 21:35:15.964 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Nov 07 21:35:15.965 [notice] Now checking whether ORPort "":9001 and DirPort "":9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Nov 07 21:35:22.717 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Nov 07 21:35:28.431 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Nov 07 21:36:11.392 [notice] We're missing a certificate from authority with signing key 250A21E163A25851BB574E80DC4E41AE86F60C89: launching request.
Nov 07 21:37:13.675 [notice] Performing bandwidth self-test...done.
Nov 07 21:37:53.883 [notice] We tried for 15 seconds to connect to "" using exit "". Retrying on a new circuit.

comment:2 Changed 11 years ago by nickm

That happened, I believe, because there was a bug in Tor that was triggered by one of the directory authorities
not replacing its certificate before it expired. See bug 851. Is stuff better now?

comment:3 Changed 11 years ago by nickm

ping. Is this still happening? Did it go away? Are you still there?

comment:4 Changed 11 years ago by grizzly

Hi nick, I only have so and so much time to check back with bugs I report. As for now, I regularly dist-upgraded my intrepid and all seems to work smoothly - tor sometimes is fast, sometimes is slow, depending obviously on the exit I catch myself.

BTW: where can one find info whether it is (still?) feasible to run 2xservers: one for surfing, one as relay/node under different start scripts?
BTW: I noticed for dir one has to offer >=50kB bandwith. While totalling to a hundred, I wished to donate 40 norm / 80 burst... Better guidelines would be nice...
BTW: when I run multi-uplink via iptables, what is the bandwith counted against? so I could give like 80/120 on 2xDSL-type uplinks?

My server log of today (usual uptime afternoon till 4:00 of my relay) looks good. Thanks. Seems fixed.

# I killed the internet - oops
Nov 20 03:25:55.858 [notice] While fetching directory info, no running dirservers known. Will try again later. (purpose 5)

#Timed shutdown of server
Nov 20 04:01:00.760 [notice] Interrupt: will shut down in 30 seconds. Interrupt again to exit now.
Nov 20 04:01:30.241 [notice] Clean shutdown finished. Exiting.

# It was started again
Nov 20 14:56:02.253 [notice] Tor 0.2.0.31 (r16744) opening log file.
Nov 20 14:56:02.644 [notice] Your Tor server's identity key fingerprint is
Nov 20 14:56:09.120 [notice] We now have enough directory information to build circuits.
Nov 20 14:56:09.200 [notice] Guessed our IP address as "".
Nov 20 14:56:10.217 [notice] Our directory information is no longer up-to-date enough to build circuits: We have only 209/1197 usable descriptors.
Nov 20 14:56:10.217 [notice] I learned some more directory information, but not enough to build a circuit: We have only 209/1197 usable descriptors.
Nov 20 14:56:11.414 [notice] I learned some more directory information, but not enough to build a circuit: We have only 209/1197 usable descriptors.
Nov 20 14:56:11.428 [notice] Our IP Address has changed from "" to ""; rebuilding descriptor.
Nov 20 14:56:11.477 [notice] We now have enough directory information to build circuits.
Nov 20 14:56:13.665 [notice] Our IP Address has changed from "" to ""; rebuilding descriptor.
Nov 20 14:56:18.889 [notice] Our IP Address has changed from "" to ""; rebuilding descriptor.
Nov 20 14:56:20.694 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Nov 20 14:56:20.694 [notice] Now checking whether ORPort "":9001 and DirPort "":9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Nov 20 14:56:50.049 [notice] Our IP Address has changed from "" to ""; rebuilding descriptor.
Nov 20 14:57:11.478 [notice] Our IP Address has changed from "" to ""; rebuilding descriptor.
Nov 20 14:57:13.749 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
# Up again

[and so on]

comment:5 Changed 11 years ago by phobos

flyspray2trac: bug closed.

comment:6 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.