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

    1100 upgrade, 22.05->23.01, high mem usage

    Scheduled Pinned Locked Moved General pfSense Questions
    74 Posts 12 Posters 46.3k 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.
    • J
      jrey @SteveITS
      last edited by

      @steveits

      i saw that too, was sure, because I couldn't remember if it was enable in prior version or not.
      @jimp suggests none of it was not enabled in prior version

      The change to crontab will for sure stop it and all the other reports it runs too.
      again out of the box the way it was configured no one would have seen them anyway ..

      There are 3 fixes that will alleviate the problem caused by the security reports.
      Dealers choice at this point.

      crontab is likely the best final solution since they say there is nothing else needed.

      All good. Cheers

      1 Reply Last reply Reply Quote 0
      • beerguzzleB
        beerguzzle
        last edited by

        I just applied patch ff715efce5e6c65b3d49dc2da7e1bdc437ecbf12 that was put out by the Netgate crew, see https://redmine.pfsense.org/issues/14016, and rebooted. Also see the discussion in the thread "23.1 using more RAM" about this patch.

        After reboot, wired mem dropped from 55% to 33% on my 1100. I'll check it in the morning to see what happened at 3 AM.

        Netgate 1100 and Netgate 2100, latest pfsense+ version

        MachasaChairaM 1 Reply Last reply Reply Quote 4
        • MachasaChairaM
          MachasaChaira @beerguzzle
          last edited by

          @beerguzzle Hello, my first comment here. Same situation, SG-1100 with 85% memory in constant use. I applied that patch and Memory usage dropped to 35% after rebooting.

          J 1 Reply Last reply Reply Quote 1
          • beerguzzleB
            beerguzzle
            last edited by

            Checking my system this morning after applying patch ff715efce5e6c65b3d49dc2da7e1bdc437ecbf12 and rebooting yesterday... Bliss! Nothing happened at 3 AM and my wired mem usage remains at about 35%. I consider this problem solved.

            Screenshot 2023-02-23 at 7.49.39 AM.png

            Netgate 1100 and Netgate 2100, latest pfsense+ version

            R 1 Reply Last reply Reply Quote 3
            • R
              rpsmith @beerguzzle
              last edited by

              Patch "ff715efce5e6c65b3d49dc2da7e1bdc437ecbf12" has completely resolved my SG-1100 memory problems!

              F 1 Reply Last reply Reply Quote 1
              • F
                FSC830 @rpsmith
                last edited by

                @rpsmith said in 1100 upgrade, 22.05->23.01, high mem usage:

                Patch "ff715efce5e6c65b3d49dc2da7e1bdc437ecbf12" has completely resolved my SG-1100 memory problems!

                +1
                ๐Ÿ˜Š
                Applied patch and rebootet yesterday at 8:00pm

                f6556b8f-56be-4a04-bd61-5ca50ebae3ee-grafik.png

                Regards

                M 1 Reply Last reply Reply Quote 1
                • M
                  mcury @FSC830
                  last edited by

                  @fsc830 Applied this patch in my SG-3100, everything OK, memory usage didn't change at night.
                  Thanks

                  dead on arrival, nowhere to be found.

                  1 Reply Last reply Reply Quote 1
                  • S SteveITS referenced this topic on
                  • J
                    JMV43 0 @MachasaChaira
                    last edited by

                    @machasachaira How do we apply the patch?

                    JMV

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      SteveITS Galactic Empire @JMV43 0
                      last edited by SteveITS

                      @jmv43-0 Install the System Patches package and use the patch ID.
                      https://docs.netgate.com/pfsense/en/latest/development/system-patches.html

                      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                      Upvote ๐Ÿ‘ helpful posts!

                      MachasaChairaM J 2 Replies Last reply Reply Quote 1
                      • MachasaChairaM
                        MachasaChaira @SteveITS
                        last edited by

                        @steveits I didn't know that way, I used the fetch command on the CLI to bring the file and replace the original.

                        Thanks.

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          SteveITS Galactic Empire @MachasaChaira
                          last edited by SteveITS

                          @machasachaira :) System Patches is relatively new (1-2 years), and a wonderful idea. Netgate publishes a list of Recommended patches for the version you're on. Updating that package updates the list of patches. Any patch with a commit ID can also be pulled in.

                          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                          Upvote ๐Ÿ‘ helpful posts!

                          1 Reply Last reply Reply Quote 2
                          • J
                            JMV43 0 @SteveITS
                            last edited by

                            @steveits Thanks

                            1 Reply Last reply Reply Quote 0
                            • M
                              mr.castoro
                              last edited by

                              Applied this patch 2 days ago. Absolutely solved the 3am memory leak. However, dns broke on my sg 1100 the past two days. I had to restart the dns resolver service to restore dns. Anyone else experiencing this?

                              S MachasaChairaM R 3 Replies Last reply Reply Quote 0
                              • S
                                SteveITS Galactic Empire @mr.castoro
                                last edited by

                                @mr-castoro There are a bunch of DNS threads lately.
                                If you have Resolver set to forward, ensure DNSSEC is unchecked.

                                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                                Upvote ๐Ÿ‘ helpful posts!

                                1 Reply Last reply Reply Quote 0
                                • MachasaChairaM
                                  MachasaChaira @mr.castoro
                                  last edited by

                                  @mr-castoro Have you restarted your SG after the patch update? I have not experienced any problems after rebooting.

                                  M 1 Reply Last reply Reply Quote 0
                                  • M
                                    mr.castoro @MachasaChaira
                                    last edited by

                                    @machasachaira yes, several times

                                    1 Reply Last reply Reply Quote 0
                                    • R
                                      rpsmith @mr.castoro
                                      last edited by rpsmith

                                      @mr-castoro -- No problems with my SG-1100 and DNS but I use the "Forwarder" and not the "Resolver" and I point the Forwarder to my two Pi-hole IPs. Works great that way!

                                      Also, instead of pointing it to a Pi-hole, you could just use: 9.9.9.9, 1.1.1.1 or 8.8.8.8 or some other external DNS.

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