9

The node in question is the following:

https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2600

The node has been restarted recently in hope of that fixing it, alas to no avail. As you can see the node itself still has all the proper flags, stable, valid, exit, fast etc.

I have not changed anything in my torrc file. Any kind of input would be helpful. Also the servers bandwidth is dedicated.

  • 1
    Nothing comes to mind, except the possibility the the bandwidth authorities had failed to measure the consensus weight properly, or your node, somehow, reported a value of 0 at some time. – Linostar Feb 2 '15 at 18:05
1

Looking at the votes for the individual directory authorities, it appears that gabelmoo and longclaw don't have Measured lines for your relay. moria1 and tor26 measure your node just fine. I worry that there's nothing you can do on your end to fix it, as it is a problem with the bandwidth authorities measurement code. I'm gabelmoo's operator and I'll try to fix it, but I have no idea about the inner workings of the bwauth code. Hopefully you'll be measured again within a day.

| improve this answer | |
  • just out of curiosity, how would you try to fix it? – schokomilch Mar 9 '15 at 19:53
  • I removed the cache files ad restarted the bwauth processes – Sebastian Mar 9 '15 at 22:04
  • I see, did you notice a difference already? – schokomilch Mar 10 '15 at 14:25
  • no :( Keeping an eye out – Sebastian Mar 10 '15 at 18:28
  • I've recently changed my exit node back to a regular relay node and within minutes its consensus started climbing again. Currently at 7710 -> atlas.torproject.org/#details/… – schokomilch Apr 29 '15 at 21:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.