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

    CPU Usage Pegging out

    Scheduled Pinned Locked Moved General pfSense Questions
    13 Posts 5 Posters 6.6k 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.
    • L
      Leoandru
      last edited by

      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.

      1 Reply Last reply Reply Quote 0
      • L
        Leoandru
        last edited by

        I just thought that you can try to init the system without rebooting.

        killall dhclient && /bin/sh /etc/rc

        1 Reply Last reply Reply Quote 0
        • S
          sullrich
          last edited by

          Use the Status -> Interfaces, Release/Renew button.

          1 Reply Last reply Reply Quote 0
          • J
            Jesse7
            last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • Y
              yoda715
              last edited by

              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)
              processes.GIF
              ![cpu peg 3.GIF_thumb](/public/imported_attachments/1/cpu peg 3.GIF_thumb)
              processes.GIF_thumb
              ![cpu peg 3.GIF_thumb](/public/imported_attachments/1/cpu peg 3.GIF_thumb)
              processes.GIF_thumb

              1 Reply Last reply Reply Quote 0
              • H
                hoba
                last edited by

                Do a fresh reinstall with beta2.

                1 Reply Last reply Reply Quote 0
                • S
                  sullrich
                  last edited by

                  FYI: And that means reinstalling, not trying to do an upgrade.

                  1 Reply Last reply Reply Quote 0
                  • Y
                    yoda715
                    last edited by

                    yep, I'll try that and see how things go

                    1 Reply Last reply Reply Quote 0
                    • Y
                      yoda715
                      last edited by

                      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)
                      putty.GIF
                      ![cpu load.GIF_thumb](/public/imported_attachments/1/cpu load.GIF_thumb)
                      putty.GIF_thumb
                      ![cpu load.GIF_thumb](/public/imported_attachments/1/cpu load.GIF_thumb)
                      putty.GIF_thumb

                      1 Reply Last reply Reply Quote 0
                      • S
                        sullrich
                        last edited by

                        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.

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