MacOs M1 Github Runner Service times out when running manually in terminal session
See original GitHub issueDescribe the bug The runner does not start on the M1 as expected. The service does not register properly with launchctl under a user domain. Running run.sh as a user ultimately will timeout if tried to run in an indefinite terminal session.
To Reproduce Steps to reproduce the behavior:
- Follow Github provided installation instructions for MacOs
2. Run ./run.sh
Roughly within 30 minutes or less the script will disconnect / reconnect aborting workflow actions and anything running when a disconnect occurs.
2022-09-09 18:12:49Z: Runner reconnected. 2022-09-09 18:22:05Z: Runner connect error: The HTTP request timed out after 00:01:00… Retrying until reconnected.
**Expected behavior**
Service remains connected
## Runner Version and Platform
2.296.1
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Self-hosted runner Status switch to offline after logout #1476
The problem starts after we close the login session (SSH or Screen share). After a few minutes, the status changed to offline. When...
Read more >Not able to run self-hosted runner application as a service ...
Describe the bug Getting "Offline" status after starting up mac. We have added self hosted runner in Mac M1 as per the documentation....
Read more >Github action runner svc start not working on MacOS ...
Trying to set up a self-hosted github actions runner as a service so it ... error was to run through the UI on...
Read more >Monitoring and troubleshooting self-hosted runners
You can monitor your self-hosted runners to view their activity and diagnose common issues.
Read more >[BUG] npm install will randomly hang forever and cannot ...
When running npm install it will sometimes hang at a random point. ... If it gets stuck it should either time-out or be...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Update: this turns out to be caused by an IPv6 routing issue on our end. forcing the runner’s machine to do IPv4 only fixes it. I’m now working on getting IPv6 fixed and then I’ll report back.
What’s interesting is that some of the API calls seemed to have succeeded - those are probably not using IPv6 yet, whereas githubusercontent.com is.
Removing the IPv6 assignment fixed my issue, too! I created subnets without IPv6 (setting
assign_ipv6_address_on_creation
tofalse
) and the issue was then resolved and authentication took place.Side note: originally,
amazon-linux-extras
just hung during the start up when trying to install docker. The resolved that issue as well.