The Ubuntu root directory file system is not shared with Windows. I think others who have used Windows have successfully used Cygwin to run the setup scripts. Perhaps you could try that approach? If you run into any problems there, you can probably get them resolved with a search in this forum/thread.
When I run
$ bash setup_p2.sh
it gets following error:
setup_p2.sh: line 7: syntax error near unexpected token newline' setup_p2.sh: line 7:’
Then I copy the raw from git which is 21 lines, and save to setup_p2.sh
and run $ bash setup_p2.sh
it says
setup_p2.sh: line 20: ./setup_instance.sh: No such file or directory
I think it’s the last line:
. $(dirname “$0”)/setup_instance.sh
Is that because the p2 is not yet approved by AWS?
I try t2 as well, and got the same error.
setup_t2.sh: line 20: ./setup_instance.sh: No such file or directory
I was able to follow the AWS Install steps and setup a p2 instance, and ssh into it. But I was doing this on one system. And after using the instance, I stopped it.
Can I redo this process and access the same instance from a different PC?
On a different PC, I modified the aws-alias.sh to point to the correct $instanceId (which is the ID of the already created instance in the step above), but I can’t ssh into it. I get the following error:
Warning: Identity file /home/username/.ssh/aws-key-fast-ai.pem not accessible: No such file or directory.
Permission denied (publickey).
How can I access the same instance from a different system?
I created a new key-pair as you mentioned (used the cli tool) and saved a .pem file in a directory. When I ssh now, using this .pem file, I still get this:
I restarted from scratch today, and the previous issues are fixed, but now I am getting this.
An error occurred (InsufficientInstanceCapacity) when calling the RunInstances operation (reached max r etries: 4): We currently do not have sufficient p2.xlarge capacity in the Availability Zone you request ed (us-west-2b). Our system will be working on provisioning additional capacity. You can currently get p2.xlarge capacity by not specifying an Availability Zone in your request or choosing us-west-2c.
An error occurred (MissingParameter) when calling the CreateTags operation: The request must contain th e parameter resourceIdSet
Waiting for instance start...
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:
aws help
aws <command> help
aws <command> <subcommand> help
aws: error: argument --instance-id: expected one argument
An error occurred (MissingParameter) when calling the RebootInstances operation: The request must contain the parameter InstancesSet
All done. Find all you need to connect in the fast-ai-commands.txt file and to remove the stack call fast-ai-remove.sh
Connect to your instance: ssh -i /home/Peter/.ssh/aws-key-fast-ai.pem ubuntu@None
This error seems to be a problem on AWS’ end. I don’t think an AZ is specified in the setup script, so I’m not sure why it claims that you can choose us-west-2c. You could try again at a later time, or you could change your region altogether.
aws configure set region us-east-1
If you change your region, you may want to do a quick check just to make sure you don’t have any leftover resources, such as unused instances, volumes, or elastic IPs. If you run this for loop you should get no output:
for resource in {instances,addresses,volumes}; do aws ec2 describe-$resource; done
edit: This is an aside, but just remembered that the fast.ai script sets up only one subnet which is associated with a single AZ. So while the error message says you can switch your AZ, you actually can’t because the fast-ai subnet CIDR block encompasses that of the entire fast-ai VPC. You could create a new VPC with a subnet for each AZ, similar to how the default one is set up.
Hi, I got this message when typed in “bash setup/setup_p2.sh”
True
An error occurred (InvalidKeyPair.NotFound) when calling the RunInstances operation: The key pair ‘aws-key-fast-ai’ does not exist
An error occurred (MissingParameter) when calling the CreateTags operation: The request must contain the parameter resourceIdSet
Waiting for instance start…
Waiter InstanceRunning failed: Max attempts exceeded
usage: aws [options] [ …] [parameters]
To see help text, you can run:
aws help
aws help
aws help
aws: error: argument --instance-id: expected one argument
An error occurred (MissingParameter) when calling the RebootInstances operation: The request must contain the parameter InstancesSet
All done. Find all you need to connect in the fast-ai-commands.txt file and to remove the stack call fast-ai-remove.sh
Connect to your instance: ssh -i /home/guyos/.ssh/aws-key-fast-ai.pem ubuntu@None
One thing that worked for me it to use the aws console to create a P2.Xlarge, then go back to the EC2 dashboard and terminate it and then try to run the script again.
I’m having the same issue as @chenwk89. After amazon set up a p2 server for me, I made it to the point of running bash setup_p2.sh and now I’m getting the following error:
“An error occurred (OptInRequired) when calling the CreateTags operation: You are not subscribed to this service. Please go to http://aws.amazon.com to subscribe”.
I’m an American working in India, so I’m assuming I’m getting this error because I’m outside of the states right now. @Zok recommended to @chenwk891to use spot instances. Is that what I should do as well? I was just a little confused by the back and forth on the forum at that point.
The spot instances are not required; they are a lower cost option to on-demand instances, but require some additional setup. I would recommend starting out with the on-demand instances, which is what the provided scripts set up.
To resolve your error message I’d check to make sure that your access key ID and secret access key are correctly assigned in the .aws/credentials file. If you’re certain they are correct then I’d try contacting AWS support.