Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #3183

Closed (moved)
(moved)
Open
Created May 14, 2011 by Trac@tracbot

heartbeat message inappropriate for bridge

[11:39] j__ what does this mean, is it important? if so, what do I do to fix it? "[Notice] Heartbeat: It seems like we are not in the cached consensus." ... [13:08] rransom Then you compiled without bufferevents enabled, and it was still broken. ... [13:09] rransom (Or you just hit the same intermittent brokenness that we've had for ages, even on 0.2.2.x--- A bridge shouldn't be in the consensus. [13:09] rransom j__: Were you running a bridge or a public relay? [13:11] j__ I'm running a bridge ... [13:12] rransom j__: If you were running a bridge, there may have been nothing wrong with it.

Trac:
Username: keb

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