Re: Solr Scale Toolkit Access Denied Error
Thanks, Tim. Worked like a charm. Appreciate your timely assistance. On Sat, Jun 7, 2014 at 9:13 PM, Timothy Potter thelabd...@gmail.com wrote: Hi Mark, Sorry for the trouble! I've now made the ami-1e6b9d76 AMI public; total oversight on my part :-(. Please try again. Thanks Hoss for trying to help out on this one. Cheers, Tim On Fri, Jun 6, 2014 at 6:46 PM, Mark Gershman montan...@gmail.com wrote: Thanks, Hoss. I did substitute the previous AMI ID from the mid-May release of the toolkit and the build process does proceed further; however, it appears the the AMI changed enough that it is not compatible with the new toolkit release. In doing a little more research, I'm inclined to believe that the permissions on the AMI may be the source of the problem and will post to the issue tracker per your suggestion. Mark Gershman On Fri, Jun 6, 2014 at 7:41 PM, Chris Hostetter hossman_luc...@fucit.org wrote: : My guess is that the customized toolkit AMI (ami-1e6b9d76) at AWS is not : accessible by my AWS credentials. Is this an AMI permissioning issue or is : it a problem with my particular account or how it is configured at AWS. I : did not experience this specific problem when working with the previous : iteration of the Solr Scale Toolkit back toward the latter part of May. It : appears that the AMI was updated from ami-96779efe to ami-1e6b9d76 with the : newest version of the toolkit. I'm not much of an AWS expert, but i seem to recall that if you don't have your AWS security group setup properly this type of error can happen? is it possible that when you were trying out solr-scale-tk before you had this setup, but now you don't? https://github.com/LucidWorks/solr-scale-tk You'll need to setup a security group named solr-scale-tk (or update the fabfile.py to change the name). At a minimum you should allow TCP traffic to ports: 8983, 8984-8989, SSH, and 2181 (ZooKeeper). However, it is your responsibility to review the security configuration of your cluster and lock it down appropriately. You'll also need to create an keypair (using the Amazon console) named solr-scale-tk (you can rename the key used by the framework, see: AWS_KEY_NAME). After downloading the keypair file (solr-scale-tk.pem), save it to ~/.ssh/ and change permissions: chmod 600 ~/.ssh/solr-scale-tk.pem ...if I'm wrong, and there really is a problem with the security on the AMI, the best place to report that would be in the project's issue tracker... https://github.com/LucidWorks/solr-scale-tk/issues -Hoss http://www.lucidworks.com/
Re: Solr Scale Toolkit Access Denied Error
Hi Mark, Sorry for the trouble! I've now made the ami-1e6b9d76 AMI public; total oversight on my part :-(. Please try again. Thanks Hoss for trying to help out on this one. Cheers, Tim On Fri, Jun 6, 2014 at 6:46 PM, Mark Gershman montan...@gmail.com wrote: Thanks, Hoss. I did substitute the previous AMI ID from the mid-May release of the toolkit and the build process does proceed further; however, it appears the the AMI changed enough that it is not compatible with the new toolkit release. In doing a little more research, I'm inclined to believe that the permissions on the AMI may be the source of the problem and will post to the issue tracker per your suggestion. Mark Gershman On Fri, Jun 6, 2014 at 7:41 PM, Chris Hostetter hossman_luc...@fucit.org wrote: : My guess is that the customized toolkit AMI (ami-1e6b9d76) at AWS is not : accessible by my AWS credentials. Is this an AMI permissioning issue or is : it a problem with my particular account or how it is configured at AWS. I : did not experience this specific problem when working with the previous : iteration of the Solr Scale Toolkit back toward the latter part of May. It : appears that the AMI was updated from ami-96779efe to ami-1e6b9d76 with the : newest version of the toolkit. I'm not much of an AWS expert, but i seem to recall that if you don't have your AWS security group setup properly this type of error can happen? is it possible that when you were trying out solr-scale-tk before you had this setup, but now you don't? https://github.com/LucidWorks/solr-scale-tk You'll need to setup a security group named solr-scale-tk (or update the fabfile.py to change the name). At a minimum you should allow TCP traffic to ports: 8983, 8984-8989, SSH, and 2181 (ZooKeeper). However, it is your responsibility to review the security configuration of your cluster and lock it down appropriately. You'll also need to create an keypair (using the Amazon console) named solr-scale-tk (you can rename the key used by the framework, see: AWS_KEY_NAME). After downloading the keypair file (solr-scale-tk.pem), save it to ~/.ssh/ and change permissions: chmod 600 ~/.ssh/solr-scale-tk.pem ...if I'm wrong, and there really is a problem with the security on the AMI, the best place to report that would be in the project's issue tracker... https://github.com/LucidWorks/solr-scale-tk/issues -Hoss http://www.lucidworks.com/
Solr Scale Toolkit Access Denied Error
I've been attempting to experiment with the recently updated Solr Scale Tool Kit mentioned here: http://searchhub.org/2014/06/03/introducing-the-solr-scale-toolkit/ After making the very well documented configuration changes at AWS and installing Python, I was able to use the toolkit to connect to AWS; however, when the demo command (fab demo:demo1,n=1) is executed, the following access denied error message is returned: C:\Temp\sk\solr-scale-tkfab demo:demo1,n=1 ←[33mGoing to launch 1 new EC2 m3.medium instances using AMI ami-1e6b9d76←[0m ←[32mSetup Instance store BlockDeviceMapping: /dev/sdb - ephemeral0←[0m Traceback (most recent call last): File c:\python27\lib\site-packages\fabric\main.py, line 743, in main *args, **kwargs File c:\python27\lib\site-packages\fabric\tasks.py, line 405, in execute results['local-only'] = task.run(*args, **new_kwargs) File c:\python27\lib\site-packages\fabric\tasks.py, line 171, in run return self.wrapped(*args, **kwargs) File C:\Temp\sk\solr-scale-tk\fabfile.py, line 1314, in demo ec2hosts = new_ec2_instances(cluster=demoCluster, n=n, instance_type=instance_type) File C:\Temp\sk\solr-scale-tk\fabfile.py, line 776, in new_ec2_instances placement_group=placement_group) File c:\python27\lib\site-packages\boto\ec2\connection.py, line 943, in run_instances verb='POST') File c:\python27\lib\site-packages\boto\connection.py, line 1177, in get_object raise self.ResponseError(response.status, response.reason, body) boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request ?xml version=1.0 encoding=UTF-8? ResponseErrorsErrorCodeAuthFailure/CodeMessageNot authorized for images: [ami-1e6b9d76]/Message/Error/ErrorsRequestIDcbdcb582-3d21-4fab-a7ea -fe68ba696e23/RequestID/Response My guess is that the customized toolkit AMI (ami-1e6b9d76) at AWS is not accessible by my AWS credentials. Is this an AMI permissioning issue or is it a problem with my particular account or how it is configured at AWS. I did not experience this specific problem when working with the previous iteration of the Solr Scale Toolkit back toward the latter part of May. It appears that the AMI was updated from ami-96779efe to ami-1e6b9d76 with the newest version of the toolkit. Many thanks to Timothy Potter to assembling this excellent toolkit for deploying and managing SolrCloud at AWS (and hopefully other cloud providers in the future). Thanks. Mark Gershman
Re: Solr Scale Toolkit Access Denied Error
: My guess is that the customized toolkit AMI (ami-1e6b9d76) at AWS is not : accessible by my AWS credentials. Is this an AMI permissioning issue or is : it a problem with my particular account or how it is configured at AWS. I : did not experience this specific problem when working with the previous : iteration of the Solr Scale Toolkit back toward the latter part of May. It : appears that the AMI was updated from ami-96779efe to ami-1e6b9d76 with the : newest version of the toolkit. I'm not much of an AWS expert, but i seem to recall that if you don't have your AWS security group setup properly this type of error can happen? is it possible that when you were trying out solr-scale-tk before you had this setup, but now you don't? https://github.com/LucidWorks/solr-scale-tk You'll need to setup a security group named solr-scale-tk (or update the fabfile.py to change the name). At a minimum you should allow TCP traffic to ports: 8983, 8984-8989, SSH, and 2181 (ZooKeeper). However, it is your responsibility to review the security configuration of your cluster and lock it down appropriately. You'll also need to create an keypair (using the Amazon console) named solr-scale-tk (you can rename the key used by the framework, see: AWS_KEY_NAME). After downloading the keypair file (solr-scale-tk.pem), save it to ~/.ssh/ and change permissions: chmod 600 ~/.ssh/solr-scale-tk.pem ...if I'm wrong, and there really is a problem with the security on the AMI, the best place to report that would be in the project's issue tracker... https://github.com/LucidWorks/solr-scale-tk/issues -Hoss http://www.lucidworks.com/
Re: Solr Scale Toolkit Access Denied Error
Thanks, Hoss. I did substitute the previous AMI ID from the mid-May release of the toolkit and the build process does proceed further; however, it appears the the AMI changed enough that it is not compatible with the new toolkit release. In doing a little more research, I'm inclined to believe that the permissions on the AMI may be the source of the problem and will post to the issue tracker per your suggestion. Mark Gershman On Fri, Jun 6, 2014 at 7:41 PM, Chris Hostetter hossman_luc...@fucit.org wrote: : My guess is that the customized toolkit AMI (ami-1e6b9d76) at AWS is not : accessible by my AWS credentials. Is this an AMI permissioning issue or is : it a problem with my particular account or how it is configured at AWS. I : did not experience this specific problem when working with the previous : iteration of the Solr Scale Toolkit back toward the latter part of May. It : appears that the AMI was updated from ami-96779efe to ami-1e6b9d76 with the : newest version of the toolkit. I'm not much of an AWS expert, but i seem to recall that if you don't have your AWS security group setup properly this type of error can happen? is it possible that when you were trying out solr-scale-tk before you had this setup, but now you don't? https://github.com/LucidWorks/solr-scale-tk You'll need to setup a security group named solr-scale-tk (or update the fabfile.py to change the name). At a minimum you should allow TCP traffic to ports: 8983, 8984-8989, SSH, and 2181 (ZooKeeper). However, it is your responsibility to review the security configuration of your cluster and lock it down appropriately. You'll also need to create an keypair (using the Amazon console) named solr-scale-tk (you can rename the key used by the framework, see: AWS_KEY_NAME). After downloading the keypair file (solr-scale-tk.pem), save it to ~/.ssh/ and change permissions: chmod 600 ~/.ssh/solr-scale-tk.pem ...if I'm wrong, and there really is a problem with the security on the AMI, the best place to report that would be in the project's issue tracker... https://github.com/LucidWorks/solr-scale-tk/issues -Hoss http://www.lucidworks.com/
