Discussion:
[squid-users] FD 222 flags=1: read/write failure: (110) Connection timed out
Jonh Smith
2018-10-19 11:26:05 UTC
Permalink
ey Folks,


Sorry for bad sentence, my English isn't good when i expected.

I have a litle problem with two user with Outlook (using MAC).
Precisly, they using the latest version of Outlook, latest iOS and surfing
in the internet with squid proxy it's not a problem, everything works fine
exepct desynchronization every 30 minutes with their clien outlook.

I have a message d'error in /var/log/squid/cache.log
local=XX.XX.XX.XX:XXXX remote=XX.XX.XX.XX:XXXXX FD 222 flags=1: read/write
failure: (110) Connection timed out

Configuration Squid :
auth_param ntlm program /usr/bin/ntlm_auth
--helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 150 startup=0 idle=1
auth_param ntlm keep_alive on


auth_param basic program /usr/bin/ntlm_auth
--helper-protocol=squid-2.5-basic
auth_param basic children 5 startup=5 idle=1
auth_param basic realm Proxy_SQUID
auth_param basic credentialsttl 8 hours

I insist in a fact, this problem appear on MAC. For windows everithing works
fine.

Thanks in advance for your advice, tips and idea.

Best regards.






--
Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
Amos Jeffries
2018-10-20 04:22:51 UTC
Permalink
Post by Jonh Smith
ey Folks,
Sorry for bad sentence, my English isn't good when i expected.
I have a litle problem with two user with Outlook (using MAC).
Precisly, they using the latest version of Outlook, latest iOS and surfing
in the internet with squid proxy it's not a problem, everything works fine
exepct desynchronization every 30 minutes with their clien outlook.
I have a message d'error in /var/log/squid/cache.log
local=XX.XX.XX.XX:XXXX remote=XX.XX.XX.XX:XXXXX FD 222 flags=1: read/write
failure: (110) Connection timed out
This has nothing to do with authentication.

The TCP stack, NAT system, or some other software on one of the machines
between the local XX.XX.XX.XX:XXXX and remote XX.XX.XX.XX:XXXXX has
timed out its records about that TCP connection and closed it.

Not using a connection for 30min sounds like a long timeout. Normal TCP
timeouts are 5min. Each active TCP connection is using up many network
resources just by staying open so letting them stay around for long
periods is a bad idea.

Amos

Loading...