RE: authenticate_program bombs out

Hi Robert, thanks too for your suggestions!

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

the way it runs now, the only IO is stdin with "while(fgets(buf, 256, stdin)
!= NULL)" and stdout like "printf("ERR\n")"

> 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.

thanks, yep - this is all that the log reports:

2001/03/27 08:52:22| authenticateStart: 'mike:xxxxxxxxxxx'
2001/03/27 08:52:22| WARNING: All authenticator processes are busy.
2001/03/27 08:52:22| WARNING: 1 pending requests queued
2001/03/27 08:52:22| storeDirWriteCleanLogs: Starting...
2001/03/27 08:52:22| Finished. Wrote 105 entries.
2001/03/27 08:52:22| Took 0.0 seconds (7000000.0 entries/sec).
FATAL: Too many queued authenticator requests
Squid Cache (Version 2.3.STABLE4): Terminated abnormally.
CPU Usage: 0.000 seconds = 0.000 user + 0.000 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 0

i suspect that "WARNING: All authenticator processes are busy" *really*
means that none of the authenticate_program instances were able to start up
:(

anyone?

thanks and regards.
Received on Tue Mar 27 2001 - 02:47:13 MST