Opened 5 years ago

Closed 5 years ago

#14950 closed enhancement (fixed)

Quiet spammy log messages in 0.2.6

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.2.6.x-final
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Sebastian sees

Feb 11 13:29:45.000 [notice] Caching new entry debian-tor for debian-tor
Feb 11 13:29:45.000 [notice] Caching new entry debian-tor for debian-tor
Feb 11 13:29:45.000 [notice] Caching new entry debian-tor for debian-tor
Feb 11 13:29:45.000 [notice] Caching new entry debian-tor for debian-tor

in his log each day. That should happen at most once ever -- and maybe even never? I think Sebastian does not care that we are wrapping getpwnam() so something about a sandbox?

Similarly, the four-times-daily heartbeat has grown to

Feb 11 13:29:53.000 [notice] Heartbeat: Tor's uptime is 9 days 0:00 hours, with 9067 circuits open. I've sent 3900.89 GB and received 3765.17 GB.
Feb 11 13:29:53.000 [notice] Average packaged cell fullness: 98.648%
Feb 11 13:29:53.000 [notice] TLS write overhead: 3%
Feb 11 13:29:53.000 [notice] Circuit handshake stats since last time: 107838/107846 TAP, 80881/80881 NTor.

Yawning, Sebastian, and I think we can get rid of the middle two lines for sure. Maybe the last one too but maybe not quite yet.

What other spammy log lines are people seeing in their client or their relay or their hidden service that would distract or spook them if they were a normal user?

Child Tickets

Change History (7)

comment:1 Changed 5 years ago by nickm

When I start a Tor client, I see:

Feb 19 09:15:40.784 [notice] Tor v0.2.6.2-alpha-dev (git-0e22da1b8de0bc10) running on Darwin with Libevent 2.0.22-stable, OpenSSL 0.9.8zc and Zlib 1.2.5.
Feb 19 09:15:40.784 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 19 09:15:40.784 [notice] This version is not a stable Tor release. Expect more bugs than usual.
Feb 19 09:15:40.799 [notice] Read configuration file "/Users/nickm/.torrc".
Feb 19 09:15:40.804 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 19 09:15:40.000 [notice] Bootstrapped 0%: Starting
Feb 19 09:15:42.000 [notice] Bootstrapped 5%: Connecting to directory server
Feb 19 09:15:42.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Feb 19 09:15:42.000 [notice] We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Feb 19 09:15:42.000 [notice] To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features.
Feb 19 09:15:42.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection
Feb 19 09:15:43.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus
Feb 19 09:15:43.000 [notice] Bootstrapped 25%: Loading networkstatus consensus
Feb 19 09:15:43.000 [notice] Bootstrapped 45%: Asking for relay descriptors
Feb 19 09:15:43.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 15/6955, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
Feb 19 09:15:44.000 [notice] Bootstrapped 50%: Loading relay descriptors
Feb 19 09:15:45.000 [notice] Bootstrapped 55%: Loading relay descriptors
Feb 19 09:15:46.000 [notice] Bootstrapped 62%: Loading relay descriptors
Feb 19 09:15:46.000 [notice] Bootstrapped 69%: Loading relay descriptors
Feb 19 09:15:46.000 [notice] Bootstrapped 76%: Loading relay descriptors
Feb 19 09:15:46.000 [notice] We now have enough directory information to build circuits.
Feb 19 09:15:46.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Feb 19 09:15:46.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Feb 19 09:15:47.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Feb 19 09:15:47.000 [notice] Bootstrapped 100%: Done

That's probably too chatty. I'm not sure I'd notice a warning in here if I weren't looking for it.

comment:2 Changed 5 years ago by nickm

I'm collecting patches here in "ticket14950_logs" here. I addressed the issues in the original report so far.

For the ones on startup, I am thinking of trying to sort things a little better, by making this happen earlier:

Feb 19 09:15:42.000 [notice] We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
Feb 19 09:15:42.000 [notice] To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features.

and suppress these when they are redundant with bootstrapped messages:

Feb 19 09:15:43.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 15/6955, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
Feb 19 09:15:46.000 [notice] We now have enough directory information to build circuits.
Feb 19 09:15:47.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.

comment:3 Changed 5 years ago by nickm

Status: newneeds_review

comment:4 Changed 5 years ago by yawning

Looks good to me with the fixup.

comment:5 Changed 5 years ago by nickm

Status: needs_reviewnew

Merging that part, leaving this ticket open for more possible log-quietings

comment:6 Changed 5 years ago by nickm

Status: newneeds_information

Quieted another at startup with 783a44f9e98953e3359fd5ccc1788d993808fa64. The ones I wanted to suppress-when-redundant are actually a little tricky to tease out when redundant. I'm throwing this into needs_information; the information in question is "Should we quiet any more messages?"

comment:7 Changed 5 years ago by nickm

Resolution: fixed
Status: needs_informationclosed

Haven't got any more complaints in the last week; closing for now.

Note: See TracTickets for help on using tickets.