Aws codedeploy agent download no such file

Copy link. One: Error extracting tar archive: 2 Two: End of file reached Three: No such file or directory - getcwd I use Github deployment through the portal and I've never had an issue before. Update: seems to be happening as it downloads the bundle. Oh, what host OS are you using? And what ruby version, just in case. Amazon Linux I've run into issue three: No such file or directory - getcwd This occurred after the disk was full - codedeploy keeps five tar files which filled up the instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment. Linked pull requests. You signed in with another tab or window. Reload to refresh your session.

Monitor Your Service 4. Conclusion 3. Create a Microservice 1. Create a Serverless Microservice 1. Extending Serverless Microservices 2. Configure orchestration with CodeStar 3. Challenge - Expose the microservice API 5. Conclusion 4. Automate Your Microservice 2.

Challenge - Enhance The Calculator Service 7. Resources 5. Exploring Messaging Options 1. Of course, different artifacts and different deploy scripts in each case. But, codedeploy creates a subfolder with the deployment id, so they shouldn't collide. Also my pipelines are multiregion and it never happened in both regions at once even tho the machines are built the same and the artifact is the same. I have opened the issue : for following up.

Skip to content. Star New issue. Jump to bottom. Now, we have reverted the affected instances to perform a yum install of the version specific rpm. Upon using the older version, CodeDeploy works as expected. What's strange to me is why CodeDeploy is failing at the DownloadBundle step, with the reason suggesting that the files the agent itself has put there shouldn't be there.

It seems like the bundle is being downloaded and then the check to see if the directory is non-empty comes in afterwards? This is happening on both freshly launched instances and existing instances with previous deployments. A couple more questions:. For those accounts you are seeing impact, with the same deployment bundle, is the deployment always failed with this error?

Or the deployment did actually succeed sometimes? With V1. It will very helpful if you can try unzip -qo the command agent is running on you bundle and see anything is wrong. Hi, yubangxi. Sorry, let me clarify. The deployment bundles are different between every account and every application. They failed consistently between all. You can check all the output of CodeDeploy in the directory:. TroubleShooting CodeDeploy it is not easy.

The official documentation lacks a bit on these corner cases. Remember to ssh into the machine and have a look into all the different log files that can help you narrowing down the error.