Thanks Amos, that explains helper activity in the cache.log around rotate time.
When the problem occurred I didn't run a mgr:ntlmauthenticators report but on one of the proxies just now it has 77 shutting down state and report is here - http://pastebin.com/jhaFeW9H
Regards
- Kris Glynn: (07) 3295 3987 - 0434602997
-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Monday, 30 September 2013 5:17 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] NTLM Authenticator Statistics 3.3.5
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
The content of this e-mail, including any attachments, is a confidential communication between Virgin Australia Airlines Pty Ltd (Virgin Australia) or its related entities (or the sender if this email is a private communication) and the intended addressee and is for the sole use of that intended addressee. If you are not the intended addressee, any use, interference with, disclosure or copying of this material is unauthorized and prohibited. If you have received this e-mail in error please contact the sender immediately and then delete the message and any attachment(s). There is no warranty that this email is error, virus or defect free. This email is also subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If this is a private communication it does not represent the views of Virgin Australia or its related entities. Please be aware that the contents of any emails sent to or from Virgin Australia or its related entities may be periodically monitored and reviewed. Virgin Australia and its related entities respect your privacy. Our privacy policy can be accessed from our website: www.virginaustralia.com
Received on Mon Sep 30 2013 - 07:26:23 MDT
This archive was generated by hypermail 2.2.0 : Mon Sep 30 2013 - 12:00:04 MDT