[squid-users] Assertion failed on Squid 4 when peer restarted.

[Amos Jeffries]

On 28/03/18 03:24, Alex Crow wrote:
> I have a squid 4.0.22 running peered with a 3.5.24 proxy. The latter
> machine stopped responding and I had to reboot it, and then the 4.0.22
> one crashed. Here's a log snippet:
> 
> 2018/03/27 15:01:48 kid1| WARNING: failed to unpack metadata because
> store entry metadata is too big
> 2018/03/27 15:04:09 kid1| Detected DEAD Sibling: webproxy.ifa.net
> 2018/03/27 15:04:09 kid1| Detected REVIVED Sibling: webproxy.ifa.net
> 2018/03/27 15:06:01 kid1| Detected DEAD Sibling: webproxy.ifa.net
> 2018/03/27 15:06:01 kid1| Detected REVIVED Sibling: webproxy.ifa.net
> 2018/03/27 15:06:44 kid1| Error negotiating SSL connection on FD 216:
> (104) Connection reset by peer
> 2018/03/27 15:06:57 kid1| Error negotiating SSL connection on FD 199:
> (104) Connection reset by peer
> 2018/03/27 15:06:57 kid1| Error negotiating SSL connection on FD 169:
> (104) Connection reset by peer
> 2018/03/27 15:06:57 kid1| Error negotiating SSL connection on FD 29:
> (104) Connection reset by peer
> 2018/03/27 15:06:57 kid1| Error negotiating SSL connection on FD 188:
> (104) Connection reset by peer
> 2018/03/27 15:06:57 kid1| Error negotiating SSL connection on FD 190:
> (104) Connection reset by peer
> 2018/03/27 15:07:12 kid1| Error negotiating SSL connection on FD 912:
> (104) Connection reset by peer
> 2018/03/27 15:07:13 kid1| Error negotiating SSL connection on FD 514:
> (104) Connection reset by peer
> 2018/03/27 15:07:26 kid1| ERROR: negotiating TLS on FD 236:
> error:00000000:lib(0):func(0):reason(0) (5/-1/104)
> 
> 2018/03/27 15:07:41 kid1| Error negotiating SSL connection on FD 129:
> (104) Connection reset by peer
> 2018/03/27 15:08:17 kid1| assertion failed: store.cc:1690: "!mem_obj"
> 
> Any ideas?
> 

First idea is to check bugzilla. I see nothing there.

Second is to upgrade to the latest v4 beta release (4.0.24 right now).

Third idea is to report to bugzilla or ask on squid-dev.

Amos