Thanks for the feedback, however, I now have a new problem. I rebooted the server my TOR Node lives on and I've got a non-system disk error so I think my partition table got corrupted.
If I can access the file system, is there any way to get what I need of the drive to retain my fingerprint? If I can't access the file system is there any way to get what I need from "somewhere" to retain my fingerprint? Matt Westfall President & CIO ECAN Solutions, Inc. Everything Computers and Networks 804.592.1672 http://ecansol.com On Sun, May 26, 2019 at 2:58 AM <[email protected]> wrote: > Dear Matt, > > I see you started your relay 22 days ago. I started one (Aramis67) within > a day of yours, so they both should still be getting adjusted. Have you > read about the lifecycle of a new relay?: > https://blog.torproject.org/comment/54651 > As your new relay gets better known, I think your consensus number will go > up, but while I have used RelayBandwidthRate to gradually cap my home relay > to about 1TB a month, I don't think you can force a new relay up faster > with bigger limits. > > I am running Aramis67 with no RelayBandwidthRate in the config: > 15 ControlSocket /run/tor/control > 16 ControlSocketsGroupWritable 1 > 17 CookieAuthentication 1 > 18 CookieAuthFile /run/tor/control.authcookie > 19 CookieAuthFileGroupReadable 1 > 26 SOCKSPort 0 > 64 ControlPort 9051 > 91 ORPort 9001 > 92 ORPort [2a00:1dc0:caff:126::a5c9]:9001 > 187 ExitRelay 0 > ----------------- > My consensus weight is currently 5730, so a good deal behind 8400, though > my current connections numbers are about 1800 and 2000 in and out. Much of > the consensus weight seems to be affected by how close you are/good > connection you have to the authentication servers. > > I expect that our relays will both generally go in the same direction. > > --Torix > > > Sent with ProtonMail <https://protonmail.com> Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Friday, May 24, 2019 3:13 PM, Matt Westfall <[email protected]> > wrote: > > My tor node: > https://metrics.torproject.org/rs.html#details/B1B10104EB72A1FBBF6687B05F1915D87D00DBDE > > Doesn't ever go up above 8800 or so. > > One thing I notice in Nyx is that my connections never go above about 2000 > in and out connections. > > I have advertised bandwidth of just shy of a gigabit in my config. I > understand now that the "advertised bandwidth" is calculated based on > observed traffic through the node, which while more reliable and avoids > abuse, seems to be counter productive to a degree. > > Ultimately what do I need to do to get more traffic through my node? Cause > I have a 2Gbps fiber sitting here basically doing nothing so I was giving > 1Gbps to tor :) > > Config -------------- > RunAsDaemon 1 > ControlPort 9051 > ORPort 9001 > ORPORT [2001:559:c290::fffb]:9001 > RelayBandwidthRate 45 MB # Throttle traffic to 100KB/s (800Kbps) > RelayBandwidthBurst 50 MB # But allow bursts up to 200KB/s (1600Kbps) > DirPort 9030 # > ExitPolicy reject *:* # no exits allowed > ExitPolicy reject6 *:* > > Any suggestions appreciated. > > > Matt Westfall > President & CIO > ECAN Solutions, Inc. > Everything Computers and Networks > 804.592.1672 > > > _______________________________________________ > tor-relays mailing list > [email protected] > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >
_______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
