Description of problem: [backend-commentoid.rhcloud.com bin]\> ~/haproxy/bin/control stop /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons/application.rb:330:in `kill': Operation not permitted (Errno::EPERM) from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons/application.rb:330:in `stop' from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons/application_group.rb:135:in `block in stop_all' from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons/application_group.rb:131:in `each' from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons/application_group.rb:131:in `stop_all' from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons/controller.rb:74:in `run' from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons.rb:139:in `block in run' from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons/cmdline.rb:105:in `call' from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons/cmdline.rb:105:in `catch_exceptions' from /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.0.10/lib/daemons.rb:138:in `run' from /var/lib/openshift/5191a04ee0b8cdfe4f000196/haproxy/usr/bin/haproxy_ctld_daemon.rb:18:in `<main>' Version-Release number of selected component (if applicable): How reproducible: Only affects some users. Steps to Reproduce: Not yet known.
Related to this thread https://www.openshift.com/forums/openshift/scaled-nodejs-haproxy-git-push-failing-error-message-failed-to-execute-control-stop#comment-32442
This issue does not reproduce on STG(devenv-stage_414), please refer to the following results: Check this issue with a jbossews-2.0 scalable app: [cews2s0-cstg23.stg.rhcloud.com bin]\> ~/haproxy/bin/control stop CLIENT_RESULT: HAProxy instance is stopped [cews2s0-cstg23.stg.rhcloud.com bin]\> ~/haproxy/bin/control start CLIENT_RESULT: HAProxy instance is started The testing account information: # rhc account Server: stg.openshift.redhat.com Login: chunchen+23 Plan: Silver Gears Used: 5 Gears Allowed: 16 Allowed Gear Sizes: small, medium SSL Certificates Supported: yes
I investigated this over a couple of hours on July 17 with the help of openshift's IRC group, and the issue was there, despite having restarted the app and using app-restart as well as ~/haproxy/bin/control stop. However, I just tested again to push the code without having made any changes to configurations and it works. remote: CLIENT_RESULT: HAProxy instance is stopped remote: CLIENT_RESULT: HAProxy instance is started You may close the ticket for now, I can reopen if the issue appears again.