- Newest
- Most votes
- Most comments
Hi,
One common reason a fleet goes from the ACTIVATING status into ERROR is due to an invalid LaunchPath in the ServerProcess configuration https://docs.aws.amazon.com/gamelift/latest/apireference/API_ServerProcess.html
Hope that helps.
There are 2 ways to upload the script; 1 by uploading zip file and 2 by using s3. It is clearly mentioned in the problem statement that when uploaded through the zip file directly, the fleet runs properly. During activation, the LaunchPath is checked separately. We see in the events sections. Hence, there should be no question about invalid launch Path. The real problem is the fleet is not activated when we create the fleet from the script uploaded by s3. Also, by ssh in fleet instance, we see that script is loaded in the fleet server from s3. Hence, there must be something that we are missing here. AWS console showing error Resource fleet-2d5a0ff4-b794-4188-adbe-xxxxxxxx is not in a taggable state
Relevant content
- asked 2 years ago
- asked 2 years ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
Did you solve this issue? If yes, please share. I am stuck for 3 days.
Op here. I solved it. The actual reason seems to be: CDK Asset cannot be used to host a game lift script. I ended up using a custom s3 bucket and that solved it.
Sir, it's not happening. Even I am manually passing the s3 bucket and object key. It's not happening. Script size is showing 0 bytes. Error in Aws console is Resource fleet-2d5a0ff4-b794-4188-adbe-xxxxxxxx is not in a taggable state. In doing ssh, I am finding that code has been uploaded. But it's stuck in the Activating part for 1 hour. Also, I have tried manually, from the AWS console, same situation occurs. Only when I upload through the zip file (which is for less than 5 mb), then only the fleet gets activated. Please help me. I am simply uploading the most minimal code which is just having an init function for example purpose.
In my case I always uploaded the script as a zip file and no problem.
Maybe this post can help you: https://github.com/aws/aws-cdk/pull/21805 to disable automatic unzipping when uploading to s3.