[opensuse-buildservice] vfork resource temporarily unavailable cause build failures
Hi, on a private OBS instance after introducing change root workers based on SLES12 hosts some builds failed with above errors. The reason was the task limit (500) enforced from systemd, the solution was to set it via the service definition for the worker to unlimited. This did help until I changed the worker type from change root to KVM. Now I got build failures again with the same message. I do not understand why, because the build target system is not systemd based at all (SLES11) so the here should not be such a small limit as SLES12 SP2 had (500) inside the VM ? Does this be a common issue on KVM workers with a higher number of VCPUs (12) ? Any idea how to solve this ? Best regards Karsten -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 6. September 2017, 07:51:29 CEST wrote Karsten Keil:
Hi,
on a private OBS instance after introducing change root workers based on SLES12 hosts some builds failed with above errors. The reason was the task limit (500) enforced from systemd, the solution was to set it via the service definition for the worker to unlimited. This did help until I changed the worker type from change root to KVM. Now I got build failures again with the same message. I do not understand why, because the build target system is not systemd based at all (SLES11) so the here should not be such a small limit as SLES12 SP2 had (500) inside the VM ?
Does this be a common issue on KVM workers with a higher number of VCPUs (12) ? Any idea how to solve this ?
IIRC this limitation gets applied in standard initrd. We solved this inside the initrd of kernel-obs-build package some time ago. Do you have the distros configured to use that one? -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi, Am 06.09.2017 um 08:00 schrieb Adrian Schröter:
On Mittwoch, 6. September 2017, 07:51:29 CEST wrote Karsten Keil:
Hi,
on a private OBS instance after introducing change root workers based on SLES12 hosts some builds failed with above errors. The reason was the task limit (500) enforced from systemd, the solution was to set it via the service definition for the worker to unlimited. This did help until I changed the worker type from change root to KVM. Now I got build failures again with the same message. I do not understand why, because the build target system is not systemd based at all (SLES11) so the here should not be such a small limit as SLES12 SP2 had (500) inside the VM ?
Does this be a common issue on KVM workers with a higher number of VCPUs (12) ? Any idea how to solve this ?
IIRC this limitation gets applied in standard initrd. We solved this inside the initrd of kernel-obs-build package some time ago.
Do you have the distros configured to use that one?
Thanks Adrian. I do not did anything special related to the kernel-obs-build package so I think our instance is not using it. I did not found anything about this in the documentation (maybe looked at the wrong place), so what is needed to enable the distros to use it ? I only found kernel-obs-build packages for SLE12, but no one for SLE11 ? Thanks Karsten -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi Karsten, On 07.09.2017 06:32, Karsten Keil wrote:
Hi,
Am 06.09.2017 um 08:00 schrieb Adrian Schröter:
On Mittwoch, 6. September 2017, 07:51:29 CEST wrote Karsten Keil:
I changed the worker type from change root to KVM. Now I got build failures again with the same message. I do not understand why, because the build target system is not systemd based at all (SLES11) so the here should not be such a small limit as SLES12 SP2 had (500) inside the VM ?
IIRC this limitation gets applied in standard initrd. We solved this inside the initrd of kernel-obs-build package some time ago.
Do you have the distros configured to use that one?
Thanks Adrian. I do not did anything special related to the kernel-obs-build package so I think our instance is not using it.
I did not found anything about this in the documentation (maybe looked at the wrong place), so what is needed to enable the distros to use it ?
I only found kernel-obs-build packages for SLE12, but no one for SLE11 ?
There is no kernel-obs-build fpr SLES11, only SLES12 upwards. I have built a kernel-obs-build for CentOS7 (to be able to build CentOS kiwi images in OBS) some time ago, documented it here: http://seifesrants.blogspot.de/2015/11/use-your-distros-kernel-in-obs.html You might be able to do the same with a SLES11 kernel. But I don't think this is really related. You boot the SLES11 build VM with the SLES12 kernel now and it fails. You could retry this with a SLES11SP2 kernel on your worker (even a SLES12 worker should be able to boot with the SLES11SP2 kernel, it should be new enough). You do not even need to boot the worker with the SP2 kernel, just use OBS_VM_KERNEL and OBS_VM_INITRD to point to the SP2 kernel. *If* this test shows that your build works with the SLES11 kernel but fails with the SLES12 kernel, we need to investigate further (put "ulimit -a" into a %prep section and check for differences in the output). Good luck :-) Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi Seife, Am 07.09.2017 um 08:55 schrieb Stefan Seyfried:
Hi Karsten,
On 07.09.2017 06:32, Karsten Keil wrote:
Hi,
Am 06.09.2017 um 08:00 schrieb Adrian Schröter:
On Mittwoch, 6. September 2017, 07:51:29 CEST wrote Karsten Keil:
I changed the worker type from change root to KVM. Now I got build failures again with the same message. I do not understand why, because the build target system is not systemd based at all (SLES11) so the here should not be such a small limit as SLES12 SP2 had (500) inside the VM ?
IIRC this limitation gets applied in standard initrd. We solved this inside the initrd of kernel-obs-build package some time ago.
Do you have the distros configured to use that one?
Thanks Adrian. I do not did anything special related to the kernel-obs-build package so I think our instance is not using it.
I did not found anything about this in the documentation (maybe looked at the wrong place), so what is needed to enable the distros to use it ?
I only found kernel-obs-build packages for SLE12, but no one for SLE11 ?
There is no kernel-obs-build fpr SLES11, only SLES12 upwards.
I have built a kernel-obs-build for CentOS7 (to be able to build CentOS kiwi images in OBS) some time ago, documented it here: http://seifesrants.blogspot.de/2015/11/use-your-distros-kernel-in-obs.html
You might be able to do the same with a SLES11 kernel.
But I don't think this is really related. You boot the SLES11 build VM with the SLES12 kernel now and it fails. You could retry this with a SLES11SP2 kernel on your worker (even a SLES12 worker should be able to boot with the SLES11SP2 kernel, it should be new enough). You do not even need to boot the worker with the SP2 kernel, just use OBS_VM_KERNEL and OBS_VM_INITRD to point to the SP2 kernel.
This cause build failure directly after the VM starts for a SLE11 build with an error that some lib is missing - I think at least I have to generate an initrd with the SLE11 packages.
*If* this test shows that your build works with the SLES11 kernel but fails with the SLES12 kernel, we need to investigate further (put "ulimit -a" into a %prep section and check for differences in the output).
Will look at this after I get around the missing lib error.
Good luck :-)
Stefan
Thanks Karsten -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Karsten Keil -
Stefan Seyfried