1. Have you checked your /etc/hosts file?

Should look like this

127.0.0.1 localhost
xx.xx.xx.xx [hostname]

2. Also in jmeter-ec2.sh file, Line 427 add this and give me output

p (scp -q -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
-i "$PEM_PATH/$PEM_FILE"
-P $REMOTE_PORT
$LOCAL_HOME/verify.sh
$LOCAL_HOME/jmeter-ec2.properties
$USER@$host:$REMOTE_HOME
&& echo "done" > $project_home/$DATETIME-$host-scpverify.out)

Make sure Same User exist when you do scp to remoate machine.
Run step 2 command seperately on command line and fix it. Make sure Firewall is off

from jmeter-ec2.

My local host shows
127.0.0.1 localhost

I noticed you put a p infront of (scp
What does that do.

from jmeter-ec2.

All it does is print the command it tries to execute. have u tried
creating instance manually and scp to it ?i ran tgis script on ubuntu
machine and it created ubuntu vm and scp my jmx. not sure if something
needa to be done if you try to scp from ubuntu to win 10

On Wednesday, July 6, 2016, Franco DeAmicis [email protected]
wrote:

My local host shows
127.0.0.1 localhost

I noticed you put a p infront of (scp
What does that do.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#73 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/APS_nK937TgNQyXfOFwX3R5sMmwuwxcsks5qTC2MgaJpZM4JGjwQ
.

from jmeter-ec2.

I'm wondering if the value of the $USER@$host:$REMOTE_HOME variable is being corrupted in any way. It would be great if I could hard code the value of $USER@$host:$REMOTE_HOME in the jmeter-ec2.sh in order to see if it works. That's not possible because the jmeter-ec2 script generates new instances each time you run the script

from jmeter-ec2.

Interesting finding. When I hard code the $USER@$host:$REMOTE_HOME \ value in the jmeter-ec2.sh script while the instance is running, the SCP call goes through. That makes me think there are two possibilities
1.) The value of $USER@$host:$REMOTE_HOME is either getting formatted incorrectly
2.) Once the instance status checks are complete, the SCP call is timing out

from jmeter-ec2.

The cause is the the value of $USER@$host:$REMOTE_HOME not getting formatted properly. I'll have to debug and see how the hosts array is being formatted

from jmeter-ec2.

check your jmeter-ec2.properties file for USER variable. Set proper value there. Format of $USER@$host:$REMOTE_HOME is correct.

#jmeter-ec2.properties file

Should match the AMI

USER="ubuntu"

Also check SUBNET= "" [should match with AWS subnet]

from jmeter-ec2.

I had the jmeter-ec2.sh print out a list of the host ip it extracted from amazon which was 52.41.112.80

When I create a separate SCP call to the running instance and use [email protected], the call works fine

When the jmeter-ec2.sh script makes the SCP call with [email protected], we get an error

Either there is a space being inserted in the ip or the ip is correct and the user is mangled as mentioned by gauravpatel2016. I'm getting closer to figuring this out

from jmeter-ec2.

What is permission of jmeter-ec2.sh

On Thursday, July 7, 2016, Franco DeAmicis [email protected] wrote:

I had the jmeter-ec2.sh print out a list of the host ip it extracted from
amazon which was 52.41.112.80

When I create a separate SCP call to the running instance and use
[email protected] javascript:_e(%7B%7D,'cvml','[email protected]');,
the call works fine

When the jmeter-ec2.sh script makes the SCP call with [email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');, we get an error

Either there is a space being inserted in the ip or the ip is correct and
the user is mangled as mentioned by gauravpatel2016. I'm getting closer to
figuring this out

[image: host]
https://cloud.githubusercontent.com/assets/4235950/16671759/5c56e7d8-446f-11e6-8ccc-071d694a5fb4.jpg

[image: sc]
https://cloud.githubusercontent.com/assets/4235950/16671768/65381c3c-446f-11e6-8f4d-4cc60a368e3e.jpg

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#73 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/APS_nD6Pdd7c1yAS898xkkPwLjIWkxJxks5qTXuagaJpZM4JGjwQ
.

from jmeter-ec2.

I gave full write and read permission to my project directory

On Thursday, July 7, 2016, Franco DeAmicis [email protected] wrote:

I had the jmeter-ec2.sh print out a list of the host ip it extracted from
amazon which was 52.41.112.80

When I create a separate SCP call to the running instance and use
[email protected] javascript:_e(%7B%7D,'cvml','[email protected]');,
the call works fine

When the jmeter-ec2.sh script makes the SCP call with [email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');, we get an error

Either there is a space being inserted in the ip or the ip is correct and
the user is mangled as mentioned by gauravpatel2016. I'm getting closer to
figuring this out

[image: host]
https://cloud.githubusercontent.com/assets/4235950/16671759/5c56e7d8-446f-11e6-8ccc-071d694a5fb4.jpg

[image: sc]
https://cloud.githubusercontent.com/assets/4235950/16671768/65381c3c-446f-11e6-8f4d-4cc60a368e3e.jpg

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#73 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/APS_nD6Pdd7c1yAS898xkkPwLjIWkxJxks5qTXuagaJpZM4JGjwQ
.

from jmeter-ec2.

I get a bad substitution error when I concatenate the strings. That is the cause of all my issues. No sure how to fix

from jmeter-ec2.

With $USER"@"$host":"$REMOTE_HOME, the $host variable had a huge amount of trailing spaces. THat is why the : ends up infront of the [email protected]

I had to add "$(echo -e "${mystring}" | sed -e 's/[[:space:]]*$//')" to the variable in order to get rid of the trailing spaces

from jmeter-ec2.