• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
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 Oct 19, 2017, 6:40 AM

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

    1 Reply Last reply Reply Quote 0
    • S
      strangegopher
      last edited by Oct 21, 2017, 9:40 PM

      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 Oct 22, 2017, 7:24 PM

        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 Oct 26, 2017, 2:28 AM

          @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 Nov 8, 2017, 3:30 AM

            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 Dec 7, 2017, 5:31 PM

              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
              • M
                MikeV7896
                last edited by Dec 10, 2017, 12:35 AM

                @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 Dec 10, 2017, 12:54 AM

                  just fyi: pfBlockerNG 2.1.2_2 includes that patch.

                  1 Reply Last reply Reply Quote 0
                  • T
                    Teken
                    last edited by Dec 11, 2017, 3:07 AM

                    @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 Dec 11, 2017, 3:08 AM

                      @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.
                        This community forum collects and processes your personal information.
                        consent.not_received