Something tried to close an or_connection_t without going through channels at src/or/connection.c:3138

[notice] Tor 0.2.4.6-alpha-dev (git-c8056dcbbb9b468f)
...
[warn] Something tried to close an or_connection_t without going through channels at src/or/connection.c:3138

added bufferevents component::core tor/tor priority::medium resolution::fixed severity::normal status::closed tor-client type::defect labels

The warning still occurs in the latest git snap

[notice] Tor 0.2.4.6-alpha-dev (git-b1ff8daeb521d164)
...
[warn] Something tried to close an or_connection_t without going through channels at src/or/connection.c:3138

Looks like this should only happen if you're running with bufferevents. Are you running with bufferevents? They're kind of buggy still. Nonetheless, we should fix this.

Trac:
Cc: N/A to andrea
Keywords: N/A deleted, tor-client bufferevents added
Milestone: N/A to Tor: 0.2.4.x-final

I'm not the OP, but I can confirm that compiling without bufferevents seems to workaround the problem.

Trac:
Milestone: Tor: 0.2.4.x-final to Tor: 0.2.5.x-final

Trac:
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.???

A user on #tor reports a similar log line (connection.c:3722) in Tor 0.2.7.6.

He also apparently had bufferevents on. Apparently the FreeBSD ports option makes it easy to click "yes turn bufferevents on". :(

Trac:
Reviewer: N/A to N/A
Sponsor: N/A to N/A
Severity: N/A to Normal

Trac:
Username: U+039b

FreeBSD Tor port configuration

Trac:
Username: U+039b

On FreeBSD,

cd /usr/ports/security/tor

make config

shows if bufferevents is enabled or not. See  FreeBSD_Tor_port_config.png

Trac:
Username: U+039b

I filed a ticket on FreeBSD bugzilla: !https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210389

Trac:
Username: U+039b

This bug needs to be clarified. Is there a bug in the FreeBSD port, or is bufferevents option generally broken?

The bufferevents option is broken and not to be used. Anything that enables it is definitely buggy, and anything that gives users the option to enable it should have that fixed too.

We've removed that option entirely from Tor 0.2.9.x.

I wonder if that means we should close this ticket and ones like it? Either with wont-fix, or with I-did-fix-and-the-fix-was-to-rip-it-out?

Close it then.

Fixed by removing the feature that had the bug.

Trac:
Resolution: N/A to fixed
Status: new to closed

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Milestone deleted

Trac:
Milestone: Tor: 0.3.??? to N/A

closed

moved to tpo/core/tor#7734 (closed)