<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
I have a local RPM repository that syncs from an internet mirror of
the CentOS 7.3 updates repository. When I try to create a local copy
of this mirror, the celery processes balloon, using all available
memory until the job eventually fails as follows:<br>
<br>
<tt>$ pulp-admin rpm repo copy all --from-repo-id
centos-7-updates-x86_64-live --to-repo-id
centos-7-updates-x86_64-snapshots-20170216a</tt><tt><br>
</tt><tt>This command may be exited via ctrl+c without affecting the
request.</tt><tt><br>
</tt><tt><br>
</tt><tt>[-]</tt><tt><br>
</tt><tt>Running...</tt><tt><br>
</tt><tt>An internal error occurred on the Pulp server:</tt><tt><br>
</tt><tt><br>
</tt><tt>RequestException: GET request on</tt><tt><br>
</tt><tt>/pulp/api/v2/tasks/776894cc-b524-4f2f-bd30-c8c4d8237c31/
failed with 500 -</tt><tt><br>
</tt><tt>[Errno 12] Cannot allocate memory</tt><tt><br>
</tt><br>
As often as not, this renders my Pulp VM inaccessible, requiring a
hard reset in order to access it again. This is Pulp 2.12.0 on
CentOS 7.2.1511. I presume this is the same issue described in
<a class="moz-txt-link-freetext" href="https://pulp.plan.io/issues/1779">https://pulp.plan.io/issues/1779</a>, but given 10 months since that
ticket was updated, I figured I'd ask here.<br>
<br>
I've tried setting PULP_MAX_TASKS_PER_CHILD=2 in
/etc/default/pulp_workers, but it doesn't seem to make any
difference.<br>
<br>
Is there a fix or workaround for this problem, or even a means to
estimate how much memory a server needs to be able to copy a repo of
a given size? This VM has 8GB, and I could add more, but it seems
faintly ridiculous that it should be required.<br>
<br>
Thanks,<br>
<div class="moz-signature">-- <br>
<div class="moz-signature">
<style type="text/css">
.smxsig {color: #828181; font-family: Segoe, Myriad Pro, Arial, sans-serif; font-size: 82%}
strong, :link, .halfstrong {color: #285BA7}
</style>
<p class="smxsig"> <strong>Richard Gray</strong> <span
class="halfstrong">| Operations Technical Lead</span> <br>
<strong>DDI:</strong> +64 9 950 2196 <strong>Fax:</strong>
+64 9 302 0518 <br>
<strong>Mobile:</strong> +64 21 050 8178 <strong>Freephone:</strong>0800
SMX SMX (769 769) <br>
<strong>SMX Limited:</strong> <span>Level 15, 19 Victoria
Street West, Auckland, New Zealand</span> <br>
<strong>Web:</strong> <a href="http://smxemail.com">http://smxemail.com</a>
<br>
<img src="http://smxemail.com/images/smxsig.png" alt="SMX |
Cloud Email Hosting & Security" moz-do-not-send="true"
vspace="4"> </p>
</div>
</div>
<div><div style="border-top-style: solid; border-top-width: 1px; border-top-color: black; border-bottom-style: solid; border-bottom-width: 1px; border-bottom-color: black; padding: 10px 0px; margin: 20px 0px; font-size: 9pt;"><span style="font-family: Verdana, Arial, Helvetica, sans-serif;">This email has been</span><font face="arial"><font face="Verdana, Arial, Helvetica, sans-serif"> filtered by SMX. For more information visit </font><a href="http://smxemail.com/" font-size:="" 9pt;"="">smxemail.com</a><font face="verdana">.<br></font></font></div>
</div>
</body>
</html>