This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] more than 10 concurrent measurements to the same target
- Previous message (by thread): [atlas] more than 10 concurrent measurements to the same target
- Next message (by thread): [atlas] more than 10 concurrent measurements to the same target
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Klaus Darilion
klaus.mailinglists at pernau.at
Fri Dec 11 17:39:06 CET 2015
On 11.12.2015 16:11, Stephane Bortzmeyer wrote: > On Wed, Dec 09, 2015 at 07:38:52PM +0100, > Klaus Darilion <klaus.mailinglists at pernau.at> wrote > a message of 12 lines which said: > >> When scheduling checks I often get the error: "We do not allow more than >> 10 concurrent measurements to the same target." >> >> Imo this is not correct. > > I believe that the counter is global (not just your measurements). I > often see this error when measuring 8.8.8.8 (a very popular target). That's what I heard too. But I have the problem when targeting my server which for sure nobody test except me. I also have the problem even when all my measurements to this target are already stopped. It seems that this counter is not updated in real time. regards Klaus
- Previous message (by thread): [atlas] more than 10 concurrent measurements to the same target
- Next message (by thread): [atlas] more than 10 concurrent measurements to the same target
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]