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

    pkg-static update using 100% cpu. What is broke?

    Scheduled Pinned Locked Moved General pfSense Questions
    14 Posts 3 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.
    • RedDelPaPaR
      RedDelPaPa
      last edited by RedDelPaPa

      noticed recently pkg-static update is using 97-100% cpu non stop on an SG-3100 box.

      What's broken? Unacceptable. Need to fix this.
      2b5bf0bc-1484-4cf6-8df4-6e86051d6597-image.png
      fa17311e-ac85-4eb6-b84f-81ae6da20790-image.png

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

        The only time I've seen that before is when there was an issue with the package servers. I'm aware of one recently though, has that been stuck like that for some time?
        I would kill that process and run the update check, menu option 13, at the console where any errors will be reported.

        Steve

        1 Reply Last reply Reply Quote 0
        • RedDelPaPaR
          RedDelPaPa
          last edited by

          I solved it by disabling dashboard update check and then rebooting the firewall.

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

            If it failed at the dashboard check I would expect it to fail when you check for packages or manually check for an update. You should solve that now before it becomes pressing.

            Steve

            RedDelPaPaR 1 Reply Last reply Reply Quote 0
            • RedDelPaPaR
              RedDelPaPa @stephenw10
              last edited by

              @stephenw10 I have no idea what is actually wrong, I just read a forum post suggesting that the problem was caused from the update servers and so I disabled the dashboard check as recommended, rebooted, and the issue appears resolved. I would suspect that the actual problem is the pfsense firewall coding itself. If the update app cannot perform its function, then it should abort its update check and not perpetually spike cpu usage to near 100%.

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

                Well I would mostly agree with that, it shouldn't get stuck at 100% like that. But without knowing what the error is it's impossible to say further. Are you able to check for packages and update correctly now?

                Steve

                RedDelPaPaR 1 Reply Last reply Reply Quote 0
                • RedDelPaPaR
                  RedDelPaPa
                  last edited by

                  I haven't tried. I will test that when I have some time to be physically near the router.

                  1 Reply Last reply Reply Quote 0
                  • RedDelPaPaR
                    RedDelPaPa @stephenw10
                    last edited by

                    @stephenw10 So I messed up my config and had to restore a backup config last night. The restore worked, but now pfsense still has my cpu pegged at 100% for hours on end trying to reinstall the few critical packages that I had running.

                    This is friggen unbelievable. I'm within an inch of throwing this pfsense box in the dumpster and buying a firewall/router solution that actually works.

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

                      Was it updating from the command line and able to see packages after the reinstall but before you restored the config?
                      If so I would be looking for something in the config that is preventing access to the pkg server.

                      Steve

                      RedDelPaPaR 1 Reply Last reply Reply Quote 0
                      • RedDelPaPaR
                        RedDelPaPa @stephenw10
                        last edited by

                        @stephenw10 So just this morning I have discovered that if I just keep retrying to install packages, it will finally succeed after about 50 tries. This leads me to believe that the package updater utility is horribly inadequate.

                        1 Reply Last reply Reply Quote 0
                        • DerelictD
                          Derelict LAYER 8 Netgate
                          last edited by

                          Whatever you are seeing is unique to you.

                          We need to find out what you are doing that nobody else in the world is doing.

                          Or what is unique to your environment when compared to everybody else in the world.

                          Chattanooga, Tennessee, USA
                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                          RedDelPaPaR 1 Reply Last reply Reply Quote 0
                          • RedDelPaPaR
                            RedDelPaPa @Derelict
                            last edited by

                            @Derelict Well, I don't think it could be anything past the router. If it's a connection issue, it would have to be at the firewall, dsl modem, or my ISP, I would think. Or, possibly failing storage?

                            1 Reply Last reply Reply Quote 0
                            • DerelictD
                              Derelict LAYER 8 Netgate
                              last edited by

                              Perhaps. Grab a cheap M.2, install to it, restore the backup config, and see if things change.

                              You generally get error messages in the system log for failing storage but you might be experiencing something different.

                              Chattanooga, Tennessee, USA
                              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                              Do Not Chat For Help! NO_WAN_EGRESS(TM)

                              RedDelPaPaR 1 Reply Last reply Reply Quote 0
                              • RedDelPaPaR
                                RedDelPaPa @Derelict
                                last edited by

                                @Derelict I ordered one. Guess we'll see what that does.

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