I have a job where I run 4+ runners in parallel. Generally we were getting pretty good performance where all were running, with the occasional failure where a GH runner was not established correctly. However - recently we've been noticing that failure occurring more frequently. This is different than some of the other issues on here, where folks are seeing the timeout error before five minutes. We see the timeout error around 5 minutes.
Here are some of our specs:
ec2 github runner version: v2.4.2
instance size: c5.18xlarge
OS: Ubuntu, 22.04
We pinned our version awhile back because we were running into some errors.
Log:
Using individual parameters as a single availability zone configuration
GitHub Registration Token is received
Attempting to start EC2 instance using 1 availability zone configuration(s)
Trying availability zone configuration 1/1
Using imageId: ami-00b26e0e6689fbfc8, subnetId: ***, securityGroupId: ***, region: us-west-2
Successfully started AWS EC2 instance i-0da07ab1c7dff13ee using availability zone configuration 1 in region us-west-2
Using region us-west-2 for checking instance i-0da07ab1c7dff13ee status
Checking for instance i-0da07ab1c7dff13ee to be up and running
AWS EC2 instance i-0da07ab1c7dff13ee is up and running
Waiting 30s for the AWS EC2 instance to be registered in GitHub as a new self-hosted runner
Checking every 10s if the GitHub self-hosted runner is registered
The maximum waiting time is 5 minutes
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Checking...
Error: GitHub self-hosted runner registration error
Error: A timeout of 5 minutes is exceeded. Your AWS EC2 instance was not able to register itself in GitHub as a new self-hosted runner.
I have a job where I run 4+ runners in parallel. Generally we were getting pretty good performance where all were running, with the occasional failure where a GH runner was not established correctly. However - recently we've been noticing that failure occurring more frequently. This is different than some of the other issues on here, where folks are seeing the timeout error before five minutes. We see the timeout error around 5 minutes.
Here are some of our specs:
ec2 github runner version: v2.4.2
instance size: c5.18xlarge
OS: Ubuntu, 22.04
We pinned our version awhile back because we were running into some errors.
Log: