corridor causes Tor assertion failure on Qubes-Fedora-26-minimal standalone proxyVM about corridor HOT 5 CLOSED

Yup, 0.3.1.9 includes the Make changes in server_mode() affect workers; fix a crash. commit, which should fix this bug.

Strangely though, the crash only happened for me when corridor was running.

That makes sense: tor starts in client mode, then corridor-data dynamically reconfigures it to server mode (using the SETCONF command).

I think it's safe to close this bug. Feel free to reopen if the problem still occurs in 0.3.1.9 or any other version that merged the bugfix commit.

from corridor.

Thanks! I'm able to reproduce this.

As a workaround, it seems that removing the line SETCONF DirPort="127.0.0.1:9030 NoAdvertise" from /usr/sbin/corridor-data and adding DirPort 127.0.0.1:9030 NoAdvertise to /etc/tor/torrc avoids the tor daemon crash.

from corridor.

Thanks, the workaround is working for me also.

Ticket 23693: Assertion threadpool failed in cpuworker_queue_work describes the issue I was experiencing. It was reported against 0.3.1.7 but I don't think the fix made it into 0.3.1.8. I will test again with 0.3.1.9. It may not be a corridor issue at all. Strangely though, the crash only happened for me when corridor was running.

from corridor.

Ugh, still present in 0.3.1.9

from corridor.

Fixed in tor 0.3.4.1 alpha, 0.3.3.6 stable, and presumably the upcoming 0.3.2.11 and 0.3.1.11 releases - see ticket 23693

from corridor.