Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #3942

Closed (moved)
Open
Opened Sep 06, 2011 by fk@fk

Tor client "Decided to publish new relay descriptor"

When logging at info level, my Tor client informs be about once per minute that it decided to publish a relay descriptor:

fk@r500 ~ $grep 'Decided to publish new relay' /usr/jails/tor-jail/usr/local/var/log/tor/info.log | tail Sep 06 22:42:16.255 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:43:17.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:44:18.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:45:19.255 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:46:20.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:47:21.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:48:22.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:49:23.254 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:50:24.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:51:25.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor

Given that it isn't actually a relay, that seems odd.

It's my impression that nothing actually gets published, though, at least (when idle), the log looks like this:

Sep 06 22:56:30.255 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:56:30.255 [info] {DIR} routerlist_remove_old_routers(): We have 2804 live routers and 0 old router descriptors. Sep 06 22:57:31.255 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:57:31.256 [info] {DIR} routerlist_remove_old_routers(): We have 2804 live routers and 0 old router descriptors. Sep 06 22:58:32.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor Sep 06 22:58:32.256 [info] {DIR} routerlist_remove_old_routers(): We have 2804 live routers and 0 old router descriptors. Sep 06 22:59:33.256 [info] {OR} mark_my_descriptor_dirty(): Decided to publish new relay descriptor: time for new descriptor

No messages from router_pick_published_address(), which I see on actual relays.

Another reason is 'config change', but it appears a lot less frequently.

It looks like the messages started to appear with Tor 0.2.3.2-alpha, but I only noticed them after the upgrade to 0.2.3.3-alpha.

I didn't get any such messages with Tor 0.2.3.1-alpha.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.3.x-final
Milestone
Tor: 0.2.3.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#3942