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

Re: [tor-bugs] #23693 [Core Tor/Tor]: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-------------------------------------------------+-------------------------
 Reporter:  alif                                 |          Owner:  nickm
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.4.x-final
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.3.1.9
 Severity:  Normal                               |     Resolution:
 Keywords:  prop286, 034-triage-20180328,        |  Actual Points:
  034-must crash 033-backport 032-backport       |
  031-backport                                   |
Parent ID:                                       |         Points:
 Reviewer:  asn                                  |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):

 * status:  needs_information => new


Comment:

 I can reproduce this issue with the following minimal test case:
 {{{
 tor DataDirectory `mktemp -d` DirPort 12345 ORPort 0 SOCKSPort 0
 }}}

 This command works with these tor versions:
 * 0.2.5.16-dev
 * 0.2.9.15-dev

 This command fails for these tor versions:
 * 0.3.1.10-dev
 * 0.3.2.10-dev
 *
 * master

 With minor variations on:
 {{{
 Apr 18 10:08:27.000 [notice] Bootstrapped 40%: Loading authority key certs
 Apr 18 10:08:34.000 [err] tor_assertion_failed_: Bug:
 src/or/cpuworker.c:499: cpuworker_queue_work: Assertion threadpool failed;
 aborting. (on Tor 0.3.1.10-dev ce8e7427b9284ef1)
 ...
 }}}

 So I suggest:
 * now: we fix the bugs in this feature in 0.3.1 and later
 * in 0.3.4 or 0.3.5: we decide if we want to support DirPort-only and
 write tests for it, or if we want to deprecate it

 One use case for DirPort-only is a local directory mirror for large
 deployments. It can be configured using the FallbackDir torrc option, to
 take load off relays or authorities. But we could just tell people to use
 `ORPort 12345 PublishDescriptor 0` as a workaround.

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