Re: [tor-relays] tor relay on windows 10
already found)) 16.05.2020, 17:56, "Станислав" :hello everyone again.please tell me the command to launch the second instance of tor relay on windows 10.service is already installed and one relay is running.thankС уважением,Станислав ,___tor-relays mailing listtor-relays@lists.torproject.orghttps://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] tor relay on windows 10
hello everyone again.please tell me the command to launch the second instance of tor relay on windows 10.service is already installed and one relay is running.thankС уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
as I wrote earlier, they are disconnected arbitrarily for 3-4 hours and then restored themselves, maybe it is better to remove the ports of dir? bandwidth should be enough running on four cores with 4 GB of memory speed 800/800 Mbps 14.05.2020, 22:52, "Felix" :Hi СтаниславYou have two relays running at the same IP. Your IP and relays seemvisible to the network:armik CE5ED345398CC02D573347C2F238F80B18E680EE178.140.230.147,broadband-178-140-230-147.ip.moscow.rt.ru,443,80Fast Run V2Dir Valid bw=9290Fast V2Dir ValidFast Run V2Dir ValidFast V2Dir Valid bw=10200Fast V2Dir ValidV2Dir ValidV2Dir Valid Run V2Dir ValidFast V2Dir Valid bw=7890armik1 0C0388BC552D7AC903F49390A40244FD3FFF44A2178.140.230.147,broadband-178-140-230-147.ip.moscow.rt.ru,9001,9030Fast Run V2Dir Valid bw=4650Fast Run V2Dir ValidFast Run V2Dir ValidFast Run V2Dir Valid bw=3200Fast Run V2Dir Valid!Fast Run V2Dir ValidFast Run V2Dir Valid bw=5960!Fast Run V2Dir ValidFast Run V2Dir Valid bw=6670Fast Run V2Dir Valid bw=4650 bwauth=moria1Am 14.05.2020 um 19:18 schrieb Станислав: hi, I still don’t understand why the relays constantly go offline for no apparent reasonMay-be there are indications: On 4 May 2020, at 20:51, Станислав <armik...@gmail.com armik...@gmail.com>> wrote: hi, strange but the relay constantly spontaneously goes offline after 3, 4 hours again online in the logs no errors other than this (Failing because we have 4063 connections already. Please read doc / TUNING for guidance. [over 1601 similar message (s) suppressed in last 21600 seconds)and TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies. Check SNMP counters. what it can mean? also my 2 relays go offline for a few hours once a day, then are restored.Port 80 is your DIR port.If you suffer under potential overload or not enough resources (by whatever reason) you can reduce.Run only one relay with OR port only and strict DOS settings. Then waita week if everything works. Wait an other week. If still everything isrunning well add the DIR port again and wait and wait. Add the secondrelay in the same way and finally relax DOS settings.When ever the relay(s) become unstable go one step back.This is a recommendation but there might better ways to go.Good luck! --Cheers, Felix___tor-relays mailing listtor-relays@lists.torproject.orghttps://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] (no subject)
hi, I still don’t understand why the relays constantly go offline for no apparent reason С уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (Без темы)
thanks for the link. I increased 'ulimit -n' with 1024 to 13500. see how it works. 04.05.2020, 15:29, "teor" :Hi, On 4 May 2020, at 20:51, Станислав <armik...@gmail.com> wrote: hi, strange but the relay constantly spontaneously goes offline after 3, 4 hours again online in the logs no errors other than this (Failing because we have 4063 connections already. Please read doc / TUNING for guidance. [over 1601 similar message (s) suppressed in last 21600 seconds)CE5ED345398CC02D573347C2F238F80B18E680EE Here is a link to doc/TUNING:https://github.com/torproject/tor/blob/master/doc/TUNING It says: "Most operating systems limit an amount of TCP sockets that can be used simultaneously. It is possible for a busy Tor relay to run into these limits, thus being unable to fully utilize the bandwidth resources it has at its disposal. Following system-specific tips might be helpful…" Let us know how you go with the system-specific instructions! T,___tor-relays mailing listtor-relays@lists.torproject.orghttps://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] (Без темы)
hi, strange but the relay constantly spontaneously goes offline after 3, 4 hours again online in the logs no errors other than this (Failing because we have 4063 connections already. Please read doc / TUNING for guidance. [over 1601 similar message (s) suppressed in last 21600 seconds)CE5ED345398CC02D573347C2F238F80B18E680EE С уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] (no subject)
I see. Thanks 02.05.2020, 10:38, "teor" :Hi, On 2 May 2020, at 00:07, Станислав <armik...@gmail.com> wrote: 01.05.2020, 14:20, "teor" <t...@riseup.net>:Hi, On 1 May 2020, at 20:57, Станислав <armik...@gmail.com> wrote: what could it mean May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end line May 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or generated stringWhere is it happening?Client or relay?Can you share a few more log lines?If it's a relay, maybe your connection just got cut off.Looks like a relay, and relays use unencrypted DIrPorts for directory downloads. So maybe:* the connection got cut off* the remote relay is sending corrupted data* the data was modified in transit There's nothing you need to do. T,___tor-relays mailing listtor-relays@lists.torproject.orghttps://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] (no subject)
01.05.2020, 14:20, "teor" :Hi, On 1 May 2020, at 20:57, Станислав <armik...@gmail.com> wrote: what could it mean May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end line May 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or generated stringWhere is it happening?Client or relay?Can you share a few more log lines?If it's a relay, maybe your connection just got cut off.T ,___tor-relays mailing listtor-relays@lists.torproject.orghttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relaysMay 01 13:40:13.000 [notice] Tor 0.4.2.7 opening new log file.May 01 13:40:13.986 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.May 01 13:40:13.987 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warningMay 01 13:40:13.987 [notice] Read configuration file "/etc/tor/torrc".May 01 13:40:13.993 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.May 01 13:40:13.993 [notice] Based on detected system memory, MaxMemInQueues is set to 2947 MB. You can override this by setting MaxMemInQueues by hand.May 01 13:40:13.993 [warn] MyFamily is set but ContactInfo is not configured. ContactInfo should always be set when MyFamily option is too.May 01 13:40:13.995 [notice] Opening OR listener on 0.0.0.0:443May 01 13:40:13.995 [notice] Opened OR listener on 0.0.0.0:443May 01 13:40:13.995 [notice] Opening OR listener on [2a03:e2c0:bc7::2]:443May 01 13:40:13.995 [notice] Opened OR listener on [2a03:e2c0:bc7::2]:443May 01 13:40:13.995 [notice] Opening Directory listener on 0.0.0.0:80May 01 13:40:13.995 [notice] Opened Directory listener on 0.0.0.0:80May 01 13:40:14.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.May 01 13:40:14.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.May 01 13:40:15.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.May 01 13:40:15.000 [notice] Your Tor server's identity key fingerprint is 'armik CE5ED345398CC02D573347C2F238F80B18E680EE'May 01 13:40:15.000 [notice] Bootstrapped 0% (starting): StartingMay 01 13:40:15.000 [notice] Starting with guard context "default"May 01 13:40:17.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.May 01 13:40:18.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.May 01 13:41:40.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.May 01 13:41:40.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6796, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)May 01 13:41:43.000 [notice] Bootstrapped 5% (conn): Connecting to a relayMay 01 13:41:43.000 [notice] Bootstrapped 10% (conn_done): Connected to a relayMay 01 13:41:43.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relayMay 01 13:41:43.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay doneMay 01 13:41:43.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptorsMay 01 13:41:44.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.May 01 13:41:48.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptorsMay 01 13:41:50.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptorsMay 01 13:41:51.000 [notice] Bootstrapped 65% (loading_descriptors): Loading relay descriptorsMay 01 13:41:52.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptorsMay 01 13:41:52.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuitMay 01 13:41:54.000 [notice] Bootstrapped 100% (done): DoneMay 01 13:41:54.000 [notice] Now checking whether ORPort 178.140.230.147:443 and DirPort 178.140.230.147:80 are reachable... (this may take up to 20 minutes -- look for log messages indicating succe
[tor-relays] (no subject)
what could it mean May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end lineMay 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or generated string С уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (no subject)
now.on one relay once a day constantly loads a new descriptor. CE5ED345398CC02D573347C2F238F80B18E680EE С уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] (Без темы)
TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies. Check SNMP counters.what it can mean? also my 2 relays go offline for a few hours once a day, then are restored. С уважением,Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Low bandwidth
and I have a recession0C0388BC552D7AC903F49390A40244FD3FFF44A2 01.04.2020, 19:34, "William Pate" :I'm running into the same problem -- seeing significant drop off in bandwidth advertised.Relay family: 7AC93EC4B3725ABF7E09A903BC4A5C5C1E36517FWilliam Patewillp...@pm.me512-947-3311inadequate.net‐‐‐ Original Message ‐‐‐On Tuesday, March 31, 2020 5:51 PM, teor <t...@riseup.net> wrote: Hi, I'm cc'ing the network health team, so they are aware of this issue. > > > On 30 Mar 2020, at 23:00, ha3ks ha...@protonmail.com wrote: > > > my relay dropped nearly all it’s bandwidth about a month ago, checking over it I can see 3 of the dir auths have given it a low consensus weighting, would that cause low bandwidth numbers? > > > I checked my ufw in Ubuntu and it’s allowing 443 and 80. > > > > Date: Tue, 31 Mar 2020 09:44:41 +1000 > > From: teor t...@riseup.net > > I have seen similar reports from a few other relay operators. > > What is your relay fingerprint? > > Have you followed the troubleshooting instructions here: > > https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow > > On 31 Mar 2020, at 20:46, ha3ks ha...@protonmail.com wrote: > The fingerprint is - 6E1DA4C0B0C05FB721B42329C47A20DA22908AEB > I have followed some of this yes, though its a little over my head I have opened a ticket in sbws to follow up this issue: sbws measures some relays 100x lower than Torflow https://trac.torproject.org/projects/tor/ticket/33775 It could be related to these other issues: sbws does not detect changes in descriptor bandwidth values https://trac.torproject.org/projects/tor/ticket/30733 sbws bandwidth scans should require a minimum exit bandwidth https://trac.torproject.org/projects/tor/ticket/33009 T tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays___tor-relays mailing listtor-relays@lists.torproject.orghttps://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] tor relay
13.03.2020, 14:55, "teor" :Hi, Post the entire file without shortening or removing any line. If it complainsabout parse error, there must be something wrong in it, but you don't noticeor don't think it is wrong. People on the mailing list can check if it's ok,but again only if you post the entire file (copy-paste or attach). С уважением,Станислав There could be a few things wrong here. Try setting ServerDNSResolvConfFile to /dev/null,or a world-readable empty file, and see if your problem goes away. If it does, here are some common issues to check: What are the permissions on /etc.resolv.conf ?Can the tor user read the file? Is the file a symlink?(macOS does this, not sure if some Linux distros do as well) Are there any hidden characters in the file?Does it use Unix newlines? Tor uses libevent's evdns_base_resolv_conf_parse() to parse the file.https://libevent.org/doc/dns_8h.html#a7e3a053e25ae7c045944a5db0947babb How old is your version of libevent? T -- teor-- ,___tor-relays mailing listtor-relays@lists.torproject.orghttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays С уважением,Станислав What are the permissions on /etc.resolv.conf ?read and write Is the file a symlink?I do not know Are there any hidden characters in the file?no Does it use Unix newlines?I do not know How old is your version of libevent?libevent 2.1.11 I deleted this file and managed to start, but such entries appeared: Mar 09 22:32:18.000 [notice] Received reload signal (hup). Reloading config and resetting internal state.Mar 09 22:32:18.000 [notice] Read configuration file "/etc/tor/torrc1".Mar 09 22:32:18.000 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.Mar 09 22:32:18.000 [warn] MyFamily is set but ContactInfo is not configured. ContactInfo should always be set when MyFamily option is too.Mar 09 22:32:18.000 [notice] Tor 0.4.2.5 opening log file.Mar 09 22:32:18.000 [warn] Unable to stat resolver configuration in '/etc/resolv.conf': No such file or directoryMar 09 22:32:18.000 [warn] Could not read your DNS config from '/etc/resolv.conf' - please investigate your DNS configuration. This is possibly a problem. Meanwhile, falling back to local DNS at 127.0.0.1.Mar 09 22:32:18.000 [warn] Unable to stat resolver configuration in '/etc/resolv.conf': No such file or directoryMar 09 22:32:18.000 [warn] Could not read your DNS config from '/etc/resolv.conf' - please investigate your DNS configuration. This is possibly a problem. Meanwhile, falling back to local DNS at 127.0.0.1. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor relay
12.03.2020, 23:36, "Sean Greenslade" : >>> What are the contents of /etc/resolv.conf ? >> >> 127.0.0.1 >> ::1 > > That's the problem. The format of resolv.conf requires the string > "nameserver" before each ip. Try something like this: > > # Up to three nameserver lines are allowed. > nameserver 127.0.0.1 > nameserver ::1 > #nameserver > > --Sean > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays С уважением, Станислав that’s exactly what it says, I simply shortened and did not write the word nameserver ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor relay
11.03.2020, 22:57, "Sean Greenslade" : > On March 9, 2020 3:55:38 AM PDT, "Станислав" wrote: >> hi.I start second instance of tor, but for some reason it stopped >> working.after updating the firmware on board pc engines apu2 >> >> Mar 09 13:48:46.000 [notice] Bootstrapped 0% (starting): Starting >> Mar 09 13:49:03.000 [notice] Starting with guard context "default" >> Mar 09 13:49:03.000 [warn] Unable to parse '/etc/resolv.conf', or no >> nameservers in '/etc/resolv.conf' (1) >> Mar 09 13:49:03.000 [warn] Couldn't set up any working nameservers. >> Network not up yet? Will try again soon. >> Mar 09 13:49:03.000 [notice] Self-testing indicates your ORPort is >> reachable from the outside. Excellent. >> Mar 09 13:49:04.000 [notice] Bootstrapped 5% (conn): Connecting to a >> relay >> Mar 09 13:49:04.000 [warn] Unable to parse '/etc/resolv.conf', or no >> nameservers in '/etc/resolv.conf' (1) >> Mar 09 13:49:04.000 [notice] Bootstrapped 10% (conn_done): Connected to >> a relay >> Mar 09 13:49:04.000 [notice] Bootstrapped 14% (handshake): Handshaking >> with a relay >> Mar 09 13:49:05.000 [notice] Bootstrapped 15% (handshake_done): >> Handshake with a relay done >> Mar 09 13:49:05.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded >> enough directory info to build circuits >> Mar 09 13:49:05.000 [notice] Bootstrapped 90% (ap_handshake_done): >> Handshake finished with a relay to build circuits >> Mar 09 13:49:05.000 [notice] Bootstrapped 95% (circuit_create): >> Establishing a Tor circuit >> Mar 09 13:49:06.000 [notice] Bootstrapped 100% (done): Done >> Mar 09 13:50:05.000 [notice] Self-testing indicates your DirPort is >> reachable from the outside. Excellent. Publishing server descriptor. >> Mar 09 13:50:08.000 [notice] Performing bandwidth self-test...done. >> Mar 09 13:51:32.000 [notice] Received reload signal (hup). Reloading >> config and resetting internal state. >> Mar 09 13:51:32.000 [notice] Read configuration file "/etc/tor/torrc1". >> Mar 09 13:51:32.000 [notice] Your ContactInfo config option is not set. >> Please consider setting it, so we can contact you if your server is >> misconfigured or something else goes wrong. >> Mar 09 13:51:32.000 [warn] MyFamily is set but ContactInfo is not >> configured. ContactInfo should always be set when MyFamily option is >> too. >> Mar 09 13:51:32.000 [notice] Tor 0.4.2.5 opening log file. >> Mar 09 13:51:32.000 [warn] Unable to parse '/etc/resolv.conf', or no >> nameservers in '/etc/resolv.conf' (1) >> Mar 09 13:51:32.000 [err] set_options(): Bug: Acting on config options >> left us in a broken state. Dying. (on Tor 0.4.2.5 ) >> Mar 09 13:51:32.000 [err] Reading config failed--see warnings above. >> For usage, try -h. >> Mar 09 13:51:32.000 [warn] Restart failed (config error?). Exiting. > > Well, these lines look like a good place to start: > >> Mar 09 13:49:03.000 [warn] Unable to parse '/etc/resolv.conf', or no >> nameservers in '/etc/resolv.conf' (1) >> Mar 09 13:49:03.000 [warn] Couldn't set up any working nameservers. Network >> not up yet? Will try again soon. > > What are the contents of /etc/resolv.conf ? > > --Sean > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays С уважением, Станислав 127.0.0.1 ::1 but the errors continue.I run of odhcpd+unbound.on a unbound works dns-over-tls in log torrc these errors.are what could be the problem? Mar 09 15:13:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 15:23:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 15:33:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] tor relay
system openwrt.I have a bunch of odhcpd+unbound.on a unbound works dns-over-tls in end face log torrc these errors.are what could be the problem? the unbound is not configured correctly. Mar 09 15:13:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 15:23:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 15:33:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 15:43:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 15:53:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 16:03:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 16:13:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 16:23:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 16:33:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 16:43:37.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) С уважением, Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] tor relay
hi.I start second instance of tor, but for some reason it stopped working.after updating the firmware on board pc engines apu2 Mar 09 13:48:46.000 [notice] Bootstrapped 0% (starting): Starting Mar 09 13:49:03.000 [notice] Starting with guard context "default" Mar 09 13:49:03.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 13:49:03.000 [warn] Couldn't set up any working nameservers. Network not up yet? Will try again soon. Mar 09 13:49:03.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Mar 09 13:49:04.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Mar 09 13:49:04.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 13:49:04.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Mar 09 13:49:04.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Mar 09 13:49:05.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done Mar 09 13:49:05.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Mar 09 13:49:05.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Mar 09 13:49:05.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Mar 09 13:49:06.000 [notice] Bootstrapped 100% (done): Done Mar 09 13:50:05.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Publishing server descriptor. Mar 09 13:50:08.000 [notice] Performing bandwidth self-test...done. Mar 09 13:51:32.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Mar 09 13:51:32.000 [notice] Read configuration file "/etc/tor/torrc1". Mar 09 13:51:32.000 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong. Mar 09 13:51:32.000 [warn] MyFamily is set but ContactInfo is not configured. ContactInfo should always be set when MyFamily option is too. Mar 09 13:51:32.000 [notice] Tor 0.4.2.5 opening log file. Mar 09 13:51:32.000 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (1) Mar 09 13:51:32.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.4.2.5 ) Mar 09 13:51:32.000 [err] Reading config failed--see warnings above. For usage, try -h. Mar 09 13:51:32.000 [warn] Restart failed (config error?). Exiting. С уважением, Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor relay ipv6
22.08.2019, 18:46, "Roman Mamedov" : > On Thu, 22 Aug 2019 13:07:21 + > "Matt Westfall" wrote: > >> So perhaps your ISP is wonking with tor traffic as suggested. > > We happened to meet in a Telegram group chat and after some more discussion > the cause turned out to be firewall rules on the relay machine itself. > > -- > With respect, > Roman > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays thank you all for your help.problem resolved. С уважением, Станислав ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor relay ipv6
22.08.2019, 06:57, "teor" : > Hi, > >> On 21 Aug 2019, at 23:38, armik...@gmail.com wrote: >> >> hi.in relay stopped working ipv6.address is correct all pings, including >> tor to the servers, but relay does not work.before that it worked perfectly >> 2 months. > > Please tell us your relay's fingerprint. > > Please copy and paste the notice-level logs that tor creates on startup, > from launch to the end of the ORPort and DirPort reachability checks. > > Please copy and paste your torrc, particularly the Address, ORPort, DirPort, > and OutboundBindAddress options. > > If we need your machines network config, we'll let you know. > > It can be hard to set up IPv6 for a relay, we're working on a grant to make > it easier. > > T > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays CE5ED345398CC02D573347C2F238F80B18E680EE. Aug 21 11:41:35.000 [notice] Tor 0.4.0.5 opening new log file. Aug 21 11:41:34.967 [notice] Tor 0.4.0.5 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1c, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A. Aug 21 11:41:34.967 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Aug 21 11:41:34.967 [notice] Read configuration file "/etc/tor/torrc". Aug 21 11:41:34.996 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong. Aug 21 11:41:34.997 [notice] Based on detected system memory, MaxMemInQueues is set to 2948 MB. You can override this by setting MaxMemInQueues by hand. Aug 21 11:41:34.999 [notice] Opening Socks listener on 127.0.0.1:9050 Aug 21 11:41:34.999 [notice] Opened Socks listener on 127.0.0.1:9050 Aug 21 11:41:35.000 [notice] Opening OR listener on 0.0.0.0:443 Aug 21 11:41:35.000 [notice] Opened OR listener on 0.0.0.0:443 Aug 21 11:41:35.000 [notice] Opening OR listener on [2a03:e2c0:bc7::2]:443 Aug 21 11:41:35.000 [notice] Opened OR listener on [2a03:e2c0:bc7::2]:443 Aug 21 11:41:35.000 [notice] Opening Directory listener on 0.0.0.0:80 Aug 21 11:41:35.000 [notice] Opened Directory listener on 0.0.0.0:80 Aug 21 11:41:36.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Aug 21 11:41:37.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Aug 21 11:41:37.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Aug 21 11:41:38.000 [notice] Your Tor server's identity key fingerprint is 'armik CE5ED345398CC02D573347C2F238F80B18E680EE' Aug 21 11:41:38.000 [notice] Bootstrapped 0% (starting): Starting Aug 21 11:42:17.000 [notice] Starting with guard context "default" Aug 21 11:42:17.000 [notice] Bootstrapped 5% (conn): Connecting to a relay Aug 21 11:42:17.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay Aug 21 11:42:17.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay Aug 21 11:42:17.000 [notice] Guessed our IP address as 109.173.41.42 (source: 131.188.40.189). Aug 21 11:42:18.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done Aug 21 11:42:18.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Aug 21 11:42:18.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Aug 21 11:42:18.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit Aug 21 11:42:20.000 [notice] Bootstrapped 100% (done): Done Aug 21 11:42:20.000 [notice] Now checking whether ORPort 109.173.41.42:443 and DirPort 109.173.41.42:80 are reachable... (this may take up to 20 minutes -- look for log messages indicating success) Aug 21 11:42:22.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent. Aug 21 11:42:23.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Aug 21 11:43:22.000 [notice] Performing bandwidth self-test...done. Aug 21 17:42:17.000 [notice] Heartbeat: It seems like we are not in the cached consensus. Aug 21 17:42:17.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 1.92 MB and received 6.28 MB. Aug 21 17:42:17.000 [notice] Average packaged cell fullness: 87.497%. TLS write overhead: 20% Aug 21 17:42:17.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 19/19 NTor. Aug 21 17:42:17.000 [notice] Since startup we initiated 0 and received 0 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 1 v3 connections; initiated 1 and received 6 v4 connections; initiated 16 and received 186 v5 connections. Aug 21 17:42:17.000 [notice] DoS mitigation since startup: 0 circuits killed with too many cells. 0 circuits rejected, 0 marked addresses. 0
