0

I built a directory server and make some relays use it, but every relay's log file contains these lines:

Heartbeat: It seems like we are not in the cached consensus.
Mar 28 20:28:04.000 [notice] Heartbeat: Tor's uptime is 1 day 17:59 hours, with 0 circuits open. I've sent 1.04 MB and received 772 kB.
Mar 28 20:28:04.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
Mar 28 20:28:04.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 1 v4 connections; and received 0 v1 connections, 0 v2 connections, 0 v3 connections, and 0 v4 connections.
Mar 28 22:40:03.000 [warn] Received http status code 404 ("Consensus not signed by sufficient number of requested authorities") from server '(my-server-ip):7000' while fetching consensus directory.

and these lines repeat a lot.

I find warn like these when restart a relay

Mar 30 12:45:56.000 [warn] Consensus does not include configured authority 'DA' at (my-server-ip):7000 (identity (my-server-identity ))
Mar 30 12:45:56.000 [warn] A consensus needs 1 good signatures from recognized authorities for us to accept it. This one has 0 (). It has 9 signatures from authorities we don't recognize.
Mar 30 12:45:56.000 [warn] Not enough good signatures on networkstatus consensus
Mar 30 12:45:56.000 [warn] Couldn't load consensus microdesc networkstatus from "/var/lib/tor/cached-microdesc-consensus"

could someone tell me what's wrong and what I can do to fix it?

  • I solve this problem. It caused by my mistake configuration of fingerprint – bella Apr 23 at 13:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.