[tor-bugs] #28223 [Core Tor/Tor]: Unparseable microdescriptor on public relay

[Tor Bug Tracker & Wiki]

#28223: Unparseable microdescriptor on public relay
-------------------------------------------------+-------------------------
 Reporter:  teor                                 |          Owner:  nickm
     Type:  defect                               |         Status:
                                                 |  needs_review
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.4.0.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  040-roadmap-proposed, regression?,   |  Actual Points:  .2
  035-can, postfreeze-ok, 040-deferred-20190220  |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by madage):

 This bug happened on a Linux 32bit machine with self compiled kernel and
 tor. Tor was built without libseccomp/sandbox support. libc is glibc 2.28.

 After nick brought the 41min gap between last-listed relay times to my
 attention, I thought it was related to a power failure that seems to have
 happened at that time. kern.log has a last entry about 9h10 and a reboot
 at 9h48. However, after a close look at tor notice.log, I see that tor
 itself was restarted at 9h10 after not being able to get a rendevous
 descriptor and it finished bootstraping at 9h11. After that tor was
 restarted again at 9h49.

 I should mention that I was not the user who first reported this to teor
 months back, but maybe (s)he had a power failure/tor restart while
 fetching the microdescriptors as well?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28223#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online