Opened 8 years ago

Last modified 2 years ago

#4386 new defect

Requesting better "too slow" warning message

Reported by: tmpname0901 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay needs-design
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Over an 18-hour period Tor v0.2.2.34 logged 5 instances of "Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy." with several hundred more messages suppressed.

Since I've never seen these message before and because I've changed nothing in the 10 days since I updated to v0.2.2.34, I feel pretty confident I can blow off these warnings.

The message, though, give no indication of how far I am from being able to handle the number of pending requests. How would I know what value to configure MaxAdvertisedBandwidth with? How much more restrictive does the exit policy need to be? The problem is that I don't know if it was a single connection that couldn't be accomplished or 10,000 connections. If the former it makes sense to tweak my config; if the latter I can safely dismiss the warnings as resulting from some sort of attempted attack.

So... can we get more info in the "too slow" warning messages?

Thanks.

Child Tickets

Change History (5)

comment:1 Changed 8 years ago by nickm

Milestone: Tor: unspecified

It would be a good idea to come up with some clever ideas here, but right now I don't think we know the right estimators for how much to downgrade your bandwidth estimate in order to be able to handle cpuworker load.

I guess we could report how many CREATE requests we've gotten vs how quickly we're handling them, but I don't know how to infer anything useful from that. More analysis needed!

comment:2 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:3 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:4 Changed 3 years ago by nickm

Keywords: needs-design added
Severity: Normal

comment:5 Changed 2 years ago by tom

I suddenly got this error message also, on a relay I had running just fine for years. A pointer to debugging information or how to investigate this would definitely be helpful.

Note: See TracTickets for help on using tickets.