Project

General

Profile

Actions

Bug #12392

closed

100% cpu usage on foreman-proxy DHCP calls

Added by Matt Jarvis over 8 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

At least since 1.8, the cpu usage on the foreman-proxy has been increasing massively. We now see it using 100% of cpu time, although it does appear to still be running as it's logging stuff, it's extremely slow and we see timeouts communicating with it. This is using Bind and isc-dhcp-server, and strangely restarting all of the daemons and the proxy itself seems to fix it for a while. I've tried upgrading to the latest git code, and this doesn't make any difference.


Files


Related issues 3 (0 open3 closed)

Related to Smart Proxy - Bug #12359: 100% cpu usage foreman-proxy after upgrade to 1.9Resolved10/31/2015Actions
Related to Smart Proxy - Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy)Closed06/20/2013Actions
Related to Foreman - Bug #12425: Fact import triggers ip conflicts checks, which drives cpu utilization to 100% on smart-proxyClosedTimo GoebelActions
Actions

Also available in: Atom PDF