Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GameLift fleet resource fails to stabilize when deploying gamelift backend #2

Open
jwlondon98 opened this issue Mar 28, 2023 · 2 comments

Comments

@jwlondon98
Copy link

Following the deployment process described in the readme. When I run cdk deploy PersistentWorldGameliftStack (step 7), the command line eventually prints a CREATE_FAILED error on step 36/42:

Example Persistent World Fleet (ExamplePersistentWorldFleet) Resource handler returned message: "Resource of type 'AWS::GameLift::Fleet' with identifier 'fleet-393d4f21-f56e-4f97-a0b9-7325b08dfaf5' did not stabilize." (RequestToken: f15ba57a-dd4f-4921-03f5-f692c7632d78, HandlerErrorCode: NotStabilized)

image

The process then proceeds to ROLLBACK all previous steps.

@ScatSoQt
Copy link

ScatSoQt commented Apr 2, 2023

Looking at the Fleets for more information, I saw under Events:
Cannot run program "/local/game/install.sh" (in directory "/local/game"): error=2, No such file or directory

@juhoaws
Copy link
Contributor

juhoaws commented Jun 1, 2023

Hi both!

Sorry for the very delayed reply. First thing you should do is to check that the LinuxServerBuild folder has install.sh in it (as it should) as well as the game server binary and data.

If you're on Windows, there might be a line ending problem with the install.sh script changing from the original Unix line endings to Windows. You could try with Notepad++ to change the line endings in install.sh by selecting "Edit -> EOL conversion -> UNIX/OSX Format" and saving.

Let me know if this helped and I will look more into it if needed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants