Self-hosted runners: error has been observed at the following site(s)

[Lou Andrew Navarro]

I have a self-hosted macos runner and it was running perfectly back then but now whenever there is a new build it throws an error. httpStatusCode: 409 ... because the update was based upon an out-of-date version of the step entity.

Resulting to not being able to clone the repository. 

[Patrik S · Accepted solution]

Hello @Lou Andrew Navarro and welcome to the Community!

The 409 status code indicates "Conflict", which may suggest that you possibly have more than one instance of the same runner being executed.

In this case, for testing porpoises, I would suggest trying to create a new runner from scratch in the UI, leave just that runner online temporarily, and test again if your pipeline now succeeds. This will help in narrowing down if the issue is related to multiple instances of the same runners being executed at the same time.

If after creating the new runner you are still facing the same issue, we kindly ask you to share the full runners logs here containing the error so we can assist you further.

Thank you, @Lou Andrew Navarro !

Patrik S

[Lou Andrew Navarro]

Thanks for the response. 

What I did was I cloned a working runner and used it to create a new one just to save time with the installations. I added that new runner with different IDs. Should that be a reason for “conflict”? 

[Lou Andrew Navarro]

I'm now getting this error when running the pipeline: 

[Patrik S]

Hello @Lou Andrew Navarro ,

It's fine to use the same installation. The runner executable is the same, it's just the command with the IDs that will differentiate one runner from another.

As you mentioned you started both runners using the different IDs you were given when creating them in the UI, there should be no conflict. It would only be a conflict if you started two runners with the exact same IDs.

In order for us to investigate what else might be causing this, would it be possible for you to : 

1. Create a new macOS runner in the UI and start it on the machine
2. Trigger a build for that runner and wait it to fail
3. Share the full runner log output (the output of the terminal where runner is being executed)

At this point we'd like to understand if there's anything else in the runner logs that stands out. When sharing the logs here, please make sure to sanitize any sensitive information, as this is a public forum.

Thank you, @Lou Andrew Navarro !

Patrik S

[Lou Andrew Navarro]

Hi, this is the full runner log output. It's failing on the clone part of the build. Any ideas what's causing this?

[Theodora Boudale]

Hi Lou Andrew,

Please allow me to step in as Patrik is out of office at the moment.

The latest log shows the following error:

We couldn't clone the repository. Try rerunning the pipeline.

I've seen this error occur with MacOS runners when a runner is stopped and then restarted because the Java process for the runner was not stopped or killed when exiting the runner. This is one possible cause for the error.

Can you please try the following:

- stop the runners
- check Activity Monitor on your Mac for any running Java processes
- if there are any, stop them from the Activity Monitor
- then start the runner again

If this doesn't solve the issue, please reach out via the support ticket you created and provide the build URL and details asked by my colleague.

Kind regards,
Theodora

[Lou Andrew Navarro]

Hi, apologies for not responding back immediately. I've been monitoring the runners lately, and builds have been successful at the moment. Thanks for the help! 

Also, Theodora, I think what you've mentioned is a big help. I'll take note of that next time I encounter this error. 

[Theodora Boudale]

That's good to hear Lou Andrew, thank you for the update! Please feel free to reach out if you ever need anything else!