Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 28 subscribers
  • Views 5729 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

/bin/networkd process has CPU pegged

Matt Zuba

This morning I woke up to an XG at home that would not hand out DHCP leases to any scopes.  I tried logging into the web console to no avail (like now, web console is inaccessible).  Was able to SSH in and ran 'top' on the Advanced shell and saw that networkd was eating up the CPU.  Rebooted the XG and it worked fine for a little bit and then it spiked again and it's been that way since.  Checking the CPU charts, there's a distinct spike when it started.  How can I analyze what's causing this and get it fixed?  I recently upgraded to v17 on Friday and it was fine Saturday and Sunday.



This thread was automatically locked due to age.
Parents
  • 0

    Bumpity - this keeps happening on a semi-regular basis.  networkd goes up to 100% cpu on two cores and prevents DHCP leases from being handed out and I can't log into the web gui.  Even though I can SSH in, I can't issue a reboot command, my only recourse is to physically power down the device and restart it.  Any hints on where to being troubleshooting this?

Reply
  • 0

    Bumpity - this keeps happening on a semi-regular basis.  networkd goes up to 100% cpu on two cores and prevents DHCP leases from being handed out and I can't log into the web gui.  Even though I can SSH in, I can't issue a reboot command, my only recourse is to physically power down the device and restart it.  Any hints on where to being troubleshooting this?

Children