search

viatra2 / IDEA-AWS-Elastic-Beanstalk-Integration

This plugin provides support for Amazon Web Services Elastic Beanstalk cloud platform
5 stars 0 forks source link

error "Command execution completed. Summary: [Successful: 0, TimedOut: 1]." #15

Open price2b opened 10 years ago

price2b commented 10 years ago

Hi, I update the aws plugin. I dont know if it has something to do with that but during my lasts commits and upload to AWS i receive the following information: "Command execution completed. Summary: [Successful: 0, TimedOut: 1]." consequently no new information is updated to the server. My elasticbeanstalk app name and my elasticbeanstalk url differ. one is: name-environment , the other is: name.elasticbeanstalk.com. When deployment finishes its says application is available at: http://name-environment.elasticbeanstalk.com when my url must be http://name.elasticbeanstalk.com.

Do you know if this could possibly have any relation with the "timeout:1" and no change are made to app on live environment?. brgds!

price2b commented 10 years ago

disregard. my mystake with cache. I downloaded the file from aws and its ok. on the other hand it displays old files on live app. weird. sorry once again,b rgds!

viatra2 commented 10 years ago

Hello, Sebastian

Regarding your issue - there is generic plugin problem when EB app-name and url differs. The plugin currently assumes that these values are identical and this could lead to incorrect URL message. Remote PHP debugging is also affected because debug configuration uses incorrect remote host.

As temporary workaround for PHP debugging you can manually change the host field in debug server settings (File > Settings > PHP > Servers > Host - please change only host, not the name field) or use default identical App\URL naming. We have created issue #16 - please use it to track the problem status.

Regarding "Command execution completed. Summary: [Successful: 0, TimedOut: 1]." - such message could appear when EB Extensions scripts have execution problems. To enable PHP XDebug on the EB instances the plugin creates .ebextensions\phpdebug.config file. Please make sure this file is not changed improperly (delete it if you doubt, it will be recreated on next debug configuration launch).

Please also provide additional information:

  1. We assumed that you use PhpStorm, is this correct?
  2. If you use PhpStorm , what configuration do you deploy with - "Run" or "Debug"?
  3. Do you use your own *.config files? If yes, please check their correctness too.
  4. Is "TimedOut: 1" message appears either regularly or occasionally?

Regards, Viatra2

price2b commented 10 years ago

thank you for your answer. 1- yes 2- run 3- no. only the proposed installation. 4- since i have a different url than app project name.

brgds!!

price2b commented 10 years ago

i´ve been testing and it seems that the best way to solve it is to create a new environment inside elasticbeanstalk with the same url that the name used previously in the other app and swap url environments,