Re: authenticate_program bombs out

Does you program uses buffered I/O? What is the lag time doing
authentication?

I don't know too much about the "NT" Port of squid (I maintain the
cygwin/Win32 port) but on every other version of squid, turning the
debug level to ALL,1 29,9 will get the actual input and ouput to the
authenticators logged. Then you can examine the log (In the event log
for your port) to see whats going on.

Rob

----- Original Message -----
From: "mike" <mike@gsat.net.au>
To: <squid-dev@squid-cache.org>
Sent: Monday, March 26, 2001 9:49 PM
Subject: authenticate_program bombs out

> Hi Folks,
>
> please excuse me if i appear to lack the correct ettiquette for this
list -
> i have only just discovered squid (yes i'm a slow learner! ;-) and
have come
> up against a baffling (well to me anyway) problem about which i am
hoping to
> gain some guidance from the enlightened.
>
> well i am used to M$ proxy mainly, and am just sick to death of the
way they
> handle their API, so you can imagine my glee when i realised how squid
does
> it - way cool! :)
>
> but alas, i quickly rapped out a test authenticate_program according
to my
> understanding, but it just causes squid to bomb out - process dies
with the
> error:
>
> FATAL: Too many queued authenticator requests
> Squid Cache (Version 2.3.STABLE4): Terminated abnormally.
>
> now when i run the authenitcate program at a commandline, it works
just
> fine. the code is supposed to authenticate out of my SQL database -
the
> back end to my radius dial-up service - and seems to do it nicely when
i run
> it interactively.
>
> by the way, i am running squid on windows2000 advanced server - the
> authenticate_program takes no arguments and seems to behave as
expected in a
> cmd shell. the squid version is: 2001/03/26 17:47:19| Starting Squid
Cache
> version 2.3.STABLE4 for WIN32...
>
> is anyone able to shed some light on this? any suggestion most
appreciated
> indeed!
>
> thanks and regards,
>
> Mike Everest.
>
>
>
>
>
Received on Mon Mar 26 2001 - 14:43:11 MST