[SOLVED ]Squid 0.4.44_25 / assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)

[vijay7]

Finally, i have moved to standalone squid proxy, and I am not getting any issues in standalone, but we have another machine running pfsense and squid, same in my case as well, our company is asking about this issue, don't know why everyday morning 9 AM squid will be down, I had to put someone in a day to continuously monitor because even the watchdog is not able to start this.

[viberua]

My Squid also start crashing.
In Friday 13 :) evening Squid and SquidGuard services stopped working.
When i tried to run it from services - webpages was opening, but after few seconds Squid services stopped again.
I have rebooted server, but no luck - after few seconds Squid stop working and pages don't load.
Then i disabled MITM and Squid falling is stopped.
We are using 2.4.5-RELEASE-p1 of Pfsense and 0.4.44_35 Squid with 1.16.18_9 SquidGuard.
Where/which logs i should check for find what cause this crashing?

[tobyswe]

Now this morning the problem is really bad. Several times SQUID is stopping. We did not have any other choice then reinstalling our old Fortigate and pay the licenses for the proxy. Anyone heard of a solution of this issue ?
Someone mentioned to test a 2.5 snapshot. Maybe a bit risky in a production environment

[viberua]

Today enabled MITM mode. After 2 hours Squid is stop working. Which logs check?

[aGeekhere]

Is this issue fixed yet?

[viktor_g]

watch https://redmine.pfsense.org/issues/10608

[viberua]

This post is deleted!

[Volnei]

This post is deleted!

[Volnei]

Hi,

After I updated the squid to the 0.4.44_36 version it started to crash and show the same message inside the cache.log file.

I may be wrong, but I saw a correlation between IP 13.224.211.126 (Amazon) and the problem. So, I bypassed this network from the proxy to see if the problem can be fixed.

pfsense: 2.4.5-RELEASE-p1
squid: 0.4.44_36

2021/01/12 13:46:33 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 13:46:35 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 13:46:37 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 13:46:38 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 14:58:10 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 14:58:12 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 14:58:14 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 14:58:16 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 14:58:17 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/12 14:58:19 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"

[Tue Jan 12 13:46:35 2021].337 438 10.15.31.22 NONE/200 0 CONNECT 13.224.211.105:443 - ORIGINAL_DST/13.224.211.105 -
[Tue Jan 12 13:46:38 2021].682 475 10.15.31.22 NONE/200 0 CONNECT 13.224.211.105:443 - ORIGINAL_DST/13.224.211.105 -
[Tue Jan 12 14:58:12 2021].412 477 10.15.31.22 NONE/200 0 CONNECT 13.224.211.126:443 - ORIGINAL_DST/13.224.211.126 -
[Tue Jan 12 14:58:16 2021].011 424 10.15.31.22 NONE/200 0 CONNECT 13.224.211.126:443 - ORIGINAL_DST/13.224.211.126 -

[vijay7]

@volnei hey what made to think, that amazon IP is the culprit?

[Volnei]

So ... as I said, I'm not sure about that. It was more due to the coincidence in access times.
for example:
2021/01/12 13:46:38 kid1 | assertion failed: http.cc:1533: "! Comm :: MonitorsRead (serverConnection-> fd)"
[Tue Jan 12 13:46:38 2021] .682 475 10.15.31.22 NONE / 200 0 CONNECT 13.224.211.105:443 - ORIGINAL_DST / 13.224.211.105 -

When I bypass the proxy network, the problem no longer occurred.

[A18G3]

@volnei I have the same problem. The problem, even if it was solved, surfaced again in the latest squid versions 0.4.44_35 - 0.4.44_36.

2021/01/14 09:30:03 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2021/01/14 09:30:03 kid1| Starting Squid Cache version 4.10 for amd64-portbld-freebsd11.3...
2021/01/14 09:30:03 kid1| Service Name: squid

[viktor_g]

@a18g3 could you test it on the latest pfSense 2.5 snapshot?
it uses squid 4.13

[gko]

This is a known bug of squid and has been fixed since version 4.11 according to this.
https://redmine.pfsense.org/issues/10608

If someone can make a guide on how to update to the latest port of squid 4.13 using pfsense 2.4.5 p1 it would be really appreciated.

[viberua]

Before yesterday squid stop at once
2021/01/20 15:41:57 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
Yesterday twice stop working.
2021/01/21 14:51:33 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
I with stability press "Clear cache" button every day - is sad. Yesterday night i have updated to devel 2.5 version with squid-4.13. Will see how it will work.

[Volnei]

Hi,
Please remove the SOLVED flag for this problem as it has not been resolved.
I opened a new ticket in squid's bugzilla: Bug 5101 - assertion failed: http.cc:1533:
"!Comm::MonitorsRead(serverConnection->fd)" (edit)

Thank you.

[viberua]

With devel 2.5 version problem is solved.

[Volnei]

Ok.
I understand.
But unfortunately I've to use only the "stable" version of the production environment.

Anyway, I appreciate the information.

[tobyswe]

I wish Netgate would understand how serious this issue is. This forced me to buy 20 new fortigates in December The squid functionality is absolutely essential in todays network environment. I have 20 netgate routers on the sheld now not in use :-(

[tobyswe]

And why is this thread still considered as solved ??? Unfortunately i lost a lot of godwill in my organisation because i hade really promoted Pfsense as a good router solution. In the end there was no choice. I had to get rid of them. I could not have my team monitoring squid process 24 hours a day and restart it all the time. Really terrible.