Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

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

    Scheduled Pinned Locked Moved Cache/Proxy
    35 Posts 10 Posters 7.7k Views 10 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V Offline
      viberua
      last edited by

      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?

      1 Reply Last reply Reply Quote 0
      • T Offline
        tobyswe
        last edited by

        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

        1 Reply Last reply Reply Quote 1
        • V Offline
          viberua
          last edited by

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

          1 Reply Last reply Reply Quote 0
          • A Offline
            aGeekhere
            last edited by

            Is this issue fixed yet?

            Never Fear, A Geek is Here!

            1 Reply Last reply Reply Quote 0
            • viktor_gV Offline
              viktor_g Netgate
              last edited by

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

              1 Reply Last reply Reply Quote 0
              • V Offline
                viberua @tobyswe
                last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • V Offline
                  Volnei
                  last edited by

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • V Offline
                    Volnei
                    last edited by

                    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 -

                    V A 2 Replies Last reply Reply Quote 1
                    • V Offline
                      vijay7 @Volnei
                      last edited by

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

                      1 Reply Last reply Reply Quote 0
                      • V Offline
                        Volnei
                        last edited by

                        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.

                        1 Reply Last reply Reply Quote 1
                        • A Offline
                          A18G3 @Volnei
                          last edited by

                          @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_gV 1 Reply Last reply Reply Quote 0
                          • viktor_gV Offline
                            viktor_g Netgate @A18G3
                            last edited by

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

                            1 Reply Last reply Reply Quote 0
                            • G Offline
                              gko
                              last edited by

                              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.

                              1 Reply Last reply Reply Quote 0
                              • V Offline
                                viberua
                                last edited by 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.

                                V 1 Reply Last reply Reply Quote 0
                                • V Offline
                                  Volnei
                                  last edited by

                                  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.

                                  1 Reply Last reply Reply Quote 0
                                  • V Offline
                                    viberua @viberua
                                    last edited by

                                    With devel 2.5 version problem is solved.

                                    1 Reply Last reply Reply Quote 0
                                    • V Offline
                                      Volnei
                                      last edited by

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

                                      Anyway, I appreciate the information.

                                      1 Reply Last reply Reply Quote 0
                                      • T Offline
                                        tobyswe
                                        last edited by

                                        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 :-(

                                        1 Reply Last reply Reply Quote 1
                                        • T Offline
                                          tobyswe
                                          last edited by

                                          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.

                                          1 Reply Last reply Reply Quote 0
                                          • viktor_gV Offline
                                            viktor_g Netgate
                                            last edited by

                                            Squid version in pfSense 2.5/21.02 is 4.13:

                                            [2.5.0-RELEASE][root@xxx]/root: pkg info squid
squid-4.13
Name           : squid
Version        : 4.13

                                            please test and leave your comment on https://redmine.pfsense.org/issues/10608

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.