pkg-static consuming 100% cpu
-
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% ;)
-
@gonace said in Pkg-Static 100% CPU:
Kind of a big oversight that a failing update-server(s) can cause pfSense to hog a process at 100% ;)
Well the pkg system is part of FreeBSD, feel free to create a bug report at: https://bugs.freebsd.org
-
@grimson said in Pkg-Static 100% CPU:
@gonace said in Pkg-Static 100% CPU:
Kind of a big oversight that a failing update-server(s) can cause pfSense to hog a process at 100% ;)
Well the pkg system is part of FreeBSD, feel free to create a bug report at: https://bugs.freebsd.org
I'm not sure since I've not confirmed it on multiple machines, but I can't reproduce it under FreeBSD 11.2 (clean install) so I'm not sure if it's a bug in FreeBSD rather than something specific when running pfSense.
But yeah, just tried to reproduce it on one virtual machine.
-
@gonace said in Pkg-Static 100% CPU:
I'm not sure since I've not confirmed it on multiple machines, but I can't reproduce it under FreeBSD 11.2 (clean install) so I'm not sure if it's a bug in FreeBSD rather than something specific when running pfSense.
Well the FreeBSD servers aren't down.
-
@grimson said in Pkg-Static 100% CPU:
@gonace said in Pkg-Static 100% CPU:
I'm not sure since I've not confirmed it on multiple machines, but I can't reproduce it under FreeBSD 11.2 (clean install) so I'm not sure if it's a bug in FreeBSD rather than something specific when running pfSense.
Well the FreeBSD servers aren't down.
Well, I blocked traffic to them and even blocked access to the internet on FreeBSD 11.2 (clean install) and did the same with a clean install of pfSense and the problem only arises on the clean install of pfSense.
-
@p1ter It´s a handshake problem ;-)
-
The BSD servers might be up but blocking access to them upstream would be equivalent to them being down. Can someone try to do just that?
Definitely a very disturbing oversight, makes me wonder what other things received the same level of attention :) -
@artichost Thank you. I mean can I fix it by myself?
-
@veriqster said in Pkg-Static 100% CPU:
The BSD servers might be up but blocking access to them upstream would be equivalent to them being down.
That would make them completely unreachable, it currently looks like the pfSense servers hang/are very slow during the SSL negotiation which is a different situation. If you want to see the difference do a traffic capture instead of fooling around.
-
Hello from Brazil. Same here, pkg-static-update 100% usage cpu but the system looks functional.
-
Hello everyone,
I have the same problem but also the process /usr/local/sbin/pkg-static search -r to 100% -
I'm not an expert, but could one via ssh temporarily replace pkg-static with a shell script that basically does nothing? If so, can someone with more skills than myself show me the way?
-Chance -
then maybe someone should just pull the Ethernet plug out of them until things are sorted out instead of messing up with some systems that people depend on.
Honestly I would have said "shit happens, maybe they can just fix it going forward" but his attitude of leaving the servers on knowing it causes issues like this makes me wonder what other things are deemed as acceptable by "the man in charge", things that a dumb user like me might not be able grasp even by looking at the code (which I have neither time nor desire to dedicate myself to)
