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

    Two Error Messages

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    18 Posts 7 Posters 2.2k 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.
    • ?
      Guest
      last edited by

      Not the same problem then. Yours sounds like the  502 error.

      1 Reply Last reply Reply Quote 0
      • S
        strangegopher
        last edited by

        I have updated ntopng, suricata and pfblocker (twice) and the error still exists.

        I have noticed this error occurs after system comes online and for some reason the modem disconnects for a few seconds and then reconnects.

        Did not have this error when I was testing the RC builds. Only difference is that I have installed ntopng

        1 Reply Last reply Reply Quote 0
        • P
          PiBa
          last edited by

          Made a little fix to retry the command when pf is apparently 'busy' processing commands from another program: https://github.com/pfsense/pfsense/pull/3857

          It seems to be related to this issue reported on FreeBSD 10.4 where also a 'retry' is advised as the proper thing to do.
          https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223093

          Still probably ignoring the 'messages' doesn't hurt, but the actions taken by code will now hopefully be a bit more 'clean' once the PR is pulled.

          1 Reply Last reply Reply Quote 0
          • S
            strangegopher
            last edited by

            @PiBa:

            Made a little fix to retry the command when pf is apparently 'busy' processing commands from another program: https://github.com/pfsense/pfsense/pull/3857

            It seems to be related to this issue reported on FreeBSD 10.4 where also a 'retry' is advised as the proper thing to do.
            https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223093

            Still probably ignoring the 'messages' doesn't hurt, but the actions taken by code will now hopefully be a bit more 'clean' once the PR is pulled.

            Great detective work there. I hope to see the fix soon.

            1 Reply Last reply Reply Quote 0
            • R
              rscrub
              last edited by

              This is the same problem I have. It basically bricks my firewall and the internet. When I wake up in the morning I will have like 140 notifications, the same ones listed above.

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

                Since updating to 2.4.2 and updating the various applications this problem appears to be solved. Much thanks to all the developers who had a hand in this.

                Now, lets get to the bottom of why my WiFi connection keeps getting dropped along with the 502 error!

                1 Reply Last reply Reply Quote 0
                • MikeV7896M
                  MikeV7896
                  last edited by

                  @Teken:

                  Now, lets get to the bottom of […] the 502 error!

                  Do you run pfBlockerng? There appears to be an issue with it that causes the 502 error.

                  https://forum.pfsense.org/index.php?topic=137103.msg767259#msg767259

                  The S in IOT stands for Security

                  1 Reply Last reply Reply Quote 0
                  • P
                    PiBa
                    last edited by

                    just fyi: pfBlockerNG 2.1.2_2 includes that patch.

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

                      @virgiliomi:

                      @Teken:

                      Now, lets get to the bottom of […] the 502 error!

                      Do you run pfBlockerng? There appears to be an issue with it that causes the 502 error.

                      https://forum.pfsense.org/index.php?topic=137103.msg767259#msg767259

                      Yes, I've been tracking that ongoing thread since it was created. Looking forward to root cause being identified and a fix issued.

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

                        @PiBa:

                        just fyi: pfBlockerNG 2.1.2_2 includes that patch.

                        Noted, and thank you!

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