On 30/09/2013 7:26 p.m., Kris Glynn wrote:
> Getting back to the initial problem.. I first discovered it when users reported they couldn't authenticate to one of the proxies, when I logged into the squid server the cache.log was full of errors like "WARNING: external ACL 'ldap_group' queue overload. Using stale result" - when I dug further I noticed at the top of the cache.log (after the nightly squid -k rotate) it had entries such as "ipcCreate: fork: (12) Cannot allocate memory WARNING: Cannot run '/usr/bin/ntlm_auth' process." And "helperOpenServers: Starting 1/50 'ext_wbinfo_group_acl' processes ipcCreate: fork: (12) Cannot allocate memory WARNING: Cannot run '/usr/lib64/squid/ext_wbinfo_group_acl' process. " - it seemed odd to me that a squid -k rotate would either restart/stop/start helpers. Shouldn't a squid -k rotate leave helpers alone when it's just instructing squid to rotate the logs?
The helpers are logging to cache.log via stderr. They need to be
restarted to connect to the new cache.log once it has been rotated.
What does the mgr:ntlmauthenticators report show about the NTLM helpers
when this is going on?
Amos
Received on Mon Sep 30 2013 - 07:16:15 MDT
This archive was generated by hypermail 2.2.0 : Mon Sep 30 2013 - 12:00:04 MDT