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.5k Views
    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.
    • M
      mdalacu
      last edited by

      I have the same problem and it is driving me nuts. Every day when office hours begins, squid crashes with this error. On 2.4.4p3 suid was rock solid...:/
      The only thing i could do from UI is to delete the cache and then squid starts, otherwise it will not start from services.
      I have no DNS issues.

      
2020-07-31 08:46:56 [45559] loading dbfile /var/db/squidGuard/Misc/domains.db
2020-07-31 08:46:56 [45559] logfile not allowed in acl other than default
2020/07/31 09:02:56 kid1| assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd)"
2020/07/31 09:02:56 kid1| Starting Squid Cache version 4.10 for amd64-portbld-freebsd11.3...
2020/07/31 09:02:56 kid1| Service Name: squid
2020-07-31 09:02:56 [53246] (squidGuard): can't write to logfile /var/log/squidGuard/squidGuard.log
2020-07-31 09:02:56 [53246] New setting: logdir: /var/squidGuard/log
2020-07-31 09:02:56 [53246] New setting: dbhome: /var/db/squidGuard
2020-07-31 09:02:56 [53246] init domainlist /var/db/squidGuard/blk_blacklists_ads/domains
2020-07-31 09:02:56 [53246] loading dbfile /var/db/squidGuard/blk_blacklists_ads/domains.db
2020-07-31 09:02:56 [53246] init urllist /var/db/squidGuard/blk_blacklists_ads/urls


      
Jul 31 09:02:56 	kernel 		pid 43401 (squid), jid 0, uid 100: exited on signal 6
Jul 31 09:02:57 	kernel 		pid 52412 (squid), jid 0, uid 100: exited on signal 6
Jul 31 09:02:58 	kernel 		pid 55101 (squid), jid 0, uid 100: exited on signal 6
Jul 31 09:02:59 	kernel 		pid 58638 (squid), jid 0, uid 100: exited on signal 6
Jul 31 09:03:00 	kernel 		pid 61188 (squid), jid 0, uid 100: exited on signal 6
Jul 31 09:03:01 	kernel 		pid 63750 (squid), jid 0, uid 100: exited on signal 6
Jul 31 09:03:17 	Squid_Alarm 	68674 	Squid has exited. Reconfiguring filter.
Jul 31 09:03:17 	Squid_Alarm 	68975 	Attempting restart...
Jul 31 09:03:20 	Squid_Alarm 	71372 	Reconfiguring filter...
Jul 31 09:03:20 	check_reload_status 		Reloading filter
Jul 31 09:03:22 	php-fpm 	28232 	/rc.filter_configure_sync: [squid] Installed but not started. Not installing 'nat' rules.
Jul 31 09:03:22 	php-fpm 	28232 	/rc.filter_configure_sync: [squid] Installed but not started. Not installing 'pfearly' rules.
Jul 31 09:03:22 	php-fpm 	28232 	/rc.filter_configure_sync: [squid] Installed but not started. Not installing 'filter' rules.

      Help please.. 😰

      1 Reply Last reply Reply Quote 1
      • V
        vijay7
        last edited by

        @madalacu were you able to resolve this, I am started getting this issue, became a nightmare for me, please help

        M 1 Reply Last reply Reply Quote 0
        • M
          mdalacu @vijay7
          last edited by

          @vijay7 Try to update the squid package to the latest version and see...
          For me the problem remains but squid threads are able to restart in the latest version.. so it is working...

          1 Reply Last reply Reply Quote 0
          • V
            vijay7
            last edited by

            Tried that already, no difference, atleast twice a day squid service is stopping.

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

              Hello all

              This is absolutely NOT a solved problem. Someone should change this. I have several netgate devices with SQUID and SQUIDGARD installed. All of them has this problem. The SQUID service along with the SQUIDGARD service stops several times a day. I have been using SQUID /SQUIDGARD since 2015 . This problem started in 2019 after an upgrade. With the latest upgrade of Pfsense firmware and SQUID /SQUIDGARD it has become terrible. I have to manually start the services several times a day. For us using pfsense without SQUID is not an option and my staff is really questioning why we continue with netgate. The above solutions was not a solution for us. Its still the same.
              The error message in SQUID logs
              assertion failed: http.cc:1533: "!Comm::MonitorsRead(serverConnection->fd):
              Does anyone has any idea of this. I would hate for the first time in a very long time to be forced to go to other routers.

              /Toby

              V 1 Reply Last reply Reply Quote 1
              • M
                mdalacu
                last edited by

                Again last week was terrible for me..same problem...i was gessing sites and blindly blacklisted them trying to solve this problem...it's a never ending storry.
                Very very annoying and time consuming!

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

                  Can you test it on the latest 2.5 snapshot?

                  1 Reply Last reply Reply Quote 0
                  • V
                    vijay7
                    last edited by

                    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.

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

                            Is this issue fixed yet?

                            Never Fear, A Geek is Here!

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

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

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

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

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • V
                                    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
                                      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
                                        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
                                          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
                                            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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.