[tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)

[Name Withheld]

Hi guys,

I've got a 1gbps (shared) debian server set up as an exit that can't 
seem to handle all the b/w through a single instance of tor.  After 
getting some help from the tor lists previously, I've started setting up 
additional instances of tor that run simultaneously to help handle more 
traffic.

Unfortunately, only the first of the extra instances works (even though 
I copied the config from the "known good" config and only changed the 
ports during other attempts).  Other instances seem to work at first, 
setting up the initial tunnels and passing very small amounts of traffic 
for about a half hour, but never seem to get listed in the directory, so 
they never get any other traffic once the initial tunnels all close, 
even after many hours pass.

Does anyone know why this is happening, and what I need to do to fix it?

Thank you.

Jul 26 12:26:06.064 [notice] Tor v0.2.3.19-rc (git-adf14e42194ebfb7) 
running on Linux.
Jul 26 12:26:06.064 [notice] Tor can't help you if you use it wrong! 
Learn how to be safe at https://www.torproject.org/download/download#warning
Jul 26 12:26:06.064 [notice] Read configuration file "/etc/tor/tor4.cfg".
Jul 26 12:26:06.065 [notice] Initialized libevent version 1.4.13-stable 
using method epoll. Good.
Jul 26 12:26:06.065 [notice] Opening Socks listener on 127.0.0.1:10054
Jul 26 12:26:06.065 [notice] Opening Control listener on 127.0.0.1:9054
Jul 26 12:26:06.065 [notice] Opening OR listener on 0.0.0.0:10004
Jul 26 12:26:06.065 [notice] Opening Directory listener on 0.0.0.0:10034
Jul 26 12:26:06.000 [notice] Not disabling debugger attaching for 
unprivileged users.
Jul 26 12:26:06.000 [notice] Parsing GEOIP file /usr/share/tor/geoip.
Jul 26 12:26:06.000 [notice] Configured to measure statistics. Look for 
the *-stats files that will first be written to the data directory in 24 
hours
  from now.
Jul 26 12:26:06.000 [warn] You are running Tor as root. You don't need 
to, and you probably shouldn't.
Jul 26 12:26:06.000 [notice] No AES engine found; using AES_* functions.
Jul 26 12:26:06.000 [notice] This version of OpenSSL has a slow 
implementation of counter mode; not using it.
Jul 26 12:26:06.000 [notice] OpenSSL OpenSSL 0.9.8o 01 Jun 2010 looks 
like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Jul 26 12:26:06.000 [notice] Your Tor server's identity key fingerprint 
is '00Teh0S1gnul00 26F728EF33D03C054B9417FAE92C809DCDEF5ED4'
Jul 26 12:26:06.000 [notice] Reloaded microdescriptor cache.  Found 3016 
descriptors.
Jul 26 12:26:06.000 [notice] We now have enough directory information to 
build circuits.
Jul 26 12:26:06.000 [notice] Bootstrapped 80%: Connecting to the Tor 
network.
*Jul 26 12:26:07.000 [notice] Heartbeat: It seems like we are not in the 
cached consensus.**
*Jul 26 12:26:07.000 [notice] Heartbeat: Tor's uptime is 0:00 hours, 
with 2 circuits open. I've sent 2 kB and received 2 kB.
Jul 26 12:26:07.000 [notice] Bootstrapped 85%: Finishing handshake with 
first hop.
Jul 26 12:26:07.000 [notice] We weren't able to find support for all of 
the TLS ciphersuites that we wanted to advertise. This won't hurt 
security, bu
t it might make your Tor (if run as a client) more easy for censors to 
block.
Jul 26 12:26:07.000 [notice] To correct this, use a more recent OpenSSL, 
built without disabling any secure ciphers or features.
Jul 26 12:26:08.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Jul 26 12:26:09.000 [notice] Tor has successfully opened a circuit. 
Looks like client functionality is working.
Jul 26 12:26:09.000 [notice] Bootstrapped 100%: Done.
Jul 26 12:26:09.000 [notice] Now checking whether ORPort 
93.114.43.156:10004 and DirPort 93.114.43.156:10034 are reachable... 
(this may take up to 20
minutes -- look for log messages indicating success)
Jul 26 12:26:10.000 [notice] Self-testing indicates your ORPort is 
reachable from the outside. Excellent. Publishing server descriptor.
Jul 26 12:26:13.000 [notice] Self-testing indicates your DirPort is 
reachable from the outside. Excellent.
Jul 26 12:26:19.000 [notice] Performing bandwidth self-test...done.
Jul 26 12:29:25.000 [notice] New control connection opened.
Jul 26 12:36:43.000 [notice] New control connection opened.
Jul 26 12:36:52.000 [notice] Received reload signal (hup). Reloading 
config and resetting internal state.
Jul 26 12:36:52.000 [notice] Read configuration file "/etc/tor/tor4.cfg".
Jul 26 12:54:25.000 [notice] Received reload signal (hup). Reloading 
config and resetting internal state.
Jul 26 12:54:25.000 [notice] Read configuration file "/etc/tor/tor4.cfg".
*Jul 26 18:26:07.000 [notice] Heartbeat: It seems like we are not in the 
cached consensus.**
**Jul 26 18:26:07.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, 
with 0 circuits open. I've sent 1.32 MB and received 4.44 MB.*
Jul 26 23:05:50.000 [notice] Received reload signal (hup). Reloading 
config and resetting internal state.
Jul 26 23:05:50.000 [notice] Read configuration file "/etc/tor/tor4.cfg".