From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [192.168.210.80] (unknown [182.2.71.35]) by gnuweeb.org (Postfix) with ESMTPSA id B26B38060F; Tue, 30 Aug 2022 05:57:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1661839064; bh=2+cTv8dBuuVs50GPyi+M+Odd82YkxszXFgwVleTsv6o=; h=Date:From:To:Cc:References:Subject:In-Reply-To:From; b=I7F5LVeRIREGIpHhOBajcJ5o5PB7DZq6d2Pk/uwoylprKUEbNaT2PJ8xAsCFpnKjX OFkMuQi6nnbK6QIUNqV9GKejMBhPmea0qJOWoXjd46deGVXgT9KgIPzMP0Eektdv2k x/spg8fF0DxnvjrWfXyiOa3VyzSDpkOZhNRWPvxq5JJaye/mOhu0/2vcyUlQqsmEDz 93ZUFLuHtR3J/sX5q3DrUsgxZ3t1muMF9DtQz7TfrN2Q0FRXeO7wvbkKhP7+Z9QV3g Qv0e0PAwOGE7mP0JkUDNa3N1PWujIuipfbYN5+yo2qXciklBeVjfI4oehGbI55XkxP utaictchy9jcg== Message-ID: <903389a3-1c36-4bf3-cb30-7c12cb9b98ed@gnuweeb.org> Date: Tue, 30 Aug 2022 12:57:39 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Content-Language: en-US From: Ammar Faizi To: Georg Koppen Cc: bad-relays , GNU/Weeb Mailing List , Louvian Lyndal References: <291c272c-f3c6-6479-1b00-bf8c57ec9cf6@gnuweeb.org> <6827c274-5a85-aa8f-b41f-ccf520d7aad6@torproject.org> <1f42f7e1-8691-5b15-36c3-a7470294867c@gnuweeb.org> Subject: Re: Your TeaInside relay is failing to relay exit traffic In-Reply-To: <1f42f7e1-8691-5b15-36c3-a7470294867c@gnuweeb.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 8/25/22 5:13 PM, Ammar Faizi wrote: > On 8/25/22 4:27 PM, Georg Koppen wrote: >> There are different ways. One thing we do is to build circuits with the >> respective nodes to test as exits and then we try to connect to >> different websites and check whether there are any failures. In your >> case it seems connections are timing out. >> >> Another way, which you could try is using Tor Browser with your node as >> exit node. For that, after you have downloaded Tor Browser and extracted >> it, add to your torrc file (in >> tor-browser_en-US/Browser/TorBrowser/Data/Tor): >> >> ExitNodes F241330F16AF6BD90226CC9130DA8E20B58AAC3B >> >> The start Tor Browser and try to surf to some websites like popular news >> sites etc. Those requests are frequently timing out or take super long >> to load resulting caused by lots of circuit churn (as the circuit fails >> due to timeouts). > > Great, thanks for the tips! > > The latter way using Tor Browser sounds easier for me. I will > investigate this and be back to you soon. Hi Georg, I have been trying to investigate this for several days, but haven't been able to fix the issue. Looking at the Tor daemon process from htop, it is spinning at 100% CPU. I don't know what is going on, but as far as I can tell, it is still consuming CPU and network I/O. I tried to specify my relay fingerprint in torrc Tor browser like what you said previously. My Tor browser didn't work. It was always timing out with no clear error. From the server side, this is the last few hundred of lines of my Tor daemon log: https://gist.githubusercontent.com/ammarfaizi2/40be0cb122b5ad1240f9001f8e58eb7d/raw/2407fc3063d786e3e0054d522a0e63323e35513e/tor_log.txt Do you have any suggestion? If you need more information to diagnose this, tell me what do you need. I will happily provide it. -- Ammar Faizi