CodeDeploy Pipeline Failures from appspec Missing Files

Question

Here's my appspec.yml file:

```
version: 0.0
os: linux
files:
  - source: /
    destination: /home/ec2-user/myapp
hooks:
  BeforeInstall:
    - location: scripts/remove_root_dir.sh
      timeout: 900
      runas: root
  ApplicationStart:
    - location: scripts/install_dependencies.sh
      timeout: 300
      runas: root
    - location: scripts/start_server.sh
      timeout: 300
      runas: root
  ApplicationStop:
    - location: scripts/stop_server.sh
      timeout: 300
      runas: root
```
Here's my stop_server.sh file under the scripts folder in my Angular root directory:

```
#!/bin/bash
isExistApp = `pgrep httpd`
if [[ -n  $isExistApp ]]; then
    service httpd stop        
fi
```
The error message that I get is "ScriptMissing" at the ApplicationStop step. The script is not missing. I stopped my codedeploy agent, tried to clear out the files under /opt/codedeploy-agent/deployment-root (but many were write protected), and restarted the codedeploy agent. No success after numerous attempts to get CodeDeploy to complete successfully. What should I do to get CodeDeploy working properly?"

Adeleke Adebowale .J. · Answer

The "ScriptMissing" error in AWS CodeDeploy typically indicates that CodeDeploy cannot find the specified script at the location specified in your appspec.yml file. Here are some steps and considerations to troubleshoot and resolve this issue:

Verify Script Location and Permissions
1) Double-check Script Location:
Ensure that the stop_server.sh script is indeed located in the scripts directory of your Angular root directory. If the script is not present or is located elsewhere, CodeDeploy will fail to find it during deployment.

2) Confirm File Permissions:
Check the permissions of the stop_server.sh script. The script should have executable permissions (chmod +x stop_server.sh) to ensure that it can be executed during the deployment process.

Debugging Steps
  1. Review CodeDeploy Logs:
Check the CodeDeploy logs to get more specific information about why the script is not being found. You can access CodeDeploy logs through the AWS Management Console or via the AWS CLI.

bash

```
aws deploy get-deployment --deployment-id  --query "deploymentInfo.[status, diagnostics[0].message]"
Replace  with your actual deployment ID.
```
 
 2. Agent Configuration:
Sometimes, issues can arise if the CodeDeploy agent does not have the correct permissions or if there are issues with its configuration. Ensure that the agent is running and has the necessary permissions to access and execute scripts from the specified locations.

3. File Structure Consistency:
If you've tried clearing out the deployment files and restarting the CodeDeploy agent without success, ensure that the directory structure and file paths in your deployment package (ZIP file or S3 bucket) match what is specified in your appspec.yml.

Example Fix
Assuming your stop_server.sh script is correctly located in scripts/stop_server.sh relative to your deployment root, and has executable permissions, here's how your appspec.yml should be structured:

yaml

```
version: 0.0
os: linux
files:
  - source: /
    destination: /home/ec2-user/myapp
hooks:
  BeforeInstall:
    - location: scripts/remove_root_dir.sh
      timeout: 900
      runas: root
  ApplicationStart:
    - location: scripts/install_dependencies.sh
      timeout: 300
      runas: root
    - location: scripts/start_server.sh
      timeout: 300
      runas: root
  ApplicationStop:
    - location: scripts/stop_server.sh
      timeout: 300
      runas: root
```

Ensure that:

stop_server.sh exists in the scripts directory relative to the root of your deployment.
The script has executable permissions (chmod +x stop_server.sh).
The path specified (scripts/stop_server.sh) matches the actual path where stop_server.sh is located in your deployment artifact.
By carefully verifying these aspects, you should be able to resolve the "ScriptMissing" error and successfully deploy your application using AWS CodeDeploy. If issues persist, reviewing detailed logs and ensuring consistent configurations across your deployment environment can provide further insights.

CodeDeploy Pipeline Failures from appspec Missing Files

新增您的答案

相關內容