Opened 6 months ago

Last modified 4 months ago

#28927 needs_information defect

TB 8.5a6 using obfs4 did not leave dormant mode on request

Reported by: traumschule Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor Version: Tor: 0.3.5.5-alpha
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Today a long running TB 8.5a6 using obfs4 repeatedly logged about being in dormant mode and did not build any circuits for existing and new tabs until the bridge was disabled. Then everything worked again.

Tor version: 0.3.5.5-alpha (git-a2ecc19ab923f34c) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.0.2q, Zlib 1.2.8, Liblzma N/A, and Libzstd N/A.

Related: #2149, #25375, #28335, #28847, #28849

Steps to reproduce:

  1. Start a fresh TB 8.5a6 with --debug --log and enable obfs4.
  2. Use it for some days.
  3. Let it run idle for some hours.

Step 2 may be optional, the computer was suspended several times but not the day this bug happened.

Will add the exact message when it happens again.

Child Tickets

Change History (3)

comment:1 Changed 6 months ago by traumschule

grep did not reveal anything familiar on tor-0.3.5.5-alpha and in the obfs4 repo, except a similar (fixed) bug.

comment:2 Changed 6 months ago by nickm

Milestone: Tor: 0.3.5.x-final
Status: newneeds_information

Hrm. It would also be great to have the configuration here, and the logs too.

There is dormancy (in the sense of hibernation) in 0.3.5.5, but the full-fledged "dormant mode" code didn't get added until 0.4.0.

comment:3 Changed 4 months ago by teor

Milestone: Tor: 0.3.5.x-finalTor: unspecified

If this happens again, please let us know.

Note: See TracTickets for help on using tickets.