nerdexam
GitHub

GITHUB-ACTIONS · Question #41

As a developer, your self-hosted runner sometimes looses connection while running jobs. How should you troubleshoot the issue affecting your self-hosted runner?

The correct answer is C. Access the self-hosted runner's installation directory and look for log files in the _diag folder.. When troubleshooting a self-hosted runner, you can access the _diag folder located in the self- hosted runner's installation directory. This folder contains diagnostic logs that can help you identify the root cause of issues, such as connection problems.

GitHub Actions - Self-Hosted Runners

Question

As a developer, your self-hosted runner sometimes looses connection while running jobs. How should you troubleshoot the issue affecting your self-hosted runner?

Options

  • ASet the DEBUG environment variable to true before starting the self-hosted runner to produce
  • BLocate the self-hosted runner in your repository's settings page and download its log archive.
  • CAccess the self-hosted runner's installation directory and look for log files in the _diag folder.
  • DStart the self-hosted runner with the --debug flag to produce more verbose console output.

How the community answered

(45 responses)
  • A
    2% (1)
  • B
    7% (3)
  • C
    76% (34)
  • D
    16% (7)

Explanation

When troubleshooting a self-hosted runner, you can access the _diag folder located in the self- hosted runner's installation directory. This folder contains diagnostic logs that can help you identify the root cause of issues, such as connection problems.

Topics

#self-hosted runners#troubleshooting#diagnostics#log files

Community Discussion

No community discussion yet for this question.

Full GITHUB-ACTIONS Practice