1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
Hello, this typically tends to happen when the zip containing the server build is not packaged correctly. Have you tried unpacking using a command line utility to verify if install.sh is at the root directory? A common behavior with archiving utilities is they tend to put all files within a top level directory, causing install.sh to be present withing an extra level of nesting.
답변함 2년 전
I'm using the aws cli gamelift upload-build function with the path to the folder containing the full server build on my machine. I don't zip anything on my end and the launch path I use for each server process is properly relative to /local/game/ so when I don't include the install.sh the fleet works properly.
To follow up, I've sshed into one of the working fleets that doesn't have install.sh and confirmed the path is correct without an extra level of nesting.
We'd need more details to help debug this issue further. Could you please reach out to AWS support via AWS Support Center so the GameLift team can help take a deeper look?