Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Builds fail on build-osuosl-ppc64-aix-71-2 with Too many processes #1151

Closed
lumpfish opened this issue Feb 19, 2020 · 2 comments · Fixed by adoptium/temurin-build#1555
Closed
Assignees
Labels
Milestone

Comments

@lumpfish
Copy link

Builds are failing on build-osuosl-ppc64-aix-71-2 with 'too many processes' messages - e.g. https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk14/job/jdk14-aix-ppc64-openj9/10/console

/opt/IBM/xlC/16.1.0/bin/xlclang++  -I../../tools/tracegen  -I../../../include -I../../include_core -I../../nls -DPPC64 -D_XOPEN_SOURCE_EXTENDED=1 -D_ALL_SOURCE -DRS6000 -DAIXPPC -D_LARGE_FILES -c  -s -q64 -qlanglvl=extended0x -qarch=ppc -qalias=noansi -qxflag=LTOL:LTOL0 -qsuppress=1506-1108 -qxlcompatmacros -fno-exceptions -fno-rtti -O3 -qhalt=w -g   -o FileUtils.o ../../tools/tracegen/FileUtils.cpp
/opt/IBM/xlC/16.1.0/bin/.orig/xlclang++: error: 1501-222 cannot fork process - Resource temporarily unavailable
1586-495 (U) SYSTEM LIMIT EXCEEDED: Too many processes are active.
../../omrmakefiles/rules.mk:379: recipe for target 'FileUtils.o' failed
gmake[6]: *** [FileUtils.o] Error 254
@sxa sxa self-assigned this Feb 19, 2020
@sxa sxa added the bug label Feb 19, 2020
@sxa sxa added this to TODO in infrastructure via automation Feb 19, 2020
@sxa sxa added this to the February 2020 milestone Feb 19, 2020
@sxa
Copy link
Member

sxa commented Feb 19, 2020

This seems mostly (though not 100%) repeatable - the load is runnign at about 10 at the time it crashes (although it peaks at about 20 previously).

I'm going to try limiting the amount of RAM the job thinks it has and see what happens. The process ulimit on the machine/jenkins user is unlimited

@sxa
Copy link
Member

sxa commented Feb 19, 2020

Paging space is 4Gb on these machines which is quite low compared to the 32Gb of RAM the build machines have (16Gb taken by ramdisk)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants