Worker nodes show offline in Github

runner2@static actions-runner % ./svc.sh status
status actions.runner.inc.mac-mini-runner2:

/Users/runner2/Library/LaunchAgents/actions.runner.inc.mac-mini-runner2.plist

Started:
72897 0 actions.runner.inc.mac-mini-runner2

However, the nodes appear offline, and aren’t taking any new jobs:

@w3sip ,

When the self-hosted runner is not connected to GitHub, it displays as ‘Offline’. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with GitHub.

In your case, it seems is because the self-hosted runner application cannot communicate with GitHub. You can try to check if there are any restrictions have been set on your Mac machine to prevent the runner application from communicating with GitHub. Such as firewall or proxy.

In addition, you also can try to install a new runner on the same Mac machine to see if it can work.

Unfortunately, this was the case of “none of the above”. The connectivity was fine, the workers were running and not showing any kind of distress. In fact, all it took to bring them back online was restarting the service.

Is there an API to generate an event/alert when either worker cannot connect to Github, or Github detects worker coming offline?

@w3sip ,

In fact, all it took to bring them back online was restarting the service.

Glad that your self-hosted runners are back to work.

Is there an API to generate an event/alert when either worker cannot connect to Github, or Github detects worker coming offline?

You can try using the “List self-hosted runners for an organization” API and “List self-hosted runners for a repository” API. From the response of the API, you can see the status (online or offline) of each runner.