Re: [tor-relays] assign_to_cpuworker failed. Ignoring.
> On 19 Oct. 2016, at 16:46, Felix wrote: > > Thanks for picking up. > > > It would help us to know if it's just FreeBSD, or just LibreSSL. > It's both LibreSSL on FreeBSD 10.1. Same setup worked fine since months > through serveral versions of Tor (2.6.x and 2.7.x) and LibreSSL (2.2.x until > today). Ok, thanks. I suspect that it's LibreSSL, because my FreeBSD/OpenSSL and Linux/OpenSSL boxes don't have that issue in their logs. Tim > > > Maybe mention the bug number on tor-talk, so that poster can provide > more details? > Might be. > > -- > Felix > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org -- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] assign_to_cpuworker failed. Ignoring.
Thanks for picking up. > It would help us to know if it's just FreeBSD, or just LibreSSL. It's both LibreSSL on FreeBSD 10.1. Same setup worked fine since months through serveral versions of Tor (2.6.x and 2.7.x) and LibreSSL (2.2.x until today). > Maybe mention the bug number on tor-talk, so that poster can provide more details? Might be. -- Felix ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] assign_to_cpuworker failed. Ignoring.
> On 19 Oct. 2016, at 16:25, Felix wrote: > > Hi everybody > > May be someone can help with this warning: > > The security update (Tor v0.2.8.9 running on FreeBSD with Libevent > 2.0.22-stable, OpenSSL LibreSSL 2.4.3 and Zlib 1.2.8.) shows the following > log entry each hour: > > Oct 19 02:51:07.000 [warn] Your system clock just jumped 136 seconds forward; > assuming established circuits no longer work. > Oct 19 02:51:07.000 [warn] assign_to_cpuworker failed. Ignoring. > ... > Oct 19 02:51:07.000 [warn] assign_to_cpuworker failed. Ignoring. > Oct 19 02:51:15.000 [notice] Tor has successfully opened a circuit. Looks > like client functionality is working. > ... > Oct 19 03:51:10.000 [warn] Your system clock just jumped 138 seconds forward; > assuming established circuits no longer work. > Oct 19 03:51:11.000 [warn] assign_to_cpuworker failed. Ignoring. > ... > Oct 19 04:50:37.000 [warn] Your system clock just jumped 105 seconds forward; > assuming established circuits no longer work. > Oct 19 04:50:37.000 [warn] assign_to_cpuworker failed. Ignoring. > ... > Oct 19 05:51:14.000 [warn] Your system clock just jumped 142 seconds forward; > assuming established circuits no longer work. > Oct 19 05:51:15.000 [warn] assign_to_cpuworker failed. Ignoring. > ... > > The warning first appeared on 2.8.7 after update on September 13th (Tor > v0.2.8.7 running on FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL > 2.4.2 and Zlib 1.2.8.). That time I switched back (Tor v0.2.7.6 running on > FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.2 and Zlib 1.2.8.) > and the warning disappeared. > > What can I do? > > The warning is reproted in tor-talk: > https:// lists.torproject.org/pipermail/tor-talk/2016-October/042425.html Thanks for reporting this issue - you could open a bug on our bug tracker under Core Tor/Tor: https://trac.torproject.org/projects/tor/newticket It would help us to know if it's just FreeBSD, or just LibreSSL. Maybe mention the bug number on tor-talk, so that poster can provide more details? Tim > > -- > Best regards, Felix > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org -- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] assign_to_cpuworker failed. Ignoring.
Hi everybody May be someone can help with this warning: The security update (Tor v0.2.8.9 running on FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.3 and Zlib 1.2.8.) shows the following log entry each hour: Oct 19 02:51:07.000 [warn] Your system clock just jumped 136 seconds forward; assuming established circuits no longer work. Oct 19 02:51:07.000 [warn] assign_to_cpuworker failed. Ignoring. ... Oct 19 02:51:07.000 [warn] assign_to_cpuworker failed. Ignoring. Oct 19 02:51:15.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. ... Oct 19 03:51:10.000 [warn] Your system clock just jumped 138 seconds forward; assuming established circuits no longer work. Oct 19 03:51:11.000 [warn] assign_to_cpuworker failed. Ignoring. ... Oct 19 04:50:37.000 [warn] Your system clock just jumped 105 seconds forward; assuming established circuits no longer work. Oct 19 04:50:37.000 [warn] assign_to_cpuworker failed. Ignoring. ... Oct 19 05:51:14.000 [warn] Your system clock just jumped 142 seconds forward; assuming established circuits no longer work. Oct 19 05:51:15.000 [warn] assign_to_cpuworker failed. Ignoring. ... The warning first appeared on 2.8.7 after update on September 13th (Tor v0.2.8.7 running on FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.2 and Zlib 1.2.8.). That time I switched back (Tor v0.2.7.6 running on FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.2 and Zlib 1.2.8.) and the warning disappeared. What can I do? The warning is reproted in tor-talk: https:// lists.torproject.org/pipermail/tor-talk/2016-October/042425.html -- Best regards, Felix ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] You dont love me anymore :(
Was it "Buttle" or "Tuttle", right now? ;-) On 18.10.2016 20:39, Tristan wrote: > Like David said, they just had the wrong IP, and it happened to be > yours. In a world where computers outnumber people, even a single > incorrect digit can have unintended side effects. > > Glad you got it fixed so quickly! > ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] You dont love me anymore :(
Like David said, they just had the wrong IP, and it happened to be yours.
In a world where computers outnumber people, even a single incorrect digit
can have unintended side effects.
Glad you got it fixed so quickly!
On Oct 18, 2016 1:36 PM, "Markus Koch" wrote:
Just solved but thank you very much for helping me out. It was
confusing without end because this server was up for 10 months and
high traffic.
Markus
2016-10-18 20:30 GMT+02:00 Tristan :
> According to this page:
> https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays
>
> Looks like you need to get in touch work bad-rel...@lists.torproject.org
>
> What's strange is that the bad relay team should have contacted you before
> making a decision.
>
>
> On Oct 18, 2016 1:23 PM, "Markus Koch" wrote:
>>
>> Thank you very much. How do I dispute this?
>>
>>
>> 2016-10-18 20:20 GMT+02:00 Tristan :
>> > I don't know why or how, but you've got the BadExit flag from moria1:
>> > https://consensus-health.torproject.org/consensus-health.html
>> >
>> >
>> > On Oct 18, 2016 1:16 PM, "Markus Koch"
>> > wrote:
>> >>
>> >> This is a guard/middle and should be good ...
>> >>
>> >>
>> >>
>> >> https://atlas.torproject.org/#details/B771AA877687F88E6F1CA5354756DF
6C8A7B6B24
>> >>
>> >> and I have never ever seen this before.
>> >>
>> >> Markus
>> >>
>> >>
>> >> 2016-10-18 20:13 GMT+02:00 Tristan :
>> >> > I've seen 404s from time to time, but this is new. Did you get a bad
>> >> > relay
>> >> > flag somehow???
>> >> >
>> >> >
>> >> > On Oct 18, 2016 1:12 PM, "Markus Koch"
>> >> > wrote:
>> >> >>
>> >> >> 20:08:18 [WARN] Received http status code 404 ("Not found") from
>> >> >> server '86.59.21.38:80' while fetching
>> >> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
>> >> >>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> >> >> 20:06:18 [WARN] Received http status code 404 ("Not found") from
>> >> >> server '194.109.206.212:80' while fetching
>> >> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
>> >> >>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> >> this range.") response from dirserver '171.25.193.9:443'. Please
>> >> >> correct.
>> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> >> this range.") response from dirserver '154.35.175.225:80'. Please
>> >> >> correct.
>> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> >> this range.") response from dirserver '131.188.40.189:80'. Please
>> >> >> correct.
>> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> >> this range.") response from dirserver '86.59.21.38:80'. Please
>> >> >> correct.
>> >> >>
>> >> >> This is my niftypika server. This is animal abuse! Seriously, WTF
is
>> >> >> going wrong?
>> >> >>
>> >> >> Markus
>> >> >> ___
>> >> >> 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
>> >> >
>> >> ___
>> >> 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
>> >
>> ___
>> 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
>
___
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] You dont love me anymore :(
Just solved but thank you very much for helping me out. It was
confusing without end because this server was up for 10 months and
high traffic.
Markus
2016-10-18 20:30 GMT+02:00 Tristan :
> According to this page:
> https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays
>
> Looks like you need to get in touch work bad-rel...@lists.torproject.org
>
> What's strange is that the bad relay team should have contacted you before
> making a decision.
>
>
> On Oct 18, 2016 1:23 PM, "Markus Koch" wrote:
>>
>> Thank you very much. How do I dispute this?
>>
>>
>> 2016-10-18 20:20 GMT+02:00 Tristan :
>> > I don't know why or how, but you've got the BadExit flag from moria1:
>> > https://consensus-health.torproject.org/consensus-health.html
>> >
>> >
>> > On Oct 18, 2016 1:16 PM, "Markus Koch"
>> > wrote:
>> >>
>> >> This is a guard/middle and should be good ...
>> >>
>> >>
>> >>
>> >> https://atlas.torproject.org/#details/B771AA877687F88E6F1CA5354756DF6C8A7B6B24
>> >>
>> >> and I have never ever seen this before.
>> >>
>> >> Markus
>> >>
>> >>
>> >> 2016-10-18 20:13 GMT+02:00 Tristan :
>> >> > I've seen 404s from time to time, but this is new. Did you get a bad
>> >> > relay
>> >> > flag somehow???
>> >> >
>> >> >
>> >> > On Oct 18, 2016 1:12 PM, "Markus Koch"
>> >> > wrote:
>> >> >>
>> >> >> 20:08:18 [WARN] Received http status code 404 ("Not found") from
>> >> >> server '86.59.21.38:80' while fetching
>> >> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
>> >> >>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> >> >> 20:06:18 [WARN] Received http status code 404 ("Not found") from
>> >> >> server '194.109.206.212:80' while fetching
>> >> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
>> >> >>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> >> this range.") response from dirserver '171.25.193.9:443'. Please
>> >> >> correct.
>> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> >> this range.") response from dirserver '154.35.175.225:80'. Please
>> >> >> correct.
>> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> >> this range.") response from dirserver '131.188.40.189:80'. Please
>> >> >> correct.
>> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> >> this range.") response from dirserver '86.59.21.38:80'. Please
>> >> >> correct.
>> >> >>
>> >> >> This is my niftypika server. This is animal abuse! Seriously, WTF is
>> >> >> going wrong?
>> >> >>
>> >> >> Markus
>> >> >> ___
>> >> >> 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
>> >> >
>> >> ___
>> >> 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
>> >
>> ___
>> 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
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] You dont love me anymore :(
For this animal abuse I demand a pika and t-shirt from you. Its not
fair at all that pikas died out in europe 25 million years ago and you
guys in america still have them :/
Ill show myself out
Markus
ps: thx for fixing it
2016-10-18 20:28 GMT+02:00 David Goulet :
> On 18 Oct (20:11:45), Markus Koch wrote:
>> 20:08:18 [WARN] Received http status code 404 ("Not found") from
>> server '86.59.21.38:80' while fetching
>> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
>>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> 20:06:18 [WARN] Received http status code 404 ("Not found") from
>> server '194.109.206.212:80' while fetching
>> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
>>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> this range.") response from dirserver '171.25.193.9:443'. Please
>> correct.
>> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> this range.") response from dirserver '154.35.175.225:80'. Please
>> correct.
>> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> this range.") response from dirserver '131.188.40.189:80'. Please
>> correct.
>> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> this range.") response from dirserver '86.59.21.38:80'. Please
>> correct.
>>
>> This is my niftypika server. This is animal abuse! Seriously, WTF is
>> going wrong?
>
> Hi!
>
> It turns out that our last change to the dirauth configuration to reject newly
> discovered malicious relays had the _wrong_ IPs for the relay fingerprints...
> and you relay IP was a victim of this :S ...
>
> My apologize! I'm currently working on fixing this, you should be back in the
> consensus once authorities update from the mistake.
>
> Again, sorry!
> David
>
>>
>> Markus
>> ___
>> 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
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] You dont love me anymore :(
According to this page:
https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays
Looks like you need to get in touch work bad-rel...@lists.torproject.org
What's strange is that the bad relay team should have contacted you before
making a decision.
On Oct 18, 2016 1:23 PM, "Markus Koch" wrote:
> Thank you very much. How do I dispute this?
>
>
> 2016-10-18 20:20 GMT+02:00 Tristan :
> > I don't know why or how, but you've got the BadExit flag from moria1:
> > https://consensus-health.torproject.org/consensus-health.html
> >
> >
> > On Oct 18, 2016 1:16 PM, "Markus Koch"
> wrote:
> >>
> >> This is a guard/middle and should be good ...
> >>
> >>
> >> https://atlas.torproject.org/#details/B771AA877687F88E6F1CA5354756DF
> 6C8A7B6B24
> >>
> >> and I have never ever seen this before.
> >>
> >> Markus
> >>
> >>
> >> 2016-10-18 20:13 GMT+02:00 Tristan :
> >> > I've seen 404s from time to time, but this is new. Did you get a bad
> >> > relay
> >> > flag somehow???
> >> >
> >> >
> >> > On Oct 18, 2016 1:12 PM, "Markus Koch"
> >> > wrote:
> >> >>
> >> >> 20:08:18 [WARN] Received http status code 404 ("Not found") from
> >> >> server '86.59.21.38:80' while fetching
> >> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
> >> >>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> >> >> 20:06:18 [WARN] Received http status code 404 ("Not found") from
> >> >> server '194.109.206.212:80' while fetching
> >> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
> >> >>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> >> >> this range.") response from dirserver '171.25.193.9:443'. Please
> >> >> correct.
> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> >> >> this range.") response from dirserver '154.35.175.225:80'. Please
> >> >> correct.
> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> >> >> this range.") response from dirserver '131.188.40.189:80'. Please
> >> >> correct.
> >> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> >> >> this range.") response from dirserver '86.59.21.38:80'. Please
> >> >> correct.
> >> >>
> >> >> This is my niftypika server. This is animal abuse! Seriously, WTF is
> >> >> going wrong?
> >> >>
> >> >> Markus
> >> >> ___
> >> >> 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
> >> >
> >> ___
> >> 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
> >
> ___
> 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] You dont love me anymore :(
It's an error being corrected, turn it back on and recheck everything in a few hours. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] You dont love me anymore :(
On 18 Oct (20:11:45), Markus Koch wrote:
> 20:08:18 [WARN] Received http status code 404 ("Not found") from
> server '86.59.21.38:80' while fetching
> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> 20:06:18 [WARN] Received http status code 404 ("Not found") from
> server '194.109.206.212:80' while fetching
> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '171.25.193.9:443'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '154.35.175.225:80'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '131.188.40.189:80'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '86.59.21.38:80'. Please
> correct.
>
> This is my niftypika server. This is animal abuse! Seriously, WTF is
> going wrong?
Hi!
It turns out that our last change to the dirauth configuration to reject newly
discovered malicious relays had the _wrong_ IPs for the relay fingerprints...
and you relay IP was a victim of this :S ...
My apologize! I'm currently working on fixing this, you should be back in the
consensus once authorities update from the mistake.
Again, sorry!
David
>
> Markus
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] You dont love me anymore :(
Thank you very much. How do I dispute this?
2016-10-18 20:20 GMT+02:00 Tristan :
> I don't know why or how, but you've got the BadExit flag from moria1:
> https://consensus-health.torproject.org/consensus-health.html
>
>
> On Oct 18, 2016 1:16 PM, "Markus Koch" wrote:
>>
>> This is a guard/middle and should be good ...
>>
>>
>> https://atlas.torproject.org/#details/B771AA877687F88E6F1CA5354756DF6C8A7B6B24
>>
>> and I have never ever seen this before.
>>
>> Markus
>>
>>
>> 2016-10-18 20:13 GMT+02:00 Tristan :
>> > I've seen 404s from time to time, but this is new. Did you get a bad
>> > relay
>> > flag somehow???
>> >
>> >
>> > On Oct 18, 2016 1:12 PM, "Markus Koch"
>> > wrote:
>> >>
>> >> 20:08:18 [WARN] Received http status code 404 ("Not found") from
>> >> server '86.59.21.38:80' while fetching
>> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
>> >>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> >> 20:06:18 [WARN] Received http status code 404 ("Not found") from
>> >> server '194.109.206.212:80' while fetching
>> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
>> >>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> this range.") response from dirserver '171.25.193.9:443'. Please
>> >> correct.
>> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> this range.") response from dirserver '154.35.175.225:80'. Please
>> >> correct.
>> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> this range.") response from dirserver '131.188.40.189:80'. Please
>> >> correct.
>> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> >> this range.") response from dirserver '86.59.21.38:80'. Please
>> >> correct.
>> >>
>> >> This is my niftypika server. This is animal abuse! Seriously, WTF is
>> >> going wrong?
>> >>
>> >> Markus
>> >> ___
>> >> 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
>> >
>> ___
>> 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
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] You dont love me anymore :(
I don't know why or how, but you've got the BadExit flag from moria1:
https://consensus-health.torproject.org/consensus-health.html
On Oct 18, 2016 1:16 PM, "Markus Koch" wrote:
> This is a guard/middle and should be good ...
>
> https://atlas.torproject.org/#details/B771AA877687F88E6F1CA5354756DF
> 6C8A7B6B24
>
> and I have never ever seen this before.
>
> Markus
>
>
> 2016-10-18 20:13 GMT+02:00 Tristan :
> > I've seen 404s from time to time, but this is new. Did you get a bad
> relay
> > flag somehow???
> >
> >
> > On Oct 18, 2016 1:12 PM, "Markus Koch"
> wrote:
> >>
> >> 20:08:18 [WARN] Received http status code 404 ("Not found") from
> >> server '86.59.21.38:80' while fetching
> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
> >>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> >> 20:06:18 [WARN] Received http status code 404 ("Not found") from
> >> server '194.109.206.212:80' while fetching
> >> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
> >>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> >> this range.") response from dirserver '171.25.193.9:443'. Please
> >> correct.
> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> >> this range.") response from dirserver '154.35.175.225:80'. Please
> >> correct.
> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> >> this range.") response from dirserver '131.188.40.189:80'. Please
> >> correct.
> >> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> >> this range.") response from dirserver '86.59.21.38:80'. Please
> >> correct.
> >>
> >> This is my niftypika server. This is animal abuse! Seriously, WTF is
> >> going wrong?
> >>
> >> Markus
> >> ___
> >> 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
> >
> ___
> 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] You dont love me anymore :(
This is a guard/middle and should be good ...
https://atlas.torproject.org/#details/B771AA877687F88E6F1CA5354756DF6C8A7B6B24
and I have never ever seen this before.
Markus
2016-10-18 20:13 GMT+02:00 Tristan :
> I've seen 404s from time to time, but this is new. Did you get a bad relay
> flag somehow???
>
>
> On Oct 18, 2016 1:12 PM, "Markus Koch" wrote:
>>
>> 20:08:18 [WARN] Received http status code 404 ("Not found") from
>> server '86.59.21.38:80' while fetching
>> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
>>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> 20:06:18 [WARN] Received http status code 404 ("Not found") from
>> server '194.109.206.212:80' while fetching
>> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
>>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
>> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> this range.") response from dirserver '171.25.193.9:443'. Please
>> correct.
>> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> this range.") response from dirserver '154.35.175.225:80'. Please
>> correct.
>> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> this range.") response from dirserver '131.188.40.189:80'. Please
>> correct.
>> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
>> this range.") response from dirserver '86.59.21.38:80'. Please
>> correct.
>>
>> This is my niftypika server. This is animal abuse! Seriously, WTF is
>> going wrong?
>>
>> Markus
>> ___
>> 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
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] You dont love me anymore :(
I've seen 404s from time to time, but this is new. Did you get a bad relay
flag somehow???
On Oct 18, 2016 1:12 PM, "Markus Koch" wrote:
> 20:08:18 [WARN] Received http status code 404 ("Not found") from
> server '86.59.21.38:80' while fetching
> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
>8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> 20:06:18 [WARN] Received http status code 404 ("Not found") from
> server '194.109.206.212:80' while fetching
> "/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
>C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '171.25.193.9:443'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '154.35.175.225:80'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '131.188.40.189:80'. Please
> correct.
> 20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
> this range.") response from dirserver '86.59.21.38:80'. Please
> correct.
>
> This is my niftypika server. This is animal abuse! Seriously, WTF is
> going wrong?
>
> Markus
> ___
> 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
[tor-relays] You dont love me anymore :(
20:08:18 [WARN] Received http status code 404 ("Not found") from
server '86.59.21.38:80' while fetching
"/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401C02A-
8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
20:06:18 [WARN] Received http status code 404 ("Not found") from
server '194.109.206.212:80' while fetching
"/tor/keys/fp-sk/14C131DFC5C6F93646BE72FA1401-
C02A8DF2E8B4-692049A2E7868BE9933107A39B1CE0C7CBF1BF65".
20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
this range.") response from dirserver '171.25.193.9:443'. Please
correct.
20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
this range.") response from dirserver '154.35.175.225:80'. Please
correct.
20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
this range.") response from dirserver '131.188.40.189:80'. Please
correct.
20:05:18 [WARN] http status 400 ("Authdir is rejecting routers in
this range.") response from dirserver '86.59.21.38:80'. Please
correct.
This is my niftypika server. This is animal abuse! Seriously, WTF is
going wrong?
Markus
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Why do 40% of Tor exits uses 8.8.8.8 for DNS resolving ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/17/2016 07:40 PM, Toralf Förster wrote: > but from the mentioned PDF I got the impression to just use the ISP > nameservers + a local cache - which I'm trying now. Which was not the best idea: $ dig www.heise.de +trace ; <<>> DiG 9.10.4-P3 <<>> www.heise.de +trace ;; global options: +cmd ;; connection timed out; no servers could be reached Adding external DNS name server solved that. - -- Toralf PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7 -BEGIN PGP SIGNATURE- iHYEAREIAB4FAlgGPtcXHHRvcmFsZi5mb2Vyc3RlckBnbXguZGUACgkQxOrN3gB2 6U4PTgD7B/4JkwIqnwmcLNe6k/psZdZDfxpSe7dIooer+ySH6FoBAITyxUdiDmTk lHO7gm7XWyISde0B73NXHLfJlihKquPE =T+TF -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] DNS resolving -problem?
On Tue, 18 Oct 2016 11:58:38 +0200 pa011 wrote: > apt-get install dnsmasq > > /etc/resolv.conf > nameserver 127.0.0.1 > > /etc/dnsmasq.conf > server=216.87.84.211 #open.nic us > server=84.200.69.80 #dns.watch us > server=84.200.70.40 #dns.watch us > server=194.150.168.168 > server=62.113.203.99 > server=188.165.200.156 > server=5.9.49.12 > server=193.183.98.154 > server=46.101.89.89 > cache-size=1 > dnssec > dnssec-check-unsigned > > > etc/init.d/dnsmasq restart Sooo, did you actually check you can resolve DNS on the host after that? Even a trivial "ping google.com", or more proper "nslookup torproject.org". > conf-file=usr/share/dnsmasq-base/trust-anchors.conf This appears like it might need a leading "/" before "usr". -- With respect, Roman ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] DNS resolving -problem?
Got problems overnight. On all servers traffic died down and looks like below - what went wrong please? Here is what I did: apt-get install dnsmasq /etc/resolv.conf nameserver 127.0.0.1 /etc/dnsmasq.conf server=216.87.84.211 #open.nic us server=84.200.69.80 #dns.watch us server=84.200.70.40 #dns.watch us server=194.150.168.168 server=62.113.203.99 server=188.165.200.156 server=5.9.49.12 server=193.183.98.154 server=46.101.89.89 cache-size=1 conf-file=usr/share/dnsmasq-base/trust-anchors.conf dnssec dnssec-check-unsigned etc/init.d/dnsmasq restart vnstat -h eth0 ^ r | rtrt rt | rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt r rt rt rtrtrt | rt rt rt rt rt rt rt rt r r r rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt -+---> | 12 13 14 15 16 17 18 19 20 21 22 23 00 01 02 03 04 05 06 07 08 09 10 11 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
