Description of problem: Ref: https://openshift.redhat.com/community/faq/can-i-access-my-applications-gear I have used haproxy_ctld -u to launch a new gear in manual mode. haproxy_ctld_daemon was not and is not running. Using rhc app show, I saw Scaling: go from 1 to 2 as expected. However, ~/haproxy-1.4/conf/gear-registry.db is empty. Where else can I find the IP or host of the framework gear? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Can't reproduce this issue on devenv or int. [rmtest-rmillnerint.int.rhcloud.com 51378bb36cec0e896a00007d]\> haproxy_ctld -u [rmtest-rmillnerint.int.rhcloud.com 51378bb36cec0e896a00007d]\> cat ~/haproxy-1.4/conf/gear-registry.db 5137920b6cec0e896a000179.73.135:php-5.3;5137920b6cec0e896a000179-rmillnerint.int.rhcloud.com Taking off the build blocker list.
The haproxy_ctld daemon should be running; but you can disable auto_scaling by setting the appropriate marker. Here's how to do that: Go into your git clone of the application touch .openshift/markers/disable_auto_scaling git add .openshift/markers/disable_auto_scaling git commit -m 'Disabled automatic scaling' git push Then ssh back into your head gear, scale up and observe ~/haproxy-1.4/conf/gear-registry.db.
Try this bug in two ways, One is Rob mentioned, after haproxy_ctld -u, gear info recorded into gear_registry.db The other one, is kill the haproxy_ctld manually, then haproxy_ctld -u, \> ps -ef |grep haproxy_ctld 501 2142 1 0 21:33 ? 00:00:00 haproxy_ctld.rb 501 23470 23012 0 21:41 pts/1 00:00:00 grep haproxy_ctld \> kill -9 2142 \> cat haproxy-1.4/conf/gear-registry.db \> haproxy_ctld -u \> cat haproxy-1.4/conf/gear-registry.db 5137fe407883cf878100000a.189.249:jbossas-7;5137fe407883cf878100000a-bmengdev.dev.rhcloud.com \> ps -ef |grep haproxy_ctld 501 13941 1 0 21:45 ? 00:00:00 haproxy_ctld.rb 501 24985 23012 0 21:45 pts/1 00:00:00 grep haproxy_ctld One concern of the issue in topic is, the haproxy_ctld -u took a long time，and the gear which just scaled-up has already scaled-down automatically. Please add disable_auto_scaling marker to prevent this kind of problem. As comment#2. Thanks. Move bug to verified.