Hide Forgot
Created attachment 830065 [details] process list and node log Description of problem: When creating zend-6.1 application, error message "Failed to start Zend Server Java Bridge daemon" is seen. Version-Release number of selected component (if applicable): devenv_4081 How reproducible: always Steps to Reproduce: 1. Create a zend-6.1 application rhc app create zd2 zend-6.1 2. Check daemon on the app 3. Actual results: Error message "Failed to start Zend Server Java Bridge daemon" is seen. Expected results: No error message is shown. The app is created successfully. Additional info: 1. "ps -ef" output and node logs are added to the attachment. 2. Zend-5.6 works OK.
https://github.com/openshift/li/pull/2198
Test on devenv_4083, When start zend-6.1 app from stop, also have this error message "Error occured while processing event 'start':Failed to start Zend Server Java Bridge daemon" [rayzhang@ray Work]$ rhc app show --state -a myzend61 Cartridge zend-6.1 is started [rayzhang@ray Work]$ rhc app stop -a myzend61 RESULT: myzend61 stopped [rayzhang@ray Work]$ rhc app start -a myzend61 Error occured while processing event 'start':Failed to start Zend Server Java Bridge daemon
Commit pushed to master at https://github.com/openshift/li https://github.com/openshift/li/commit/0f06ba496db8b9adc915304d5702952d88b8e059 fix zend-6.1 watchdog failure Bug 1035605 https://bugzilla.redhat.com/show_bug.cgi?id=1035605
I fixed this issue in my local development environment. It should be resolved once we update the binary package.
Tested on devenv_4084. [openshift@dhcp-10-143 tmp]$ rac zd zend-6.1 Application Options ------------------- Domain: qiuzhang Cartridges: zend-6.1 Gear Size: default Scaling: no Creating application 'zd' ... done Note: You should set password for the Zend Server Console at: https://zd-qiuzhang.dev.rhcloud.com/ZendServer Zend Server 6 started successfully Waiting for your DNS name to be available ... done Cloning into 'zd'... @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ The RSA host key for zd-qiuzhang.dev.rhcloud.com has changed, and the key for the corresponding IP address 184.73.23.14 is unchanged. This could either mean that DNS SPOOFING is happening or the IP address for the host and its host key have changed at the same time. Offending key for IP in /home/openshift/.ssh/known_hosts:429 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the RSA key sent by the remote host is dc:7e:20:1c:9d:37:de:b3:94:3c:2a:ff:c1:bf:31:4a. Please contact your system administrator. Add correct host key in /home/openshift/.ssh/known_hosts to get rid of this message. Offending RSA key in /home/openshift/.ssh/known_hosts:135 Password authentication is disabled to avoid man-in-the-middle attacks. Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks. Your application 'zd' is now available. URL: http://zd-qiuzhang.dev.rhcloud.com/ SSH to: 529bff06d8b6cecec500000a.rhcloud.com Git remote: ssh://529bff06d8b6cecec500000a.rhcloud.com/~/git/zd.git/ Cloned to: /home/openshift/tmp/zd Run 'rhc show-app zd' for more details about your app. [openshift@dhcp-10-143 tmp]$ rhc app stop zd; rhc app start zd RESULT: zd stopped RESULT: zd started Mark the bug as verified.
@David, I already fixed this issue in the cartridge configuration files. Is there any other issue in the ZS binaries? How can we reproduce that?
This issue is no longer relevant since the current version of Openshift is no longer maintained.