Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-08-14 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
-+-
 Reporter:  yurivict271  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-httptunnel,  |  Actual Points:
  033-triage-20180320, 033-removed-20180320  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by traumschule):

 * keywords:  033-triage-20180320, 033-removed-20180320 => tor-httptunnel,
 033-triage-20180320, 033-removed-20180320


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-02-05 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * status:  new => needs_information


Comment:

 Once the ZeroNet process has stopped, you still have Tor at 100% CPU? In
 other words, do you still see many many SOCKS request coming in after?

 What probably we need now is debug logs by adding this to your torrc:

 `Log debug file /tmp/tor-debug.log`.

 This might be very very load but the idea is to catch what tor is doing
 _after_ ZeroNet has stopped spamming tor in circuit requests.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-20 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 So, once #24899 will be fixed, this problem will still likely persist.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-20 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 After increasing the limit to {{{MaxClientCircuitsPending 128}}}, I still
 see the problem. The log ended with
 {{{
 Jan 20 16:33:30.000 [notice] We'd like to launch a circuit to handle a
 connection, but we already have 128 general-purpose client circuits
 pending. Waiting until some finish. [1808313 similar message(s) suppressed
 in last 600 seconds]
 }}}
 ZeroNet has been stopped at about the same time.

 The tor process was at 100% CPU for at least 10 minutes after ZeroNet was
 stopped. Only after ~15 minutes it became usable again.

 The problem seems to be deeper than just the running out of circuits. It
 persists for many minutes after all temporary ZeroNet onions have been
 shut down.

 Once the user-process is shut down, all its onions and circuits should
 shut down promptly. It looks like this doesn't happen.

 Somebody should re-create the setup I have (Tor+ZeroNet with tor=always
 and a lot of sites on FreeBSD 11.1), and see what the problem is.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-17 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 The milestones on this one and on #24899 don't match. :-)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-17 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * milestone:   => Tor: 0.3.3.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-15 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 This feature suggestion might help in this situation:
 https://trac.torproject.org/projects/tor/ticket/24899

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-15 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 I think the default limit of 32 is also very low. It is maybe okay for
 browsing. But if people have ZeroNet with several sites, the reasonable
 upper limit is even hard to determine. There can be a lot of peers
 requesting/syncing content, depending on situation.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-15 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yawning):

 I don't think this is a bug.  There is a upper limit on how many outgoing
 circuits are being constructed at any given time, the majority of the user
 base does not bump into the limit, and for those that do, there is a knob
 that can be used to increase said limit.  And your tor instance is logging
 that it is hitting the limit whenever the delays occur.

 {{{
MaxClientCircuitsPending NUM
Do not allow more than NUM circuits to be pending at a time for
 handling client streams. A circuit is pending if we have begun
 constructing it,
but it has not yet been completely constructed. (Default: 32)
 }}}

 There may be a case for having an additional separate limits for
 restricting pending circuits by purpose, but that should probably be a
 separate ticket.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-14 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 More than likely, the non-SOCKS requests are sent by ZeroNet. Here is the
 bug report: https://github.com/HelloZeroNet/ZeroNet/issues/1243

 But service interruption, and the messages
 > [notice] We'd like to launch a circuit to handle a connection, but we
 already have 32 general-purpose client circuits pending. Waiting until
 some finish.
 are probably caused by busy temporary ZeroNet onion services.

 No matter how busy they get, this shouldn't block access for other users,
 IMO.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-14 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 These ZeroNet hidden services might be very busy.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-14 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 > Does it happen with only one onion service?
 Will see.

 > How loaded are the onion services?
 Supposed to be totally idle. The names weren't advertised, and only exist
 for experimental purposes.

 > Does it happen on Linux or some other OS too?
 I only have FreeBSD.

 > Is your network failing at the time?
 Network functions very well, is never interrupted.

 > What other things is the client being asked to do at the same time?
 ZeroNet runs in tor=always mode. It creates some temporary onions via the
 control port, so that other peers can connect.

 

 What is also interesting is that this "bombing" stopped after tor restart.
 Now, after a while, I only see one such line again:
 {{{
 Jan 14 23:26:36.000 [notice] Have tried resolving or connecting to address
 '[scrubbed]' at 3 different places. Giving up.
 Jan 14 23:27:54.000 [notice] Have tried resolving or connecting to address
 '[scrubbed]' at 3 different places. Giving up.
 Jan 14 23:28:20.000 [notice] Have tried resolving or connecting to address
 '[scrubbed]' at 3 different places. Giving up.
 Jan 14 23:28:40.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit
 $BC630CBBB518BE7E9F4E09712AB0269E9DC7D626~IPredator at 197.231.221.211.
 Retrying on a new circuit.
 Jan 14 23:29:00.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $379FB450010D17078B3766C2273303C358C3A442~aurora
 at 176.126.252.12. Retrying on a new circuit.
 Jan 14 23:29:21.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $30C19B81981F450C402306E2E7CFB6C3F79CB6B2~Libero
 at 64.113.32.29. Retrying on a new circuit.
 Jan 14 23:29:27.000 [warn] Missing mapping for virtual address
 '[scrubbed]'. Refusing.
 Jan 14 23:33:43.000 [warn] Socks version -125 not recognized. (This port
 is not an HTTP proxy; did you want to use HTTPTunnelPort?)
 Jan 14 23:33:43.000 [warn] Fetching socks handshake failed. Closing.
 Jan 14 23:34:43.000 [warn] Rejecting SOCKS request for anonymous
 connection to private address [scrubbed].
 Jan 14 23:36:40.000 [notice] Have tried resolving or connecting to address
 '[scrubbed]' at 3 different places. Giving up.
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-14 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 Replying to [ticket:24897 yurivict271]:
 > Jan 14 22:11:35.000 [notice] We'd like to launch a circuit to handle a
 connection, but we already have 32 general-purpose client circuits
 pending. Waiting until some finish. [1312433 similar message(s) suppressed
 in last 600 seconds]

 This one looks like #14006, and looks related to a "Tor can't reach
 anything" behavior.

 Trying to narrow down some variables would be smart here. Does it happen
 with only one onion service? Does it happen on Linux or some other OS too?
 Is your network failing at the time? How loaded are the onion services?
 What other things is the client being asked to do at the same time?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-14 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by yurivict271):

 > You should figure out what you have bombing your socksport with non-
 socks requests.

 Yes, I will try to figure this out.

 But it bombs it once in every several seconds. This shouldn't cause
 service interruption.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-14 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 Replying to [ticket:24897 yurivict271]:
 > Jan 14 22:10:41.000 [warn] Socks version -125 not recognized. (This port
 is not an HTTP proxy; did you want to use HTTPTunnelPort?)

 You should figure out what you have bombing your socksport with non-socks
 requests.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

2018-01-14 Thread Tor Bug Tracker & Wiki
#24897: Tor seems to malfunction on FreeBSD
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by arma):

 * component:  - Select a component => Core Tor/Tor


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs