[tor-relays] Tor relay struggling with circuit creation (CPU Limit)
Hi Tor relay community, I have recently made a new tor relay, and all is going well however I use NYX to mointor it and over the last day it has been giving the warning message seen below in the nyx mointor, the relay had been running fine for it's first 4 days of life but now shows this message for nealry 30 hours now (scrolling through logs) Also the nyx mointor shows a CPU usage of 80-90% so I know this is the limiting factor and have no issue with it as this server is just free VPS that I am donating so ideally would like it to pump out as much data in/out as possible, but my question is, Do I need to change my torrc to fix this error or will the tor network realize overtime how much traffic is best for this node? Useful information: https://metrics.torproject.org/rs.html#details/448E2528A4AC58A7531EC950AAF0F4A083C7E627: GANDI24325second the relay in quesiton, with this website showing everything as fine Family: https://metrics.torproject.org/rs.html#search/family:BC77562EF192F0A580F54D1A5182EC6EC4B3899F: the other two relays are working fine Contact info: GANDI24325_TOR [at] protonmail (dot) com Addtional info: If I haven't provided enough infomation/if you want the torrc I can help Thanks in advance for any help Warning messages: 09:10:10 [WARN] 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. │ [2012 similar message(s) suppressed in last 120 seconds] │ 09:09:09 [WARN] 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. │ [1467 similar message(s) suppressed in last 60 seconds] │ 09:08:08 [WARN] 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. │ [628 similar message(s) suppressed in last 60 seconds] │ 09:07:08 [WARN] 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. │ [518 similar message(s) suppressed in last 120 seconds] │ 09:05:57 [WARN] 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. │ [10092 similar message(s) suppressed in last 2820 seconds] │ 08:19:05 [WARN] 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. │ [13039 similar message(s) suppressed in last 120 seconds] │ 08:18:04 [WARN] 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. │ [11034 similar message(s) suppressed in last 60 seconds] │ 08:17:04 [WARN] 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. ─┘ [7335 similar message(s) suppressed in last 60 seconds]___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] relayor v22.0.0-rc is released
Hi and thanks. Now I try to up a guard relay. I'm a noob but I may try to do those things. El lun, 3 ene 2022 a la(s) 20:09, nusenu (nusenu-li...@riseup.net) escribió: > Hi, > > relayor v22.0.0-rc is released. > > relayor is an ansible role that helps you with running tor relays with > minimal effort (automate everything). > > > https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor-relay-operator > > Changes since relayor v21.2.0-rc: > > * MetricsPort support improvements: > * generate nginx reverse server config for remote prometheus scraping > on the relay (we do not install nginx) > * generate htpasswd file for HTTP basic auth of MetricsPort on the > relay > * debian/ubuntu: support new alpha repos (branch name is no longer > included in the repo name). > * FreeBSD 12.3 is supported > > > kind regards, > nusenu > > -- > https://nusenu.github.io > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bridge showing offline
This has now happened again, on the same bridge, showing off-line to the metrics, but the logs showing it running with activity taking place. Guess I'll keep an eye on the metrics to see if it pops back to available. I'm wondering how often this might be happening, because I don't check the metrics that often and the instance documented below didn't change the Uptime or Last Restart to indicate anything had happened. So unless I notice while it's in this state, like now, I have no way of knowing if it happens regularly or not. Cheers. On 10/14/2021 12:11 PM, Eddie wrote: On 10/14/2021 2:44 AM, Bleedangel Tor Admin wrote: You are running 0.4.5.8, maybe updating to a newer version of tor will help? Sent from ProtonMail for iOS On Thu, Oct 14, 2021 at 03:02, Georg Koppen wrote: Eddie: > Looking at tor metrics, one of my bridges is showing as off-line: > B080140DC1BAB5B86D1CE5A4CA2EF64F20282440 > > However, the log isn't showing any issues: > > Oct 14 00:00:28.000 [notice] Tor 0.4.5.8 opening new log file. > Oct 14 00:00:28.000 [notice] Configured hibernation. This interval > began at 2021-10-14 00:00:00; the scheduled wake-up time was 2021-10-14 > 00:00:00; we expect to exhaust our quota for this interval around > 2021-10-15 00:00:00; the next interval begins at 2021-10-15 00:00:00 > (all times local) > Oct 14 01:49:40.000 [notice] Heartbeat: Tor's uptime is 124 days 6:00 > hours, with 0 circuits open. I've sent 907.23 GB and received 922.28 GB. > I've received 63052 connections on IPv4 and 8375 on IPv6. I've made > 512684 connections with IPv4 and 100974 with IPv6. > Oct 14 01:49:40.000 [notice] While not bootstrapping, fetched this many > bytes: 1801791624 (server descriptor fetch); 175792 (server descriptor > upload); 221750347 (consensus network-status fetch); 10974 (authority > cert fetch); 19905655 (microdescriptor fetch) > Oct 14 01:49:40.000 [notice] Heartbeat: Accounting enabled. Sent: 140.52 > MB, Received: 140.69 MB, Used: 281.21 MB / 200.00 GB, Rule: sum. The > current accounting interval ends on 2021-10-15 00:00:00, in 22:10 hours. > Oct 14 01:49:40.000 [notice] Heartbeat: In the last 6 hours, I have seen > 14 unique clients. > > Initially I thought of a previous issue I had with IPv6 connectivity, > but don't think this is the problem here as the 2nd bridge on the same > server is showing on-line. Also an IPv6 port scan shows the ports for > both bridges as accessible. > > Ideas ?? I wonder whether that is another instance https://gitlab.torproject.org/tpo/core/tor/-/issues/40424. Hard to tell, though. Does that issue happen regularly? Georg ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays I didn't touch anything, and this morning the metrics say the bridge is running normally, with an uptime of over 125 days. Looks like it might have been a metrics issue, not the bridge itself. Cheers. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
