Self-hosted runner hangs indefinitely at "Fetching the repository"

[JonasVautherin]

Select Topic Area

Bug

Body

I have a setup with two self-hosted runners running on the same machine (macOS).

It used to work well when each runner was being run by its own macOS user. But recently I changed it to only one user running both runners (so I do ./svc.sh install twice from the same macOS user).

Sometimes, one of the runners hangs indefinitely at "Fetching the repository". It may look like this:

Fetching the repository
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +59d74d46b95901239e1c86e7949f263eedf11901:refs/tags/my-tag
  Error: The operation was canceled.

I have been observing it for multiple days and it seems like it only happens when the other runner is active. When the other runner is idle, I have never seen this one hang. It's also not a problem of resources on the machine: I checked the disk/memory/cpu/network while it was hanging and nothing seems off. Also while it is hanging, I can go on the machine and run an arbitrary git clone from the Terminal and it just works.

I have been searching a lot and I haven't seen any documentation online saying that two self-hosted runners cannot be active at the same time on the same machine.

Could it be that they conflict for some reason (on macOS)? Would that be considered a bug?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ushiii111798]

Now experiencing technical issue with all git operation on github. I guess it is related.

[JonasVautherin]

I don't think so. It happened in the last week, and for what I could see, it consistently works when the other runner is inactive.

[connorDevLGH]

https://www.githubstatus.com/

There is a problem with the server status.

[connorDevLGH]

Now the server is working fine, please try again.

[JonasVautherin]

It has been happening in the last week, and really sometimes it hangs while the other runner is fine, and when the other runner stops, I can restart the job and it passes.

[rivaldo766hi]

I'm also experiencing this issue on a self-hosted macOS runner. It works fine initially, but after running several jobs, it hangs while fetching the repository. Have you found a solution, @JonasVautherin ?

[NoSugarCoffee]

I'm facing this issue on a self-hosted Ubuntu runner. It seems good when I access the _work dir and run the same command. I'm not sure what is happening.

[JonasVautherin]

Is it a public or private repo (using an access token)?

[NoSugarCoffee]

In my case, it seemed to be a network issue. Accessing the GitHub API in China was very slow. After I deployed the Runner overseas, the problem disappeared.

But I don't know why it worked fine when accessing the _work dir.

[khareyash05]

Happening with my self hosted Mac Runners. Did we get a solution regarding the same?

[enmanuelmag]

Happening on my linux slef hosted, any solution?

[JonasVautherin]

Do you have multiple runners on the same machine, as I described at the top? I have moved to running just one runner per machine, and I haven't seen this issue anymore.

Not sure if that was the issue though, maybe something was wrong in the configuration...