CPU Usage Pegging out
-
Thats the dhcp client, it assigning you (pfSense interfaces configured with dhcp) a dynamic address. dhcpd is what assigns your client's ip addresses.
I don't know how to restart the dhcpclient yet. I guess Scott or someone else could tell how, if you don't want to lose your uptime. -
I just thought that you can try to init the system without rebooting.
killall dhclient && /bin/sh /etc/rc
-
Use the Status -> Interfaces, Release/Renew button.
-
I get this happening almost everytime I use the upgrade option instead of fresh installing. As soon as I upgrade the cpu sits on max. Doesn't happen everytime I've upgraded. Latest time being one of those times it is working correctly.
-
It happened again :-\ Although this time it is two different processes chewing up the cpu usage. One thing to note is the syslog is taking up a good bit of usage, yet I do not have syslog enabled. Does that process run even when you are not using syslog to a remote server?
![cpu peg 3.GIF](/public/imported_attachments/1/cpu peg 3.GIF)
![cpu peg 3.GIF_thumb](/public/imported_attachments/1/cpu peg 3.GIF_thumb)
![cpu peg 3.GIF_thumb](/public/imported_attachments/1/cpu peg 3.GIF_thumb)
-
Do a fresh reinstall with beta2.
-
FYI: And that means reinstalling, not trying to do an upgrade.
-
yep, I'll try that and see how things go
-
Well I loaded beta 2 from a fresh install and I have not had the cpu usage peg to 100%, however it is constantly staying at 4-6% usage now. The cpu used to never stay at 4-6% before beta 2 (at least before it pegged out). I am running 1.2ghz Athlon and I don't see how anything should be using 4-6%. So I logged into shell and looked and low and behold its the Dhclient again. Its not pegging it out, but it is eating up some resources. Is this to be expected?
![cpu load.GIF](/public/imported_attachments/1/cpu load.GIF)
![cpu load.GIF_thumb](/public/imported_attachments/1/cpu load.GIF_thumb)
![cpu load.GIF_thumb](/public/imported_attachments/1/cpu load.GIF_thumb)
-
A number of people have been complaining about these problems on the FreeBSD lists. It's somewhat a known by not known problem.
The dhclient maintainer seems to think there are some edge cases left in the client. Please describe in more detail your isp setup and what options the isp are pushing to you.