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

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)

[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

[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,

[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

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 >

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

[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

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

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 ... > >

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: >

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 >

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"

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 :

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

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

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

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