Re: [tor-talk] Fwd: inreasing MaxClientCircuitsPending useful?

2013-02-01 Thread Quan
On 2013-02-01 20:29, grarpamp wrote: >> Anyone with an advice on this? > > 1) Bumping your own thread within 24hrs is lame. Why? There are a lot of users on this list and many topics are forever forgotten if not answered in the first day (or two). > 2) Bump the parameter value to whatever seems

[tor-talk] Fwd: inreasing MaxClientCircuitsPending useful?

2013-02-01 Thread Quan
Anyone with an advice on this? Original Message Subject: inreasing MaxClientCircuitsPending useful? Date: Thu, 31 Jan 2013 22:38:13 +0100 I have around 250 hidden services in torrc and I sometimes see this message: [notice] We'd like to launch a circuit to handle a connection,

Re: [tor-talk] tor crashing: [err] circuit_build_times_get_xm(): Bug: circuitbuild.c:803: circuit_build_times_get_xm: Assertion bin_counts > 0 failed; aborting

2013-01-31 Thread Quan
On 2013-01-31 23:04, Mike Perry wrote: > Bleh. I'm guessing your circuit build times data is somehow > degenerate/corrupted. Perhaps you ran out of disk space and the state > file got truncated? disk has enough free space and there is also a lot of free ram. I cannot say anything about state file

[tor-talk] inreasing MaxClientCircuitsPending useful?

2013-01-31 Thread Quan
I have around 250 hidden services in torrc and I sometimes see this message: [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. Does this mean that the connection to hidden service was not estab

[tor-talk] tor crashing: [err] circuit_build_times_get_xm(): Bug: circuitbuild.c:803: circuit_build_times_get_xm: Assertion bin_counts > 0 failed; aborting

2013-01-31 Thread Quan
I have around 250 hidden services in torrc. I upgraded tor today and restarted process. Tor crashed twice with this message: [err] circuit_build_times_get_xm(): Bug: circuitbuild.c:803: circuit_build_times_get_xm: Assertion bin_counts > 0 failed; aborting Third time I run it it was to able to

[tor-talk] How to debug "missing" HiddenService

2012-12-13 Thread Quan
I have over 100 HiddenService entries in torrc files. I just discovered that some .onion addresses are not reacting at all. It always comes to timeout. Other onion addresses on the same server work just fine. I turned on the logs (Log info-err, SafeLogging 0) in Tor and I see one of these "missi

Re: [tor-talk] hidden service not reachable: Your system clock just jumped 121 seconds forward; assuming established circuits no longer work.

2012-11-26 Thread Quan
On 2012-11-26 22:57, Julian Yon wrote: > On Sun, 25 Nov 2012 23:34:30 +0100 > Quan wrote: > >> On 2012-11-25 16:22, Andreas Krey wrote: >>>> p.s.: My system clock is running correctly >>> >>> Pretty definitely not. NB: The BIOS clock isn't the s

Re: [tor-talk] hidden service not reachable: Your system clock just jumped 121 seconds forward; assuming established circuits no longer work.

2012-11-25 Thread Quan
On 2012-11-25 16:22, Andreas Krey wrote: >> p.s.: My system clock is running correctly > > Pretty definitely not. NB: The BIOS clock isn't the system clock > of the operating system (which one?); this looks like your > system clock gets alternatively set from two different sources > (and to differ

[tor-talk] hidden service not reachable: Your system clock just jumped 121 seconds forward; assuming established circuits no longer work.

2012-11-25 Thread Quan
I see this message in tor logs and my hidden service is not reachable: Received reload signal (hup). Reloading config and resetting internal state. Tor 0.2.2.39 (git-2f7e71c2e896772f) opening log file. Your system clock just jumped 121 seconds forward; assuming established circuits no longer