|
| 1 | +# Troubleshooting startCluster |
| 2 | + |
| 3 | +If you are having problems at [Step 3 (Start Cluster)](step_3_start_cluster.md) in your Distributed-CellProfiler runs, you may find the following troubleshooting information helpful. |
| 4 | + |
| 5 | +## IamFleetRole |
| 6 | + |
| 7 | +If there is a problem with the `IamFleetRole` in your Fleet File, you may get the following error: |
| 8 | + |
| 9 | +```bash |
| 10 | +botocore.exceptions.ClientError: An error occurred (InvalidSpotFleetRequestConfig) when calling the RequestSpotFleet operation: Parameter: SpotFleetRequestConfig.IamFleetRole is invalid. |
| 11 | +``` |
| 12 | + |
| 13 | +## IamInstanceProfile |
| 14 | + |
| 15 | +If there is a problem with the `IamInstanceProfile` in your Fleet File, you may get the following error: |
| 16 | + |
| 17 | +```bash |
| 18 | +Your spot fleet request is causing an error and is now being cancelled. Please check your configuration and try again |
| 19 | +spotFleetRequestConfigurationInvalid : c5.xlarge, ami-0f161e6034a6262d8, Linux/UNIX: Value |
| 20 | +``` |
| 21 | + |
| 22 | +- Check your FleetFile.json. |
| 23 | +Confirm that in the `IamInstanceProfile` the `Arn` is an **instance-profile** NOT a **role** (e.g. `"arn:aws:iam::012345678901:instance-profile/ecsInstanceRole"`). |
| 24 | +This is different from the `IamFleetRole` at the top of the FleetFile.json that is a **role**. |
| 25 | +- Confirm that your ecsInstanceRole was created correctly. |
| 26 | +If you created resources manually, using either the CLI or the console, you may have missed part of the `IamInstanceProfile` creation. |
| 27 | +In your command line, run `aws iam list-instance-profiles-for-role --role-name ecsInstanceRole`. |
| 28 | +If it returns `{"InstanceProfiles": []}`, then run the following commands: |
| 29 | + |
| 30 | +```bash |
| 31 | +aws iam create-instance-profile --instance-profile-name ecsInstanceRole |
| 32 | + |
| 33 | +aws iam add-role-to-instance-profile --role-name ecsInstanceRole --instance-profile-name ecsInstanceRole |
| 34 | +``` |
| 35 | + |
| 36 | +## SubnetId |
| 37 | + |
| 38 | +If there is a problem with the `SubnetId` in your Fleet File, you may get the following error: |
| 39 | + |
| 40 | +```bash |
| 41 | +botocore.exceptions.ClientError: An error occurred (InvalidSpotFleetRequestConfig) when calling the RequestSpotFleet operation: One of the provided subnets was not valid. |
| 42 | +``` |
| 43 | + |
| 44 | +## Groups |
| 45 | + |
| 46 | +If there is a problem with the `Groups` in your Fleet File, you may get the following error: |
| 47 | + |
| 48 | +```bash |
| 49 | +Your spot fleet request is causing an error and is now being cancelled. Please check your configuration and try again |
| 50 | +spotFleetRequestConfigurationInvalid : c5.xlarge, ami-0f161e6034a6262d8, Linux/UNIX: The security group 'sg-01234567890123451atest' does not exist in VPC 'vpc-0123456789012345' |
| 51 | +``` |
0 commit comments