Amazon Installation is Failing for Both 1pm and multi pm

5 posts / 0 new
Last post
idokara
idokara's picture
Offline
Last seen: 4 weeks 16 hours ago
Joined: Mar 2 2014
Junior Boarder

Posts: 6

Ido Karavany
Amazon Installation is Failing for Both 1pm and multi pm

Hi All,

 

I'm trying to install InfiniDB using amazon installer and installation is failing.

 

What was done:

 

1. Create instance with InfiniDB 4.6 AMI  (eu-west-1) - instance created under private VPC

2. Configure amazonConfig.xml (can be found at the bottom of the post) - values changed: subnet ID, VPC Start IP, Required Keys

3. Executed /root/amazonInstaller

 

Results:

 

1. Instance Tagging was changed to calpont-1-pm1 (meaning that connection to AWS works)

2. creating second pm (pm2) is failing with the below detilas.

 

Can you please assist?

 

Thanks,

Ido

 

Error:
 

[root@ip-172-18-21-46 ~]# ./amazonInstaller amazonConfig.xml
 
This is the Amazon InfiniDB AMI System Configuration and Installation tool.
It will Configure and startup an Amazon InfiniDB System.
It will read the system configuration settings from /root/amazonConfig.xml
 
===== Setting up system 'calpont-1' based on these settings =====
 
InfiniDB Version = 4.6.0-1
System Type = separate
SubNet ID = subnet-46aa6a23
Starting VPC Private IP = autoassign
Number of User Modules = 1 (m3.medium)
User Modules Instances Security Group = sg-2d8a5948
Using EBS Volumes for User Module storage = y
User Module EBS Volume Size = 10
Number of Performance Modules = 2 (m3.medium)
Number of DBRoots per Performance Modules = 1
Using EBS Volumes for Performance Module (DBRoot) storage = y
DBRoot EBS Volume Size = 100
SNMP Trap Receiver IP Address = 0.0.0.0
Instance and Volume Name Auto Tagging = enabled
Amazon Region = eu-west-1
 
===== Launch Instances =====
 
Local Instance for pm1: i-3647c176
 Creating Instance Tag for pm1
 
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for um1, will retry up to 5 times
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for pm2, will retry up to 5 times
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for um1, will retry up to 5 times
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for pm2, will retry up to 5 times
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for um1, will retry up to 5 times
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for pm2, will retry up to 5 times
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for um1, will retry up to 5 times
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for pm2, will retry up to 5 times
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for um1, will retry up to 5 times
 *** Failed to Successfully Launch Instance for um1
 
***** Performing System Cleanup *****
 
Client.InvalidParameterValue: Value (sg-20f43845) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
 *** Failed to Launch an Instance for pm2, will retry up to 5 times
 *** Failed to Successfully Launch Instance for pm2
 
 
 
 
Cleanup finished, exiting
 
 
 
[root@ip-172-18-21-46 ~]# cat amazonConfig.xml
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: amazonConfig.xml 2830 2012-04-08 17:38:58Z dhill $ -->
<!--   Used with the amazonInstaller script-->
<Calpont Version="V1.0.0">
        <SystemConfig>
                <!-- System Name-->
                <SystemName>calpont-1</SystemName>
 
                <!-- System Type: combined (um and pm functionality on same instance)
                                        separate (um and pm functionality on separate instances) -->
                <SystemType>separate</SystemType>
 
                <!--- VPC Configuration Setup -->
                <!---                                             -->
                <!--- subnet ID -->
                <!--- The ID of the Amazon VPC subnet in which to launch the instance(s) -->
                <SubNetID>subnet-46aa6a23</SubNetID>
 
                <!-- VPC Starting Private IP Address -->
                <!-- Requires the SubNetID to be setup -->
                <!-- Use this if you want InfiniDB to assigned IP Addresses starting with this one -->
                <!-- Set value to 'autoassign' if you want Amazon to auto-assign IP Addresses within the subnet range -->
                <VPCStartPrivateIP>autoassign</VPCStartPrivateIP>
 
                <!-- User Modules Private IP Address list, use when running on a Amazon VPC -->
                <!-- Requires the SubNetID to be setup -->
                <!-- This list would start with um1, list is seperated by commands. i.e 'ip1,ip2,ip3' -->
                <!-- IGNORED when VPCStartPrivateIP is set -->
                <UserModulePrivateIP>unassigned</UserModulePrivateIP>
 
                <!-- Performance Modules Private IP Address list, use when running on a Amazon VPC -->
                <!-- Requires the SubNetID to be setup -->
                <!-- This list would start with pm2, list is seperated by commands. i.e 'ip1,ip2,ip3' -->
                <!-- IGNORED when VPCStartPrivateIP is set -->
                <PerformanceModulePrivateIP>unassigned</PerformanceModulePrivateIP>
 
                <!-- Elastic IP to Module Assignment -->
                <!--- Example usages: x.x.x.x:um1 -->
                <!--- Example usages: x.x.x.x:um1,y.y.y.y:pm1 -->
                <ElasticIPs>unassigned</ElasticIPs>
 
                <!-- Number of User Modules: n/a for combination system type -->
                <UserModuleCount>1</UserModuleCount>
 
                <!-- User Modules Instances list, use existing instances instead of Launching new ones -->
                <!-- This list would start with um1, list is seperated by commands. i.e 'id1,id2,id3' -->
                <UserModuleInstances>unassigned</UserModuleInstances>
 
                <!-- User Modules Instance Type, default to local Instance Type -->
                <UserModuleInstanceType>unassigned</UserModuleInstanceType>
 
                <!-- User Modules Security Group, default to local Security Group -->
                <UserModuleSecurityGroup>unassigned</UserModuleSecurityGroup>
 
                <!-- Use EBS Volumes for User Module data storage? -->
                <!-- Applicable for system type = 'separate' only -->
                <UseUMEBSVolumes>y</UseUMEBSVolumes>
 
                <!-- Size of User Module EBS Volumes in gigibytes -->
                <!-- Applicable for system type = 'separate' only -->
                <UMEBSVolumeSize>10</UMEBSVolumeSize>
 
                <!-- Number of Performance Modules -->
                <PerformanceModuleCount>2</PerformanceModuleCount>
 
                <!-- Performance Modules Instances list, use existing instances instead of Launching new ones -->
                <!-- This list would start with pm2, list is seperated by commands. i.e 'id1,id2,id3' -->
                <PerformanceModuleInstances>unassigned</PerformanceModuleInstances>
 
                <!-- Number of DBRoots assigned to each Performance Module -->
                <DBRootsPerPM>1</DBRootsPerPM>
 
                <!-- Use EBS Volumes for (um/pm) data storage (system type = 'combined')? -->
                <!-- Use EBS Volumes for pm data storage (system type = 'separate')? -->
                <UsePMEBSVolumes>y</UsePMEBSVolumes>
 
                <!-- Size of Back-End Data EBS Volumes in gigibytes -->
                <PMEBSVolumeSize>100</PMEBSVolumeSize>
 
                <!-- SNMP Trap Receiver IP Address: 0.0.0.0 means no snmptraps will be forwarded -->
                <SNMPTrapIPAddr>0.0.0.0</SNMPTrapIPAddr>
 
                <!-- Total UM Memory Size Percentage, default to postConfigure setting -->
                <TotalUmMemory>unassigned</TotalUmMemory>
 
                <!-- Blocks Cache Size Percentage, default to postConfigure setting -->
                <NumBlocksPct>unassigned</NumBlocksPct>
 
                <!-- Root Password or 'ssh' for ssh-key setup -->
                <RootPassword>Calpont1</RootPassword>
 
                <!-- Enables Automatic Amazon Instance/Volume tagging -->
                <!-- When set 'y', Instance Name Tags will be set to 'system-name'-'module-name' -->
                <!--               DBRoot Volume Name Tags will be set to 'system-name'-'dbrootID' -->
                <!--               User Module Volume Name Tags will be set to 'system-name'-'module-name' -->
                <AutoTagging>y</AutoTagging>
 
                <!-- Amazon EC2 region your running in, run ec2-describe-regions to get valid region names -->
                <Region>eu-west-1</Region>
 
                <!-- x.509 Certification File with directory location. i.e. /root/cert-xxxx -->
                <x509CertificationFile>/root/cert.pem</x509CertificationFile>
 
                <!-- x.509 Private Key File with directory location. i.e. /root/pk-xxxx -->
                <x509PrivateFile>/root/pk.pem</x509PrivateFile>
        </SystemConfig>
</Calpont>
 
 
 

 

davidhill
davidhill's picture
Offline
Last seen: 1 month 2 weeks ago
Joined: Oct 27 2009
Administrator

Posts: 595

david hill
install failure

Hey Ido, the error being reported is related to the "IAM role". So I assume when you launched the first instance from the AMI, you provided a IAM Role on the same page you entered the subnet information.

Not being a Amazon expert, it seems to not like the IAM role in assocation with the UM-Security-group name you provide. So this assocation needs to be checked out.

 

You could change the amazonConfig file and not enter the UM-security and let it default to the same security that the Original instance was started with, just to see if that works.

 

Also just a point of clarification..

 

When you run the command as shown here, its using the default config version of amazonConfig.xml

 

   ./amazonInstaller amazonConfig.xml

 

You can just run:

 

   ./amazonInstaller

 

And if you wanted to use a different version than the default, you would do the following:

 

./amazonInstaller -c amazonConfig_pm1.xml

 

David

idokara
idokara's picture
Offline
Last seen: 4 weeks 16 hours ago
Joined: Mar 2 2014
Junior Boarder

Posts: 6

Ido Karavany
Hi,

Hi,

 

Thanks for your response.

I've pasted the wrong execution output (I've tried both with and w/o SG)

 

I executed w/o security group configuration as you can see in the above amazonConfig.xml

 

so it is not working w/o as well.

 

any advise?

 

Thanks,

Ido

idokara
idokara's picture
Offline
Last seen: 4 weeks 16 hours ago
Joined: Mar 2 2014
Junior Boarder

Posts: 6

Ido Karavany
Hi,

Hi,

 

Thanks for your response.

I've pasted the wrong execution output (I've tried both with and w/o SG)

 

I executed w/o security group configuration as you can see in the above amazonConfig.xml

 

so it is not working w/o as well.

 

any advise?

 

Thanks,

Ido

davidhill
davidhill's picture
Offline
Last seen: 1 month 2 weeks ago
Joined: Oct 27 2009
Administrator

Posts: 595

david hill
install failure

You report you pasted the wrong execution output, so what is the correct and current error you are getting?

This VPC type setup does work for me, so there seems to be something related to your VPC setup or still the possible use of a AMI ROLE.

 

Please retry and post the Error... And you might try to Launch another InfiniDB AMI Instance without giving the AMI ROLE and see what happens.

That cold help isolate the issue.

 

David