Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 343
    • Issues 343
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #40233

Assertion when starting an IPv4-only bridge on 0.4.5.2-alpha

When I set up a bridge on FreeBSD, I got this issue.

Jan 01 21:10:44.000 [notice] Bootstrapped 0% (starting): Starting
Jan 01 21:10:44.000 [notice] Starting with guard context "default"
Jan 01 21:10:44.000 [notice] Registered server transport 'obfs4' at '[::]:80'
Jan 01 21:10:45.000 [warn] tor_bug_occurred_: Bug: src/feature/relay/relay_find_addr.c:201: relay_addr_learn_from_dirauth: Non-fatal assertion !(!node) failed. (on Tor 0.4.5.2-alpha )
Jan 01 21:10:
Jan 01 21:10:45.000 [warn] Bug:     0x11a2ad2 <router_build_fresh_descriptor+0x2a2> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x11a1f3f <router_rebuild_descriptor+0x6f> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x11a1d49 <consider_publishable_server+0x39> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x1225714 <reschedule_descriptor_update_check+0x274> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x122a77a <periodic_event_connect+0x10a> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x8013fe0ed <event_base_assert_ok_nolock_+0xa5d> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x8013fa09c <event_base_loop+0x53c> at /usr/local/lib/libevent-2.1.so.7 (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x116c861 <do_main_loop+0xf1> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x1155cbc <tor_run_main+0x12c> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x1154651 <tor_main+0x61> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )
Jan 01 21:10:45.000 [warn] Bug:     0x1154309 <main+0x19> at /usr/local/bin/tor (on Tor 0.4.5.2-alpha )

This happened on FreeBSD 12.2 on a bridge on Microsoft Azure. Tor was installed via pkg and I do not have a local-link IPv6 address.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking