- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello,
Reviewing the above error message it seems the script itself is failing which is causing the deployment to fail. To further troubleshoot the issue I would recommend to login (SSH) to the EC2 instance and test the working of your affected script by executing it manually.
Additionally, as you mentioned that shell/after.sh run as user ubuntu failed with exit code 1
, Thus I would request you to please try and execute shell/after.sh script using root user and check if that works for you.
Moreover I would request you to review the script logs from the location below -
less /opt/codedeploy-agent/deployment-root/<deployment-group-ID>/<deployment-ID>/logs/scripts.log
In case you are still facing any issues, I would recommend to create a support case with AWS Premium support for further troubleshooting so that support team can have a deeper look at your environment configuration. This would help us to reproduce the issue, if required further.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- Wie kann ich den CodeDeploy-Agent mit einem Benutzerprofil ausführen, das nicht das Stammprofil ist?AWS OFFICIALAktualisiert vor 3 Jahren
The installation of zaproxy caused a conflict with the Python package. I have deleted all the extra zaproxy related packages. Codedeploy has returned to normal. I still need to find a way to isolate zaproxy.