Bug 1110162
| Summary: | Attempt to create jbosseap-6 application on OpenShift Enterprise 2.1 fails, coredump mentioned | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jan Pazdziora (Red Hat) <jpazdziora> |
| Component: | Containers | Assignee: | Brenton Leanhardt <bleanhar> |
| Status: | CLOSED DUPLICATE | QA Contact: | libra bugs <libra-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.1.0 | CC: | jialiu, jokerman, jpazdziora, libra-onpremise-devel, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-25 08:20:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I confirm that increasing limits_nproc=250 to limits_nproc=500 and restarting service ruby193-mcollective restart resolved the issue for me. Change of memory_limit_in_bytes or memory_memsw_limit_in_bytes was not needed. https://bugzilla.redhat.com/show_bug.cgi?id=1043412#c4 already mentioned that, so I will close this bug as DUPLICATE. *** This bug has been marked as a duplicate of bug 1043412 *** (In reply to Johnny Liu from comment #11) > https://bugzilla.redhat.com/show_bug.cgi?id=1043412#c4 already mentioned > that, so I will close this bug as DUPLICATE. Well, I tried to point out the fact that at least in my situation, memory_*limit_in_bytes settings plays no role. I guess BZ#1043412 has the same situation as yours, we did not point out that clearly, thanks for your clarification. |
Description of problem: On fresh OpenShift Enterprise 2.1 installed with openshift.sh and passing oo-diagnostics, I see perl-5.10 created without any issues but running commands like rhc create-app -n test -a eap3842 -t jbosseap-6 fails. Version-Release number of selected component (if applicable): OpenShift Enterprise 2.1 as of today. How reproducible: I've seen it failing with various error messages, especially on setups with separate ActiveMQ. Steps to Reproduce: 1. Have OpenShift Enterprise 2.1 installation, possibly all-on-one but ActiveMQ on separate machine. 2. Run rhc create-app -n test -a eap3842 -t jbosseap-6 Actual results: # rhc create-app -n test -a eap3842 -t jbosseap-6 Application Options ------------------- Domain: test Cartridges: jbosseap-6 Gear Size: default Scaling: no Creating application 'eap3842' ... Unable to complete the requested operation due to: The server broker.example.com that your application is running on failed to respond in time. This may be due to a system restart. Reference ID: ee6da7d3a1dbe64968134c39957800b8 or # rhc create-app -n test -a eap8834 -t jbosseap-6 Application Options ------------------- Domain: test Cartridges: jbosseap-6 Gear Size: default Scaling: no Creating application 'eap8834' ... Starting jbosseap cartridge Found 127.6.115.129:8080 listening port Found 127.6.115.129:9999 listening port Failed to execute: 'control start' for /var/lib/openshift/539fe4e26892df876500009d/jbosseap Terminated (core dumped) Expected results: No error, application created. Additional info: In /var/log/openshift/node/platform.log there is June 17 08:59:09 INFO Shell command 'quota --always-resolve -w 539fe67b6892df87650000da' ran. rc=0 out=Disk quotas for user 539fe67b6892df87650000da (uid 5649): Filesystem blocks quota limit grace files quota limit grace /dev/mapper/vg_ibmx3550m308-lv_root 6308 0 1048576 416 0 80000 June 17 08:59:09 INFO openshift-agent: request end: action=cartridge_do, requestid=e1788ec8ac565d9c915aa8dd8738296b, senderid=broker.example.com, statuscode=1, data={:time=>nil, :output=>"CLIENT_ERROR: Failed to execute: 'control start' for /var/lib/openshift/539fe67b6892df87650000da/jbosseap\nCLIENT_MESSAGE: Starting jbosseap cartridge\nCLIENT_MESSAGE: Found 127.11.8.129:8080 listening port\nCLIENT_MESSAGE: Found 127.11.8.129:9999 listening port\n\nCLIENT_ERROR: Killed (core dumped)\n", :exitcode=>157, :addtl_params=>nil} That rhc create-app command takes some time to fail. When I run rhc apps while that rhc create-app is running, that eap* application is listed, and after it fails it gets removed again.