The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

[HarshadDGhorpade-eaton]

Describe the bug
Time to time we're getting this error and workflow is getting canceled due to that, its very frustating. We have looked into couple of other issues as well:
The runner has received a shutdown signal. · Issue #6709 · actions/runner-images

The runner has received a shutdown signal. · actions/runner-images · Discussion #7188

we have reduced number of threads needed for our build to 28 from total capacity of 32 but still its same.

Runner Version and Platform

Runner version : '2.322.0'
We're using larger runner with 32 cores
Image: ubuntu-22.04
Version: 20250209.1.0

OS of the machine running the runner? OSX/Windows/Linux/...
OS : Ubuntu 22.04.5

What's not working?

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Process completed with exit code 137.
The operation was canceled.

[matanbaruch]

We are facing the same issue and have conducted several debugging steps:

1. Increased Resources: Upgraded runners from 4 CPU / 16GB RAM to 8 CPU / 32GB RAM—no improvement.
2. Resource Starvation: No signs of CPU/memory exhaustion; Grafana shows nodes staying well below 10% utilization.
3. Network Stability: No network disruptions observed; runner connects successfully but stops unexpectedly after a few minutes.
4. Logs: No meaningful logs indicating the cause of disconnection or failure.
5. Runner Status: Manually connecting to the runner shows it functioning normally, not stuck or unresponsive.
6. Version Downgrade: Rolling back from 2.322.0 to 2.321.0 had no effect.
7. Kubernetes Setup: Running on Kubernetes using the new GitHub Actions Runner Controller 0.10.2 (migrated from summerwinds).
8. OS Upgrade Suspicions: We suspect a potential issue with the Ubuntu 24.04 upgrade, but no confirmation yet.
9. Custom Docker Image: Based on the official GitHub Actions runner image, adding necessary tools on top.
10. GitHub API Rate Limits: No signs of hitting rate limits; GitHub.com statistics show no related errors.
11. Time-Based Pattern?: Failure happens more often at night (US time), but this is an observation, not a confirmed cause.

Any insights or guidance on further debugging steps would be greatly appreciated!