pkg-static update using 100% cpu. What is broke?
-
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
-
I solved it by disabling dashboard update check and then rebooting the firewall.
-
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
-
@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%.
-
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
-
I haven't tried. I will test that when I have some time to be physically near the router.
-
@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.
-
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
-
@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.
-
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.
-
@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?
-
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.
-
@Derelict I ordered one. Guess we'll see what that does.
