FAQs

❓ Code Deploy Agent running with pid 0

This usually means that the EC2 disk space is low. Use below commands to correct the issue

sudo rm /opt/codedeploy-agent/state/.pid/codedeploy-agent.pid
sudo rm /opt/codedeploy-agent/state/.pid/codedeploy-agent.pid.lock
sudo service codedeploy-agent restart

Reference

---

❓ File already exists at given location on target instance

This happens if the new change detected by github is already present on target instance. For example, if a new file is added on github repo, but it was already lying around on EC2; then the pipeline will give an error at Install state.
The option to overwrite target files is not present inside pipeline.
The solution is to either create a manual deployment from the CodeDeploy application or remove the file from EC2 and release the CodePipeline again

---

❓ HEALTH_CONSTRAINTS Error Code

The error message would be The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems.
This usually means that the health check constraints failed. One possible reason could be that correct IAM role is not attached to EC2 instance. (Note, a restart of the instance is required after attaching any new IAM role)

---

❓ Error deleting directories in donwloadbundle stage

Restart the code-deploy agent service with sudo service codedeploy-agent restart or sudo systemctl restart codedeploy-agent.service

---