[squid-users] Error while writing to TCP socket: Permission denied

[Amos Jeffries]

On 07/06/17 22:54, Ишаяhу Ластов wrote:
>
> I use squid on freebsd 10.3. When I set proxy adress in web brouser, I 
> can't attach files to mail on mail.ru. Whithout proxy it works. In 
> access.log there are no errors. In cache.log I've got:
>
> |2017/05/29 21:12:16 kid1| local=217.151.68.36:34572 
> remote=217.69.139.216:443 FD 44 flags=1: read/write failure: (13) 
> Permission denied 2017/05/29 21:12:16 kid1| local=217.151.68.36:36057 
> remote=217.69.139.216:443 FD 44 flags=1: read/write failure: (13) 
> Permission denied |
>
> FD can change If I understand right, how to use lson, then
>

FD in this case is an open network connection. Each TCP connection has 
exactly one FD in Squid. They get re-used like ports, but it should 
remain unchanged as long as the TCP connection exists. Another identical 
TCP connection made later may get a different FD.

 > How can I solve that problem?


It is rather odd to have "Permission denied" (filesystem error!) on a 
network socket. The network equivalent is a failure to connect in the 
first place, or a sudden close event if already open. I suspect a bug in 
your OS kernel or whatever security system it has controlling access to 
system resources.

If this were Linux I would point at SELinux misconfiguration, but I'm 
not sure what (if anything) FreeBSD has doing that sort of control.


Sorry
Amos