pkg-static consuming 100% cpu
-
Did anyone ever find a solution to this problem? I've manually killed it and rebooted the router. pkg-static has been pinning one of the cores for going on 45 minutes now.
-
https://forum.netgate.com/topic/139905/solved-xg1537-cpu-load-jumped-up-but-no-culprit-to-be-found
-
@grimson if I'm understanding this correctly, I just wait for the server it's trying to contact to come back online?
-
@mouseskowitz said in Pkg-Static 100% CPU:
@grimson if I'm understanding this correctly, I just wait for the server it's trying to contact to come back online?
Yes, or until pkg-static gives up trying to contact the server.
-
Same problem over here.
-
Noticed in the dashboard CPU was running 50%+ (dual core VM in HyperV), and found the same thing happening with pkg-static maxing out one of the cores as well.
-
I would suggest following our Twitter feed; we will post updates there: https://twitter.com/NetgateUSA/status/1088455647807455232
-
not everyone has twitter stuff, nor wants to have that. why not updating in https://www.netgate.com/blog/? this way all could use the dashboard widget :). or, maybe have the tweeter feed linked to a widget? :D
-
We're seeing this issue as well, every time we navigate to the Package Manager in the GUI.
Pinning everyone's CPU cores if the update servers are down is not a great failure mechanism :-\
-
We're also seeing this right now. This is obviously a bug.
-
Same situation=-( Hello everybody
-
Same here. Just started doing it today. Earlier this week, I had to take action because 'rate' was consuming 100% CPU on both cores on my dual-core VM. Now today, pkg-static was pegging one core until I killed its pid.
-
Any temporary workarounds?
-
I bumped into this accidentally, while trying to install iperf to run some tests.
It actually messed up my /var/db/pkg files and the pkg has been compaining about them since. partially fixed by setting the branch to development and saving then reverting to stable and saving again but not certain it fixed the issue. pkg doesn't complain about not finding files but I see nothing under packages available for install and running pkg update spits errors after about 30 min of being stuck. 1 core pegged to 100% but the system is still operational and routing (hopefully as supposed).
Agree, NOT a great way to fail for ANY process, I would actually go as far as saying not an acceptable way; I'm yet to see any other OS fail to update in this way. -
None I am aware of. Process will return. Wait for the server to come up.
-
I bet all it takes to fix this is a couple of lines at the beginning of a certain file, something along the lines of " ping.......; if/while........; else "try again at another time when server is up and running".
Wondering if this applies to community edition only or paid members are affected as well. -
It's probably even simpler than that, this is a symptom of a common oversight.
-
Just update the certificate and reboot the server. ;-)
-
@artichost said in Pkg-Static 100% CPU:
Just update the certificate and reboot the server. ;-)
Sorry. I'm not shure I understand what you mean. Can you explain please?
-
Kind of a big oversight that a failing update-server(s) can cause pfSense to hog a process at 100% ;)
