Re: [squid-users] Wrong password locking the users logins

Hi All

Thanks "Squid FAQ" for the help. Now Squid is working fine. (And the users
are happy...)
The loop was caused by a mistake in one of our ACLs at squid.conf

At FAQ (10.8-Common Mistakes) there is the tip...

"For example, the following access control configuration will never work:

        acl ME src 10.0.0.1
        acl YOU src 10.0.0.2
        http_access allow ME YOU "

...and we had something like this.

Debugging Squid at level 9 ("debug_options ALL,9") was too wealth to find
and solve the problem.

Best Regards
W. Tomico Silva
Internetworkers from Brazil

>From: "Tomico Silva" <tomicosilvabr@hotmail.com>
>To: squid-users@squid-cache.org
>Subject: [squid-users] Wrong password locking the users logins Date: Thu,
>26 Sep 2002 17:08:32 -0300
>
>
>
>Hello All,
>
> I have a question about the SQUID (2.4.STABLE7) using SMB_AUTH as
>an authenticate program.
>Squid just sends username <space> password <newline> and expects OK
>or ERR as result.
>Fine, when Squid receives an "OK" message from the smb_auth he allows
>the access to the user and go on with his work.
>But when Squid receives an "ERR" message from the smb_auth then he
>starts to ask the authenticate program again with the same (wrong)
>username/password.
>Every 3 seconds squid open a new socket to the PDC (at port 139) and
>then the number of opened sockets, many of them in a "TIME_WAIT"
>status, go to the maximum (1024), and the Squid run out of free sockets
>to do his work and we have to shutdown the Squid.
>As a consequence of a lot of try the PDC lock the user login.
>
>At the limit Squid sends to the users not the requested web pages but
>an error message:
>"Sep 26 11:21:50 cache squid[86165]: comm_open: socket failure: (55) No
>buffer space available"
>
>Is there an option at squid.conf to control the number of opened socket
>per user at these cases ?
>
>
>Thanks in advance,
>
>Tomico Silva
>InternetWork
>Brazil
Received on Mon Sep 30 2002 - 07:54:11 MDT