On 11/07/2013 1:16 a.m., x-man wrote:
Hi,
it was compilation error and after fixing it now it's working fine when
using single Squid process...
I got problems when trying to use workers
Listen settings are like this:
http_port 3128
http_port 8080 transparent
http_port 8081 tproxy
workers 2
is the above correct and do I need to specify more ports with if/else
clauses for the different workers?
No. The http_port directive is SMP-aware.
and now the actual issues is that I get these in my log files
2013/07/10 18:41:15 kid2| commBind: Cannot bind socket FD 19 to [::]: (2) No
such file or directory
...
2013/07/10 18:41:12 kid1| commBind: Cannot bind socket FD 18 to [::]: (2) No
such file or directory
...
These are usually seen in SMP configurations where the UDS sockets
between workers are unable to be created. Check your /var/run/squid
directory has read-write permissions to the Squid user/group (maybe for
root/other as well).
Hint to anyone diagnosing these in future: the UDS/IPC socket can be
identified by the *lack of port number* in the bind message. TCP/IP
sockets will have at minimum a port number.
Amos
