{"action":"created","issue":{"url":"https://api.github.com/repos/oliverlloyd/jmeter-ec2/issues/37","labels_url":"https://api.github.com/repos/oliverlloyd/jmeter-ec2/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/oliverlloyd/jmeter-ec2/issues/37/comments","events_url":"https://api.github.com/repos/oliverlloyd/jmeter-ec2/issues/37/events","html_url":"https://github.com/oliverlloyd/jmeter-ec2/issues/37","id":96538240,"number":37,"title":"Test don't start with default amazon Ubuntu instance","user":{"login":"Firfi","id":947595,"avatar_url":"https://avatars.githubusercontent.com/u/947595?v=3","gravatar_id":"","url":"https://api.github.com/users/Firfi","html_url":"https://github.com/Firfi","followers_url":"https://api.github.com/users/Firfi/followers","following_url":"https://api.github.com/users/Firfi/following{/other_user}","gists_url":"https://api.github.com/users/Firfi/gists{/gist_id}","starred_url":"https://api.github.com/users/Firfi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Firfi/subscriptions","organizations_url":"https://api.github.com/users/Firfi/orgs","repos_url":"https://api.github.com/users/Firfi/repos","events_url":"https://api.github.com/users/Firfi/events{/privacy}","received_events_url":"https://api.github.com/users/Firfi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-22T11:07:38Z","updated_at":"2015-07-22T14:48:13Z","closed_at":null,"body":"I use Ubuntu Server 14.04 LTS (HVM), SSD Volume Type - ami-5189a661 . \r\n\r\nIt starting correctly and being active during test, but all the time I see only \r\n\r\n`waiting for the test to start...to stop the test while it is running, press CTRL-C`. This message doesn't disappear, and it can hang there one hour.\r\n\r\nIf I do ctrl+c, script exiting successfully, destroying temporary instance, and returns empty report.\r\n\r\nAny suggestions what can cause this problem?"},"comment":{"url":"https://api.github.com/repos/oliverlloyd/jmeter-ec2/issues/comments/123746938","html_url":"https://github.com/oliverlloyd/jmeter-ec2/issues/37#issuecomment-123746938","issue_url":"https://api.github.com/repos/oliverlloyd/jmeter-ec2/issues/37","id":123746938,"user":{"login":"oliverlloyd","id":1336821,"avatar_url":"https://avatars.githubusercontent.com/u/1336821?v=3","gravatar_id":"","url":"https://api.github.com/users/oliverlloyd","html_url":"https://github.com/oliverlloyd","followers_url":"https://api.github.com/users/oliverlloyd/followers","following_url":"https://api.github.com/users/oliverlloyd/following{/other_user}","gists_url":"https://api.github.com/users/oliverlloyd/gists{/gist_id}","starred_url":"https://api.github.com/users/oliverlloyd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oliverlloyd/subscriptions","organizations_url":"https://api.github.com/users/oliverlloyd/orgs","repos_url":"https://api.github.com/users/oliverlloyd/repos","events_url":"https://api.github.com/users/oliverlloyd/events{/privacy}","received_events_url":"https://api.github.com/users/oliverlloyd/received_events","type":"User","site_admin":false},"created_at":"2015-07-22T14:48:13Z","updated_at":"2015-07-22T14:48:13Z","body":"If I had to have a guess I'd say jmeter is failing to start. Have a look to see if there are any *.out files in the directory where you are running the script. The `[blah]jmeter.out` file(s) should contain the stdout from the command to execute jmeter, if there were any errors with this they will be here. Maybe this instance is missing a pre-requisit like java. Does it work if you use a different ami such as `ami-e1e8d395`?\r\n\r\nIt's also possible that the command to execute jmeter failed before the jmeter process was started. The best way to test this is to spin up an instance, jump onto it, and try to run jmeter directly on the instance.\r\n\r\nAnother possibility is connectivity issues but this is less likely because you've got passed the install stages which means the script was able to talk to the instance that was spun up - it's just not hearing back from jmeter.\r\n\r\nYou can also try running the script in debug mode by passing `-x` when running it or editing jmeter-ec2.sh to have `set -x` at the top. This will print the commands being run and, if you don't terminate the instances by passing `terminate=FALSE` as an option then you can use this log to try rerunning these commands manually.\r\n\r\nIf you still have no luck print a copy of your output here with the -x debug option set.\r\n\r\n"}}