RE: [squid-users] Squid 2.5.STABLE3 and ntlm and authentication popup

> So far I'm sticking by my original hunch - that the problem
> is the PDC taking too long to respond, and not with Squid
> itself. But we'll see what the numbers reveal.

Since upping the # of children I still haven't had any
helperStatefulDefer's, but I am getting invalid callback's and since
I've increased NTLM logging I'm seeing a number of challenge exceeded
max lifetime by xxx seconds.

Here's an excerpt from cache.log:

2003/07/01 19:03:15| authenticateValidateUser: Auth_user_request was
NULL!
2003/07/01 19:03:15| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:15| authenticateNTLMChangeChallenge_p: Challenge
exceeded max lifetime by 52 seconds
2003/07/01 19:03:15| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:15| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:15| authenticateNTLMAuthenticateUser: proxy-auth cache
miss.
2003/07/01 19:03:15| authenticateValidateUser: Auth_user_request was
NULL!
2003/07/01 19:03:15| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:15| authenticateNTLMChangeChallenge_p: Challenge
exceeded max lifetime by 51 seconds
2003/07/01 19:03:15| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:15| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:15| authenticateNTLMAuthenticateUser: proxy-auth cache
miss.
2003/07/01 19:03:16| authenticateValidateUser: Auth_user_request was
NULL!
2003/07/01 19:03:16| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:16| authenticateNTLMChangeChallenge_p: Challenge
exceeded max lifetime by 52 seconds
2003/07/01 19:03:16| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:16| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:16| authenticateNTLMAuthenticateUser: proxy-auth cache
miss.
2003/07/01 19:03:16| authenticateValidateUser: Auth_user_request was
NULL!
2003/07/01 19:03:16| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:16| authenticateNTLMChangeChallenge_p: Challenge uses
(1) exceeded max uses (0)
2003/07/01 19:03:16| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:16| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:16| authenticateNTLMAuthenticateUser: proxy-auth cache
miss.
2003/07/01 19:03:20| authenticateValidateUser: Auth_user_request was
NULL!
2003/07/01 19:03:20| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:20| authenticateNTLMChangeChallenge_p: Challenge
exceeded max lifetime by 3125 seconds
2003/07/01 19:03:20| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:20| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:20| authenticateNTLMAuthenticateUser: proxy-auth cache
miss.
2003/07/01 19:03:20| authenticateValidateUser: Auth_user_request was
NULL!
2003/07/01 19:03:20| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:20| authenticateNTLMChangeChallenge_p: Challenge
exceeded max lifetime by 3124 seconds
2003/07/01 19:03:20| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:20| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:20| authenticateNTLMAuthenticateUser: proxy-auth cache
miss.
2003/07/01 19:03:23| authenticated
ch (removed)
auth NTLM (removed)
authuser (removed)
2003/07/01 19:03:23| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:23| authenticated
ch (removed)
auth NTLM (removed)
authuser (removed)
2003/07/01 19:03:23| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:23| AuthenticateNTLMHandleReply: invalid callback data.
Releasing helper '0x64d7c8'.
2003/07/01 19:03:23| authenticateNTLMHelperServerAvailable: not starving
- returning 1
2003/07/01 19:03:23| AuthenticateNTLMHandleReply: invalid callback data.
Releasing helper '0x64b718'.

All told there were 174 challenge exceeded max lifetime messages that
ranged between 1 and 24706 seconds. And 44 invalid callback data
messages.

At 20:42 this is what the cache manager report looked like.

NTLM Authenticator Statistics:
number running: 32 of 32
requests sent: 6218
replies received: 6218
queue length: 0
avg service time: 364 msec

# FD PID # Requests # Deferred Requests Flags Time Offset Request
1 7 7039 1027 0 A 51.515 0 (none)
2 8 7040 327 0 A 51.508 0 (none)
3 9 7041 127 0 A 51.434 0 (none)
4 10 7042 42 0 A 2781.871 0 (none)
5 11 7043 13 0 A 5545.033 0 (none)
6 12 7044 9 0 A 5545.012 0 (none)
7 13 7045 3 0 A 5544.775 0 (none)
8 14 7046 2 0 A 5544.755 0 (none)
9 15 7047 0 0 A 544276.436 0 (none)
(the rest were unused)

After 20:42 there were another 34 lifetime exceeded messages, ranging
from 36 to 2451 seconds.

~ Daniel

-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.
Received on Wed Jul 02 2003 - 06:05:50 MDT