The kdump doesn't show any sign of infinite loop, but squid 100% CPU (instead of normal CPU usage ~5-15%) and the denial of service caused (squid is unavailable when it uses 100% CPU or very very slow), reminds me of an infinite loop under a thread. The kdump is done when squid hangs, then it seems all works fine, very strange... Anyway kdump file grows in size in the time when this event happened. -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le mercredi 15 mai 2013 à 15:53 -0600, Alex Rousskov a écrit : > On 05/15/2013 01:07 PM, Loïc BLOT wrote: > > > Sorry, but it's an approximation, when there is only few users squid can > > run for hours :) > > I see. This information increases the number of suspects, but the > recommended triaging methods remain the same (FWIW, kdump is not one of > them). > > > > Squid has got in an infinite loop. Here is a kdump extract of squid it > > seems there is no special kernel call: > > This kdump does not show a infinite loop -- things change as Squid reads > and writes data. Was that kdump growing as Squid was inside the infinite > loop? Or did it stop grow once Squid entered the loop? > > > Thank you, > > Alex.
Attachment:
signature.asc
Description: This is a digitally signed message part
