Hey, This is indeed the issue I was aiming at.. It was never looked at before since nobody never seen this problem before If I am right. So I have a suggestion. Instead of just shooting at it we have the test "subject" in hands. The latest stable version of squid is 3.3 We can do run a basic test out of the production environment to make sure that we can reproduce the issue. Amos do we have a QA\BUG_TEST section in the bugzilla? This way we can look at a bug and classify it as a testing bug and close the issue with a more detailed report?? Back.. The issue is that the DNS did not responded fast enough to squid. Since it's not a bug that actually has a ground that affect a working(fully functional) network infrastructure I would say it's less of a bug but more of an issue that needs to be tested at 3.1 3.2 3.3 and 3.4 to make sure that it will be a *known bug* to make sure that in a case of a problem there will be an answer. Eliezer On 09/25/2013 09:04 AM, T Ls wrote: > Hi, > > Am 24.9.2013 23:38, schrieb Eliezer Croitoru: >> On 09/24/2013 03:56 PM, T Ls wrote: >>> What kind of reconfigure do you mean? >> The plain command of "squid -kreconf". > > This changed nothing. > >> From your previous mail it seems like these dns queries are new.. >> SO you are not aware of the existence of these requests before the last >> few days. > > That's right, these dns queries may have been there before, but I > noticed there existens first on monday (I did not expect them => I did > not looked for them). On monday someone (higher-ranking department) > played around with the dns servers and the dns replys took much longer > than usual, so squids delay was much greater => users complained. > > On tuesday, the dns servers behaves as usual, users did not complain > anymore, but the dns queries are still there (but there influence on > squids delay is much smaler). > >> ...> Once we do have the debug_options that Amos wanted to see we >> could then >> understand in a way the source of the queries which shouldn't be there >> from first glance at the squid.conf. > > Ok, thanks so far. > > Thomas >
