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

[Tor Bug Tracker & Wiki]

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

Comment (by teor):

 No, this fix is not in 0.3.3.5-rc:
 https://blog.torproject.org/tor-0335-rc-released
 But it is in nightly.

 The fix will be available in the next 0.3.1, 0.3.2, and 0.3.3 releases.

 Your options are:
 * upgrade to nightly using the instructions at
 https://www.torproject.org/docs/debian.html.en
 * downgrade to 0.2.9
 * add the following lines to your torrc as a workaround:
 {{{
 ORPort 12345
 PublishDescriptor 0
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

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

Comment (by tiejohg2sahth):

 My I ask when the fix will be available through the official PPA on Ubuntu
 18.04?

 I see with:
 {{{
 curl -s https://deb.torproject.org/torproject.org/pool/main/t/tor/ | grep
 -o '"tor_.*bionic.*_amd64\.deb"'
 }}}
 that 0.3.3.5-rc1 and 0.3.4.0-alpha are available in the PPA, presumably
 with the fix for this bug merged in it, however when I update with apt, I
 am still stuck with the 0.3.2.10 version which is unfortunately unusable.

 Or is there a particular step to do to be able to update to the pre-
 release versions?

 Thank you

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

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

Comment (by nickm):

 The original version of this patch had a bug: #23693.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

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

 * status:  merge_ready => closed
 * resolution:   => fixed


Comment:

 merged!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 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 asn):

 * status:  needs_review => merge_ready


Comment:

 LGTM and tests pass.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 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 nickm):

 * status:  new => needs_review


Comment:

 I've updated `bug23693_031_redux` with an actual commit to actually work.
 I'm fine merging it to 0.3.1 and forward; we can open a separate ticket to
 test or disable the feature.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_information
 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 nickm):

 * cc: arma (added)
 * status:  needs_revision => needs_information


Comment:

 Putting this into needs_information based on Teor's questions above.
 Roger, what do you think here?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 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:
-+-

Comment (by teor):

 Maybe we will deprecate DirPort some time in the future. Maybe we won't,
 There are bootstrapping and diagnostic issues.

 But here are some questions we can answer right now:
 * Do we support DirPort without ORPort?
 * If we do, when was the last Tor release that it actually worked?
 * Why don't we have any tests for DirPort only operation?

 As far as I can tell, people who get this bug seem to be setting DirPort
 as a workaround.
 They don't actually want to serve descriptors, they just want them
 available locally.

 If we can't find a use case that involves serving descriptors, I think we
 should:
 * fix the hibernation options so they allow people to download descriptors
 every hour if that's what they need, then
 * deprecate DirPort-only operation

 But I'm not sure if we can remove features as a backport, so we are stuck
 with fixing crashes like this (or saying "don't do that").

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 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:
-+-

Comment (by asn):

 Hmm, I took the torrc from comment:28 to test the patch. The original
 assert seems to be fixed but now it crashes on a different place:
 {{{
 Apr 17 14:01:00.000 [notice] Bootstrapped 0%: Starting
 Apr 17 14:01:00.000 [notice] Starting with guard context "default"
 Apr 17 14:01:00.000 [err] tor_assertion_failed_(): Bug:
 src/or/router.c:142: dup_onion_keys: Assertion onionkey failed; aborting.
 (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: Assertion onionkey failed in dup_onion_keys
 at src/or/router.c:142. Stack trace: (on Tor 0.3.1.10-dev
 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(log_backtrace+0x43)
 [0x557795fffab3] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug:
 ./src/or/tor(tor_assertion_failed_+0x8d) [0x557796018add] (on Tor
 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(dup_onion_keys+0x10f)
 [0x557795f22a9f] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug:
 ./src/or/tor(server_onion_keys_new+0x41) [0x557795ef2f91] (on Tor
 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(+0x1283b7)
 [0x557795fb93b7] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(threadpool_new+0x18b)
 [0x55779601f91b] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(cpu_init+0xad)
 [0x557795fb97dd] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(do_main_loop+0x15d)
 [0x557795ee0d2d] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(tor_main+0xe25)
 [0x557795ee3b25] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(main+0x19)
 [0x557795edc729] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: /lib/x86_64-linux-
 gnu/libc.so.6(__libc_start_main+0xe7) [0x7faf9e096a87] (on Tor
 0.3.1.10-dev 386f8016b7373bec)
 Apr 17 14:01:00.000 [err] Bug: ./src/or/tor(_start+0x2a)
 [0x557795edc77a] (on Tor 0.3.1.10-dev 386f8016b7373bec)
 }}}

 I guess that when we are not in server mode, Tor won't create the onionkey
 in `init_keys()`... I wonder if we should try to fix these situations with
 patches like the one from comment:29, or we should just disallow having a
 DirPort without an ORPort and abort if such a configuration is seen. IIUC,
 we are planning to eventually deprecate DirPort anyhow and just use
 `BEGIN_DIR`, right?

 Here is the torrc:
 {{{
 DirPort 9030
 SocksPort 0
 Log notice stdout
 DataDirectory /tmp/tor
 RelayBandwidthRate 4 MBytes
 RelayBandwidthBurst 5 MBytes
 ExitRelay 0
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 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 asn):

 * status:  needs_review => needs_revision


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 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 asn):

 * reviewer:  dgoulet => asn


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 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:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

 * reviewer:   => dgoulet


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 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:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  prop286, 034-triage-20180328, 034-must crash 033-backport
 032-backport =>
 prop286, 034-triage-20180328, 034-must crash 033-backport 032-backport
 031-backport
 * status:  reopened => needs_review


Comment:

 Okay, there's a fix in `bug23693_031_redux`, probably.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  reopened
 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   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by tiejohg2sahth):

 Replying to [comment:26 nickm]:
 > The most useful information here would be the tor version and your
 configuration (the torrc file)
 Tor version as reported by apt-cache show tor: 0.3.2.10-1~bionic+1
 My torrc: https://pastebin.com/raw/CWTMmwHc

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  reopened
 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   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arma):

 Replying to [comment:21 arma]:
 > Running maint-0.3.2, I start my Tor client with
 {{{fetchuselessdescriptors 1 dirport 9030}}}, and on startup I get this
 stacktrace and abort

 To be clear, this is repeatable. I just did it again now, with Tor master:
 {{{
 Apr 09 21:59:53.749 [err] Bug: Assertion threadpool failed in
 cpuworker_queue_work at src/or/cpuworker.c:510. Stack trace: (on Tor
 0.3.4.0-alpha-dev 21c81348a39dd235)
 Apr 09 21:59:53.749 [err] Bug: src/or/tor(log_backtrace+0x42)
 [0x5649ed2260b2] (on Tor 0.3.4.0-alpha-dev 21c81348a39dd235)
 Apr 09 21:59:53.749 [err] Bug: src/or/tor(tor_assertion_failed_+0x8c)
 [0x5649ed24140c] (on Tor 0.3.4.0-alpha-dev 21c81348a39dd235)
 Apr 09 21:59:53.749 [err] Bug: src/or/tor(cpuworker_queue_work+0x6f)
 [0x5649ed1c9cbf] (on Tor 0.3.4.0-alpha-dev 21c81348a39dd235)
 Apr 09 21:59:53.749 [err] Bug: src/or/tor(consdiffmgr_rescan+0x839)
 [0x5649ed1bc169] (on Tor 0.3.4.0-alpha-dev 21c81348a39dd235)
 [...]
 }}}
 You could too, I think!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  reopened
 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   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 The most useful information here would be the tor version and your
 configuration (the torrc file)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  reopened
 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   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by tiejohg2sahth):

 I am affected by this bug too with the same stack trace as the original
 poster.

 I have just migrated from Ubuntu 14.04 to 18.04. Tor was installed from
 the official PPA.

 I am running a relay and have very little changes from the default
 configuration.
 I am available if you need more data to reproduce.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  reopened
 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   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  prop286, 034-triage-20180328, 034-removed-20180328 => prop286,
 034-triage-20180328, 034-must crash 033-backport 032-backport


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
--+
 Reporter:  alif  |  Owner:  nickm
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.9
 Severity:  Normal| Resolution:
 Keywords:  prop286   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 Running maint-0.3.2, I start my Tor client with {{{fetchuselessdescriptors
 1 dirport 9030}}}, and on startup I get this stacktrace and abort:
 {{{
 Jan 06 04:25:28.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop
 Jan 06 04:25:29.000 [err] tor_assertion_failed_(): Bug:
 src/or/cpuworker.c:499: cpuworker_queue_work: Assertion threadpool failed;
 aborting. (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: Assertion threadpool failed in
 cpuworker_queue_work at src/or/cpuworker.c:499. Stack trace: (on Tor
 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(log_backtrace+0x42)
 [0x55f592aa5922] (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(tor_assertion_failed_+0x8c)
 [0x55f592ac071c] (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(cpuworker_queue_work+0x6f)
 [0x55f592a4bb1f] (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(consdiffmgr_rescan+0x82f)
 [0x55f592a3e44f] (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(+0x51aaf) [0x55f592973aaf]
 (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x7fc) [0x7fbd389a03dc] (on Tor
 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(do_main_loop+0x244)
 [0x55f5929747c4] (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(tor_main+0x1c25)
 [0x55f592978005] (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(main+0x19) [0x55f59296ff29]
 (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: /lib/x86_64-linux-
 gnu/libc.so.6(__libc_start_main+0xf5) [0x7fbd3794ab45] (on Tor 0.3.2.8-rc-
 dev 5f2c7a85671ee514)
 Jan 06 04:25:29.000 [err] Bug: src/or/tor(+0x4df79) [0x55f59296ff79]
 (on Tor 0.3.2.8-rc-dev 5f2c7a85671ee514)
 Aborted
 }}}

 Looks like the consensus diff manager wants to use the threadpool, but I'm
 not a relay so nothing set it up.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
--+
 Reporter:  alif  |  Owner:  nickm
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.9
 Severity:  Normal| Resolution:
 Keywords:  prop286   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:  029-backport, 030-backport, 031-backport, review-group-24 =>
 prop286
 * version:  Tor: 0.3.1.7 => Tor: 0.3.1.9


Comment:

 Replying to [comment:17 rustybird]:
 > > (please reopen if this bug occurs in any version released _after_
 today.)
 >
 > It still occurs if `server_mode()` is false but `dir_server_mode()` is
 true. Doesn't seem to make a difference (with 0.3.1.9) if it is set up
 like that in `torrc` on startup, or the result of being reconfigured.
 >
 > (Use case for this configuration: http://github.com/rustybird/corridor
 calls `SETCONF DirPort="127.0.0.1:9030 NoAdvertise"` to ensure the client
 continues to refresh the consensus even when dormant.)

 Running a directory mirror will cause a lot of unnecessary load and disk
 usage, particularly with newer tor versions. You'll generate a whole bunch
 of compressed diffs that you'll never serve.

 Try using `FetchDirInfoEarly 1` instead. If this doesn't work, just issue
 a RESOLVE request to a common address every hour or two at random, to keep
 tor alive. We have a proposal for a better controller API for this.

 Also, if you want a consensus with IPv6 addresses on a client, use
 `UseMicrodescriptors 0`.

 If you don't care about descriptors, and want to save bandwidth, use
 `FetchServerDescriptors 0`. You might find some bugs using this option,
 it's not well-tested.

 You can set `SOCKSPort 0` if you're not using it. It might add a bit of
 security.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  reopened
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport, 030-backport,  |  Actual Points:
  031-backport, review-group-24  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.4.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  reopened
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport, 030-backport,  |  Actual Points:
  031-backport, review-group-24  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * milestone:  Tor: 0.2.9.x-final => Tor: 0.3.2.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  reopened
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport, 030-backport,  |  Actual Points:
  031-backport, review-group-24  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by rustybird):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 > (please reopen if this bug occurs in any version released _after_
 today.)

 It still occurs if `server_mode()` is false but `dir_server_mode()` is
 true. Doesn't seem to make a difference (with 0.3.1.9) if it is set up
 like that in `torrc` on startup, or the result of being reconfigured.

 (Use case for this configuration: http://github.com/rustybird/corridor
 calls `SETCONF DirPort="127.0.0.1:9030 NoAdvertise"` to ensure the client
 continues to refresh the consensus even when dormant.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:  fixed
 Keywords:  029-backport, 030-backport,  |  Actual Points:
  031-backport, review-group-24  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.3.2.x-final => Tor: 0.2.9.x-final


Comment:

 (please reopen if this bug occurs in any version released _after_ today.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport, 030-backport,  |  Actual Points:
  031-backport, review-group-24  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Thanks!  I've merged this to 0.2.9 and forward.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport, 030-backport,  |  Actual Points:
  031-backport, review-group-24  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => merge_ready


Comment:

 Replying to [comment:8 nickm]:
 > Possible fix in branch `bug23693_029` in my public repository, assuming
 I have the diagnosis right.

 lgtm; I confirm that going from client -> bridge is working properly.

 Agree on the backport.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 030-backport|  Actual Points:
  031-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by alif):

 Commenting out `#DirPort 9030` solves it. Re-enabling it reproduces that
 assertion failure.

 I now have a working Tor service that is able to go all the way to
 `Bootstrapped 100%: Done`.

 Please, note that I haven't tested commenting out Dirport within my
 original configuration before the introduced obfs4, bridge definitions and
 data files copied from Tor-Browser.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 030-backport|  Actual Points:
  031-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by alif):

 Now, trying to solve my connectivity problem, I installed obfs4proxy from
 the Xenial repository, and coped over the obfs4 bridges from Tor-browser's
 torrc but nothing happened. Still "[notice] While fetching directory info,
 no running dirservers known. Will try again later. (purpose 6)"

 But after I copied the "cached-x" files from Tor browser's Data directory
 to my system and restarting the service, the exception appeared again:

 {{{
  several messages pertaining to connecting to bridges  then
 Oct 03 00:54:12.000 [notice] new bridge descriptor '' (cached):
 $FC259A04A328A07FED1413E9FC6526530D9FD87A~NX01 at XX.XX.XX.XX
 Oct 03 00:54:12.000 [notice] new bridge descriptor 'X' (cached):
 $FE7840FE1E21FE0A0639ED176EDA00A3ECA1E34D~Azadi at XXX.XX.XX.XX
 Oct 03 00:54:12.000 [notice] Delaying directory fetches: Pluggable
 transport proxies still configuring
 Oct 03 00:54:12.000 [notice] Opening Socks listener on /var/run/tor/socks
 Oct 03 00:54:12.000 [notice] Opening Control listener on
 /var/run/tor/control
 Oct 03 00:54:13.000 [err] tor_assertion_failed_(): Bug:
 ../src/or/cpuworker.c:499: cpuworker_queue_work: Assertion threadpool
 failed; aborting. (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: Assertion threadpool failed in
 cpuworker_queue_work at ../src/or/cpuworker.c:499. Stack trace: (on Tor
 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /usr/bin/tor(log_backtrace+0x42)
 [0x55fb088902b2] (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug:
 /usr/bin/tor(tor_assertion_failed_+0x94) [0x55fb088a8904] (on Tor 0.3.1.7
 )
 Oct 03 00:54:13.000 [err] Bug: /usr/bin/tor(cpuworker_queue_work+0x65)
 [0x55fb0884c395] (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /usr/bin/tor(consdiffmgr_rescan+0x9a7)
 [0x55fb0883f037] (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /usr/bin/tor(+0x4ec7d) [0x55fb08776c7d]
 (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x754) [0x7fa5e1eecf24] (on Tor
 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /usr/bin/tor(do_main_loop+0x24d)
 [0x55fb08777a4d] (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /usr/bin/tor(tor_main+0x1c35)
 [0x55fb0877b215] (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /usr/bin/tor(main+0x19)
 [0x55fb087733c9] (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /lib/x86_64-linux-
 gnu/libc.so.6(__libc_start_main+0xf5) [0x7fa5e1099f45] (on Tor 0.3.1.7 )
 Oct 03 00:54:13.000 [err] Bug: /usr/bin/tor(+0x4b41b) [0x55fb0877341b]
 (on Tor 0.3.1.7 )
 }}}

 the files I copied are:
 cached-certs
 cached-descriptors
 cached-descriptors.new
 cached-microdesc-consensus
 cached-microdescs
 cached-microdescs.new

 lines changed in torrc:
 {{{
 ClientTransportPlugin obfs2,obfs3,obfs4,scramblesuit exec
 /usr/bin/obfs4proxy
 #ClientTransportPlugin obfs2,obfs3,ScrambleSuit exec /usr/bin/obfsproxy
 managed
 }}}
 then some obfs4 definitions copied from tor-browser

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 030-backport|  Actual Points:
  031-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by alif):

 Well, I'm no longer able to reproduce this! Sorry.
 It persisted for a couple of days after having updated Tor to 0.3.1.7
 using a deb from the projects repository, until I had to reboot for a
 different reason.

 Now I'm back to "[notice] While fetching directory info, no running
 diverseness known. Will try again later. (purpose 6)" which is preventing
 me from making a circuit via obfs3, even though I'm able to do so in the
 Tor-browser via obfs4. But that's a different issue.

 Anyway, my torrc at the time of the errors is the following (I had
 disabled bridges to try to debug and to make the report less complicated).
 I removed commented lines for clarity and redacted secrets:

 

 Log notice file /var/log/tor/notices.log

 ControlPort 9051
 HashedControlPassword 16:XXX

 PortForwarding 1

 Address redacted.example.com

 Nickname 

 ContactInfo elsewhereXX

 DirPort 9030 # what port to advertise for directory connections
 DirPortFrontPage /usr/share/doc/tor/tor-exit-notice.html

 ExitPolicy reject *:* # no exits allowed

 HiddenServiceStatistics 1

 UseBridges 0
 UpdateBridgesFromAuthority 1

 ClientTransportPlugin obfs2,obfs3,ScrambleSuit exec /usr/bin/obfsproxy
 managed

 #Some bridge definitions go here; obfs3 and plain
 

 Also here's my /etc/apparmor.d/abstractions/tor since I had modified it to
 be able to run obfsproxy in 14.04:
 
 # vim:syntax=apparmor

   #include 
   #include 

   network tcp,
   network udp,

   capability chown,
   capability dac_read_search,
   capability fowner,
   capability fsetid,
   capability setgid,
   capability setuid,

   /usr/bin/tor r,
   /usr/sbin/tor r,

   # Needed by obfs4proxy
   /proc/sys/net/core/somaxconn r,

   /proc/sys/kernel/random/uuid r,
   /sys/devices/system/cpu/ r,
   /sys/devices/system/cpu/** r,

   /etc/tor/* r,
   /usr/share/tor/** r,

   /usr/bin/obfsproxy PUx,
   /usr/bin/obfs4proxy Pix,
 

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
-+-
 Reporter:  alif |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.7
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 030-backport|  Actual Points:
  031-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:   => 029-backport 030-backport 031-backport


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
--+
 Reporter:  alif  |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.7
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  accepted => needs_review


Comment:

 Possible fix in branch `bug23693_029` in my public repository, assuming I
 have the diagnosis right.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
--+
 Reporter:  alif  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.7
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  new => accepted


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
--+
 Reporter:  alif  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.7
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 alif, if you could answer any of the questions above, that would help us
 diagnose and fix this bug.  I have some guesses below, but they're just
 guesses.

 Some ideas, based on looking at the code:  There are two ways I think this
 could happen: if we reach cpuworker_queue_work() without having called
 cpu_init(), or if we somehow fail to create a threadpool in cpu_init()
 when we do call it. But I don't think it can be the second case, since
 that would have created a nonfatal assertion from threadpool_new().

 We call cpu_init() in two cases: when our settings change, the transition
 affects workers, and we have become a server; or when we start as a server
 in main.c.

 I think that the check in the first cpu_init() case might be wrong: if we
 start as a client, and then transition to a bridge (not a public server),
 I don't think we will trigger options_transition_affects_workers().

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23693 [Core Tor/Tor]: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work (was: 0.3.1.7 daemon fails)

[Tor Bug Tracker & Wiki]

#23693: 0.3.1.7: Assertion threadpool failed in cpuworker_queue_work
--+
 Reporter:  alif  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.7
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs