Re: [squid-users] "Cannot open HTTP Port" on 3.0.STABLE1

Alan Strassberg wrote:
> Squid 3.0R1 fails in daemon mode when binding to a privileged port.
> Works fine on ports > 1023.
>
> There is nothing running on the ports as verified with "lsof -i" and
> "netstat -a"
>
> Debug (squid -X) shows this:
> 2008/02/04 11:13:24.293| acl_access::containsPURGE: invoked for
> 'http_access allow manager localhost'
> 2008/02/04 11:13:24.293| acl_access::containsPURGE: can't create tempAcl
> 2008/02/04 11:13:24.293| acl_access::containsPURGE: returning false
> 2008/02/04 11:13:24.293| leave_suid: PID 8500 called
> 2008/02/04 11:13:24.293| leave_suid: PID 8500 giving up root, becoming 'squid'
> 2008/02/04 11:13:24.293| command-line -X overrides: ALL,1
>
> What is "acl_access::containsPURGE: can't create tempAcl" trying to
> tell me to fix?
>
> This is FreeBSD 6.3-STABLE

Nothing to worry about that one. Just squid barfing a little trying to
prune its ACL lists. Squid handles it nicely so I don't know what that
debug was left for.

Amos

-- 
Please use Squid 2.6STABLE17+ or 3.0STABLE1+
There are serious security advisories out on all earlier releases.