You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
here is no error message in codedeploy-agent.aws_wire.log. Codedeploy can sometimes be deployed successfully, but most of them fail this time. At first, I thought it was an S3 access problem because I set the aws security group outbound traffic limit for the instance. But I opened the outbound traffic to S3. When I opened all outbound traffic of 443 and 80, this error still appeared. Is there any other way to fix this error?
The text was updated successfully, but these errors were encountered:
@nassercarlos19 we found that when new instances came online sometimes the code deploy agent would not start and therefore the deployment would fail. I added a scheduled task to our image that runs every 5 minutes to check the service is running and start it if it isn't.
We only have this on our Windows image, Linux never had the same issues.
Thanks, @a-jackson. In my case, the agent is always running, but for some reason, after downloading the bundle, I see the agent stopping and starting again. After this restart, it gets stuck until it time out after 1 hour and 10 minutes.
This is a random issue; sometimes it works, and sometimes fails.
here is no error message in codedeploy-agent.aws_wire.log. Codedeploy can sometimes be deployed successfully, but most of them fail this time. At first, I thought it was an S3 access problem because I set the aws security group outbound traffic limit for the instance. But I opened the outbound traffic to S3. When I opened all outbound traffic of 443 and 80, this error still appeared. Is there any other way to fix this error?
The text was updated successfully, but these errors were encountered: