Hide Forgot
Description of problem: On a fresh all-on-one OpenShift Enterprise 2.0 installation, running oo-diagnostics -v -w 1 fails with INFO: running oo-accept-node [31mFAIL: run_script oo-accept-node had errors: --BEGIN OUTPUT-- FAIL: kernel.sem semaphores too low: 128 < 512 1 ERRORS --END oo-accept-node OUTPUT--[0m Version-Release number of selected component (if applicable): Enterprise 2.0. How reproducible: Deterministic. Steps to Reproduce: 1. Run ./openshift.sh to configure all on one Enterprise 2.0. 2. Run oo-diagnostics -v -w 1 Actual results: INFO: running oo-accept-node [31mFAIL: run_script oo-accept-node had errors: --BEGIN OUTPUT-- FAIL: kernel.sem semaphores too low: 128 < 512 1 ERRORS Expected results: No error. Additional info: I should point out that I've reported this issue on Origin back in June in bug 974497, it even got cloned to Enterprise product as bug 1007752 but sadly that got deferred, so this bug confirms my concern from bug 1007752 comment 4 -- the issue got to GA'ed version.
That didn't use to happen. I'll have to figure out what changed.
This shouldn't happen at all. When you use openshift.sh, it sets the semaphores higher, and has for as long as we've had it I think. See: configure_sysctl_on_node() { set_sysctl kernel.sem '250 32000 32 4096' 'Accomodate many httpd instances for OpenShift gears.' Now, this doesn't take effect until system reboot (or there's a sysctl option to put it into effect). However the instructions are to reboot after install. Are you running this after a reboot or before?
(In reply to Luke Meyer from comment #5) > This shouldn't happen at all. When you use openshift.sh, it sets the > semaphores higher, and has for as long as we've had it I think. See: > > configure_sysctl_on_node() > { > set_sysctl kernel.sem '250 32000 32 4096' 'Accomodate many httpd > instances for OpenShift gears.' > > > Now, this doesn't take effect until system reboot (or there's a sysctl > option to put it into effect). However the instructions are to reboot after > install. Are you running this after a reboot or before? Yeah, thank you for he catch, it was the "not rebooting" thing. I cannot reasonably reboot after installation so that was the cause of the bug. Running sysctl -p fixes the problem. I wonder if the openshift.sh could do that automatically?
I'm going to close this as DEFERRED. If it ever happens it will be part of this PR: https://github.com/openshift/openshift-extras/pull/311