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

Re: [tor-bugs] #7164 [Tor]: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1



#7164: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced
1 node(s); held_by_nodes == 1
------------------------+-------------------------------------------------
     Reporter:  jaj123  |      Owner:
         Type:  defect  |     Status:  needs_information
     Priority:  major   |  Milestone:  Tor: 0.2.???
    Component:  Tor     |    Version:  Tor: 0.2.4.19
   Resolution:          |   Keywords:  tor-client 024-backport 025-triaged
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-------------------------------------------------

Comment (by AndrewBuck):

 I'm not technical enough a user to understand the details in the
 discussion above but I will give a couple more datapoints here just in
 case it helps in diagnosing the issue.  I run a middle relay on version
 2.5.10 (but I started seeing these about a week ago on 2.5.9).  I had
 never seen them before but I kept getting them every hour (about 20 at a
 time).  After a few days of this I restarted my relay both to update to
 2.5.10 and to see if that cleared up the issue.  After restart the relay
 worked normally for about a week and now I am seeing them again.  Here is
 one pair of lines (again getting about 20 of these every hour).

 Nov 12 07:25:07.334 [Warning] microdesc_cache_clean(): Bug:
 Microdescriptor seemed very old (last listed 168 hours ago vs 168 hour
 cutoff), but is still marked as being held by 1 node(s). I found 1 node(s)
 holding it. Current networkstatus is 0 hours old. Hashtable badness is 0.

 Nov 12 07:25:07.338 [Warning] microdesc_cache_clean(): Bug:   [0]:
 ID=18E0BC920307C0B79F576EDB3473D74D4D1BCA94. md=0x7f8a1bcdaf60,
 rs=0x7f8a1d09c290, ri=0x7f8a1d86c200. Microdesc digest in RS does match.
 RS okay in networkstatus.

 Here is my node on atlas if that helps as well.
 https://atlas.torproject.org/#details/55E80F21D6D05CD5FAE52DAEF19EB9E62B8E1F6B

 Everything in the logs looks normal before these errors start cropping up,
 the only thing even a bit out of place is that in the last heartbeat
 before the errors start I am seeing about 8000 TAP handshakes compared to
 3 or 4 thousand normally (the number of circuits and NTor handshakes are
 normal though).

 Anyway, hope this information helps diagnose the problem.  I will keep my
 relay up like this for a couple more days before restarting in case there
 is any other kind of information you would like gathered from it.

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