Description of problem:
satellite installer disables Pulp_max_tasks_per_child in the capsule by default, but it does not disable in the satellite.
Fresh install system with satellite installed
Ran satellite-installer -scenario=satellite
In capsule server /etc/default/pulp_workers Pulp_max_tasks_per_child is commented
In satellite server /etc/default/pulp_workers Pulp_max_tasks_per_child is uncommented
This leads to memory leaks on the capsule server
*** Bug 1643650 has been marked as a duplicate of this bug. ***
Verified fix in sat 6.5 snap 11.
Pulp workers is commented by default during satellite install:
# To avoid memory leaks, Pulp can terminate and replace a worker after processing X tasks. If
# left commented, process recycling is disabled. PULP_MAX_TASKS_PER_CHILD must be > 0.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25511 has been resolved.
We removed all instances of the configuration for PULP_MAX_TASKS_PER_CHILD as this configuration is no longer supported as it leads to deadlocks in task processing, see:
if you are still seeing PULP_MAX_TASKS_PER_CHILD entries in /etc/default/pulp_workers on a Satellite or Capsule then that bug is not resolved but in our tests and internal lab hosts on fresh installations of Satellite and Capsules there is no more PULP_MAX_TASKS_PER_CHILD setting which is correct.
Going to close this out as CURRENTRELEASE but if you are seeing this configuration entry still, please re-open.