|
|
|
|
@@ -16,11 +16,11 @@ shortTitle: Troubleshoot GitHub Actions
|
|
|
|
|
|
|
|
|
|
## Checking the health of {% data variables.product.prodname_actions %}
|
|
|
|
|
|
|
|
|
|
You can check the health of {% data variables.product.prodname_actions %} on {% data variables.location.product_location %} with the `ghe-actions-check` command-line utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
|
|
|
|
|
You can check the health of {% data variables.product.prodname_actions %} on {% data variables.location.product_location %} with the `ghe-actions-check` command-line utility. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" and "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
|
|
|
|
|
|
|
|
|
|
## Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %}
|
|
|
|
|
|
|
|
|
|
{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)."
|
|
|
|
|
{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-tls)."
|
|
|
|
|
|
|
|
|
|
### Installing the certificate on the runner machine
|
|
|
|
|
|
|
|
|
|
@@ -61,7 +61,7 @@ If you deploy {% data variables.product.prodname_ghe_server %} in your environme
|
|
|
|
|
You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.location.product_location %}. Each self-hosted runner will require one of the following procedures:
|
|
|
|
|
|
|
|
|
|
* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application.
|
|
|
|
|
* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[Removing self-hosted runners](/actions/hosting-your-own-runners/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
|
|
|
|
|
* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/removing-self-hosted-runners)" and "[AUTOTITLE](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
|
|
|
|
|
|
|
|
|
|
## Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits
|
|
|
|
|
|
|
|
|
|
@@ -71,9 +71,9 @@ You may be hitting the CPU or memory limits if you notice that jobs are not star
|
|
|
|
|
|
|
|
|
|
### 1. Check the overall CPU and memory usage in the management console
|
|
|
|
|
|
|
|
|
|
Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)."
|
|
|
|
|
Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)."
|
|
|
|
|
|
|
|
|
|
If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.location.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)."
|
|
|
|
|
If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.location.product_location %} is running at capacity and needs to be scaled up. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources)."
|
|
|
|
|
|
|
|
|
|
### 2. Check the Nomad Jobs CPU and memory usage in the management console
|
|
|
|
|
|
|
|
|
|
@@ -92,7 +92,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
|
|
|
|
|
|
|
|
|
|
### 3. Increase the resource allocation for services at their limit
|
|
|
|
|
|
|
|
|
|
1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
|
|
|
|
|
1. Log in to the administrative shell using SSH. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
|
|
|
|
|
1. Run the following command to see what resources are available for allocation:
|
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
@@ -167,13 +167,13 @@ By default, {% data variables.product.prodname_actions %} workflow runs that are
|
|
|
|
|
|
|
|
|
|
There are three ways to resolve this problem:
|
|
|
|
|
|
|
|
|
|
1. You can update your workflows so that they are no longer triggered by {% data variables.product.prodname_dependabot %} using an expression like: `if: github.actor != 'dependabot[bot]'`. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
|
|
|
|
|
2. You can modify your workflows to use a two-step process that includes `pull_request_target` which does not have these limitations. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions#responding-to-events)."
|
|
|
|
|
1. You can update your workflows so that they are no longer triggered by {% data variables.product.prodname_dependabot %} using an expression like: `if: github.actor != 'dependabot[bot]'`. For more information, see "[AUTOTITLE](/actions/learn-github-actions/expressions)."
|
|
|
|
|
2. You can modify your workflows to use a two-step process that includes `pull_request_target` which does not have these limitations. For more information, see "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions#responding-to-events)."
|
|
|
|
|
3. You can provide workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and allow the `permissions` term to increase the default scope of the `GITHUB_TOKEN`. For more information, see "[Providing workflows triggered by{% data variables.product.prodname_dependabot %} access to secrets and increased permissions](#providing-workflows-triggered-by-dependabot-access-to-secrets-and-increased-permissions)" below.
|
|
|
|
|
|
|
|
|
|
### Providing workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and increased permissions
|
|
|
|
|
|
|
|
|
|
1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
|
|
|
|
|
1. Log in to the administrative shell using SSH. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
|
|
|
|
|
1. To remove the limitations on workflows triggered by {% data variables.product.prodname_dependabot %} on {% data variables.location.product_location %}, use the following command.
|
|
|
|
|
``` shell
|
|
|
|
|
$ ghe-config app.actions.disable-dependabot-enforcement true
|
|
|
|
|
@@ -199,10 +199,10 @@ A part of the Actions setup had problems and needs an administrator to resolve.
|
|
|
|
|
To install the official bundled actions and starter workflows within a designated organization in {% data variables.product.prodname_ghe_server %}, follow this procedure.
|
|
|
|
|
|
|
|
|
|
1. Identify an organization that will store the official bundled actions and starter workflows. You can create a new organization or reuse an existing one.
|
|
|
|
|
- To create a new organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
|
|
|
|
|
- For assistance with choosing a name for this organization, see "[Reserved Names](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#reserved-names)."
|
|
|
|
|
- To create a new organization, see "[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
|
|
|
|
|
- For assistance with choosing a name for this organization, see "[AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#reserved-names)."
|
|
|
|
|
|
|
|
|
|
1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
|
|
|
|
|
1. Log in to the administrative shell using SSH. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
|
|
|
|
|
1. To designate your organization as the location to store the bundled actions, use the `ghe-config` command, replacing `ORGANIZATION` with the name of your organization.
|
|
|
|
|
```shell
|
|
|
|
|
$ ghe-config app.actions.actions-org ORGANIZATION
|
|
|
|
|
@@ -220,4 +220,4 @@ To install the official bundled actions and starter workflows within a designate
|
|
|
|
|
$ ghe-config-apply
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
After you've completed these steps, you can resume configuring {% data variables.product.prodname_actions %} at "[Managing access permissions for GitHub Actions in your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#managing-access-permissions-for-github-actions-in-your-enterprise)."
|
|
|
|
|
After you've completed these steps, you can resume configuring {% data variables.product.prodname_actions %} at "[AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#managing-access-permissions-for-github-actions-in-your-enterprise)."
|
|
|
|
|
|
Peter Bengtsson