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

    sg-1100 22.01->23.05.1-high memory ussage after upgrade

    Scheduled Pinned Locked Moved General pfSense Questions
    16 Posts 3 Posters 1.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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      No, in 23.05 they were merged, the two packages are identical.

      If you restart Unbound or pfBlocker does the usage change?

      L 1 Reply Last reply Reply Quote 0
      • L
        lrossi @stephenw10
        last edited by

        @stephenw10 I gave it a try but it didn't make a difference.

        I also disabled the "telegraph" package for a bit, as i remember having memory issues with it in the past, but this didn't help either. I then restarted the "nut" package, as i read another thread where a user was having memory problems with that package, but this didn't help either.

        For reference this is the memory graph for the last month. Can you guess where the update to 23.05.1 happened?Memory pfsense.png

        It seems that the active memory increased from roughly 5% to 25%.

        Do you happen to have any more ideas of things i could try?

        GertjanG 1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan @lrossi
          last edited by

          @lrossi

          I've seen this before on the forum :

          3ad56b23-b653-4413-93c6-5ad5acb57983-image.png

          but never on my own pfSense devices.

          Not that "Laundry" is bad, but the presence == not zero says to me : something doesn't go as planned.
          The laundry kernel process can't decide what to do with it. (last thread, last line).

          These stand out for me :

          HAProxy
          Telegraf
          

          because - don't laugh - I don't use them.
          A way to debug is : stop using them - and memory issues go away ?

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          L 1 Reply Last reply Reply Quote 0
          • L
            lrossi @Gertjan
            last edited by

            @Gertjan Thanks for the input. I disabled the Telegraf service for a bit, just to see it makes a difference, but nothing changed.

            About HAProxy, i will have to try tomorrow as the network users are starting to become active and they rely on that service for their normal operations.

            However, i'll be surprised if this is the problem since HAProxy is widely used and i have not seen anybody talking about its high memory use.

            1 Reply Last reply Reply Quote 0
            • L
              lrossi
              last edited by

              @Gertjan i hust stopped HAProxy for about 20 minutes and the memory usage didn't change.
              Do you happen to have any other suggestions of things i could try?

              My system is not crashing but i find it odd that it is using twice as much memory all of the sudden.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Mmm, if it's not actually climbing then it shouldn't be an issue. Interesting that it also shows far more variability. 🤔

                1 Reply Last reply Reply Quote 0
                • L
                  lrossi
                  last edited by

                  And just like that, the system started to behave as it did before the update (or similar).

                  I knew this forum was good, but i never imagined they could intimidate a system into fixing itself. Wow you guys are good.
                  pfsense 2023-08-01 1.png pfsense 2023-08-01 2.png

                  Even the variability that @stephenw10 noticed is gone. The situation with the "laundry" memory that @Gertjan saw is still there.

                  Now, what produced this behavior after the update? How it got fixed? I have learned to focus my time on problems and, right now, this is not one of them.

                  Thanks for trying to help.

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, odd! Nothing logged at that time?

                    L 1 Reply Last reply Reply Quote 0
                    • L
                      lrossi @stephenw10
                      last edited by

                      @stephenw10 per my estimation, the change happened on 7/31 between 7:20 AM and 7:40 AM

                      The logs between that time are nothing out of the ordinary

                      Jul 31 08:00:01 	php 	78976 	[pfBlockerNG] Starting cron process.
                      Jul 31 07:00:49 	php 	1559 	[pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
                      Jul 31 07:00:01 	php 	1559 	[pfBlockerNG] Starting cron process.
                      

                      Nothing else was logged during that period of time.

                      The only thing that concerns me is that I haven't seen any other reports of this on the SG-1100 which may implies there is something different and odd on my configuration or my hardware is starting to malfunction. Neither option is great.

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        I doubt it's a hardware issue causing memory use like that.

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