Search squid archive

Re: Intermittent SquidKerbAuth 'Cannot allocate memory'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/01/11 01:37, Nick Cairncross wrote:
Hi List,

 From time to time my users experience constant unsatisfiable prompts from squid. Cache.log reports:

2011/01/07 12:04:53| authenticateNegotiateHandleReply: Error validating user via Negotiate. Error returned 'BH gss_acquire_cred() failed: Unspecified GSS failure.  Minor code may provide more information. Cannot allocate memory'
2011/01/07 12:04:53| authenticateNegotiateHandleReply: Error validating user via Negotiate. Error returned 'BH gss_acquire_cred() failed: Unspecified GSS failure.  Minor code may provide more information. Cannot allocate memory'

Quickest fix is to 'service squid restart' but I'd like to get to the bottom of it as how/why this occurs. Squidkerbauth helper can't allocate memory, freezes and refuses to process requests. Has anyone else come across this sort of thing before? Memory leak..? Any suggestions for further debugging welcome.

RHEL5.3 x86, Squid 3.20STABLE, squidkerbauth 1.0.7 (IIRC)

What does "squid -v" report as the version? we don't have a 3.20 release yet.

And yes it looks like a memory leak in the helper.

Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.10
  Beta testers wanted for 3.2.0.4


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux