Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Workflow don't start on self hosted runner

See original GitHub issue

Describe the bug We are using self hosted runner. After push to master, workflow doesn’t start running, and has got status in Queued. Problem reoccurs once a week.

To Reproduce Steps to reproduce the behavior:

After merge PR to master, workflow must begin running.
Workflow have got status Queued
Github action runner working as a service, with a command sudo ./svc.sh start

Expected behavior Workflow must run, and go to status In Progress

Runner Version and Platform

V2.300.2

Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy

Job Log Output


[2023-01-17 08:11:58Z INFO GitHubActionsService] Finished operation Location.GetConnectionData
[2023-01-17 08:11:58Z INFO GitHubActionsService] Starting operation Location.GetConnectionData
[2023-01-17 08:13:38Z WARN GitHubActionsService] GET request to https://pipelines.actions.githubusercontent.com/LiPvOEqVDHnB8f0MfsWaL2lCKf1zmCckzivkJxEOWAnQAONO7A/_apis/connectionData?connectOptions=1&lastChangeId=116858881&lastChangeId64=116858881 timed out after 100 seconds.
[2023-01-17 08:13:38Z INFO GitHubActionsService] Finished operation Location.GetConnectionData
[2023-01-17 08:13:38Z INFO JobServer] Catch exception during connect. 2 attempts left.
[2023-01-17 08:13:38Z ERR  JobServer] System.TimeoutException: The HTTP request timed out after 00:01:40.

Issue Analytics

State:
Created 8 months ago
Comments:7

Top GitHub Comments

2reactions

thiago-scherrercommented, Jan 17, 2023

Same here: Amazon linux:

hostnamectl
   Static hostname: ip-172-31-71-116.ec2.internal
         Icon name: computer-vm
           Chassis: vm
        Machine ID: ec2b61f81a781ec246ec8108b04ef88b
           Boot ID: 7a5c6d998bd84cf689d6c2c469c26bc5
    Virtualization: amazon
  Operating System: Amazon Linux 2
       CPE OS Name: cpe:2.3:o:amazon:amazon_linux:2
            Kernel: Linux 5.10.157-139.675.amzn2.x86_64
      Architecture: x86-64

Runner job:

runner1

runner2

1reaction

fhammerlcommented, Jan 18, 2023

Hi @starverdiyev 👋 Thanks for putting this issue together. The root cause of this timeout is likely on the server side and we’re already investigating and tracking it internally.

@thiago-scherrer the original issue is about a timeouts, while yours seems to be caused by an IO error. Would you mind filing it in a different issue with the following context:

Are you running as a service?
- If yes, are the user who configured / installed the service the same as the one running it? (if not, that would explain your IO error)
- If not, are you running the runner through an ssh session?
Are you running any anti-virus?
Do you have any other runners on this VM?

Top Results From Across the Web

About self-hosted runners

GitHub-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted runners are a highly configurable way to run workflows in...

How to prevent GitHub Actions workflow being triggered by ...

Do not use the self-hosted runner unless you really need it. If you need it then make your repo private. Switch to GitHub-hosted...

Error "Waiting for a runner to pick up this job" using GitHub ...

In my case, it was petty mistake. The runs-on was supposed to be ubuntu-latest, but was self-hosted. And it was waiting on it...

Self-hosted runners for GitHub Actions is now in beta

Self -hosted runners offers a number of advantages when the hosted virtual environments don't meet all your needs and it's now available for ......

Self hosted workflows struggles to start

I would expect the workflow worker to start and operate smoothly, but it keeps restarting and spitting out errors that dont make much...