[squid-users] Squid for Windows Repeatedly Crashing

[Van Order, Drew (US - Hermitage)]

Thank you for replying, and that's an excellent point.

Short answer--definitely not in a container, these are garden variety VMWare instances. I've already flagged the OS power settings to maximum performance, so nothing should be going to sleep. I'll doublecheck, though.

So, if I understand correctly, this error could also be indicative of an issue in between the agent and Squid. Agents first go through a firewall, then the F5 before reaching Squid.

[Stopped, reason:Listener socket closed job1]: (14) Bad address

Any thoughts on this error, which tends to be more common than the other?

2019/02/20 09:42:33 kid1| comm_poll: poll failure: (14) Bad address
2019/02/20 09:42:33 kid1| Select loop Error. Retry 2



-----Original Message-----
From: Amos Jeffries <squid3 at treenet.co.nz>
Sent: Thursday, February 21, 2019 6:38 AM
To: squid-users at lists.squid-cache.org
Subject: Re: [squid-users] Squid for Windows Repeatedly Crashing

On 21/02/19 6:23 pm, Van Order, Drew (US - Hermitage) wrote:
> Hello folks, we're running Squid 3.5.28 on four Windows 2016 VM's,
> each has 4 CPU, 8 GB memory, 10 GB NIC. We implemented Squid to
> support forwarding Azure Log Analytics data, it's all CONNECT. The
> Squids are load balanced through a F5. There are less than 1,000
> servers sending data to Log Analytics.
>
>
>
> All four Squids are regularly crashing, and I don't know how to
> interpret the errors in cache.log. It crashes if we disable caching too.
>
...
>
> 2019/02/20 09:42:32 kid1|  FD 12, 10.5.11.12 [Stopped, reason:Listener
> socket closed job1]: (14) Bad address
>

Something other than Squid closed the network socket Squid was using to receive new client connections (the http_port socket).

The only things which should know that socket even exists are Squid and the operating system.

This is not an error I've seen before. Is this Squid maybe running in a container or VM which is being hibernated, or suspended, or anything along those lines which may cause the OS filedescriptors to change unexpectedly?

Amos

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.

v.E.1