{"version":"2.1.271","anchor":"self-hosted-runner-session-start-now-probes-the-session-conf","canonical_anchor":"self-hosted-runner-session-start-now-probes-the-session-conf","heading":"Self-hosted runner session start now probes the session config dir before proceeding","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/self-hosted-runner-session-start-now-probes-the-session-conf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Self-hosted runner session start now probes the session config dir before proceeding\n\nSelf-hosted runner sessions now check the config directory's health before starting, flagging stuck NFS\/CSI mounts\n\n**What**\n\nWhen a self-hosted runner starts a new session, it now runs an explicit check to see if the session's config directory is reachable, logging `[runner:stuck] session config dir check ... (check NFS\/CSI mount health)` if something's wrong. This check happens before the runner sets up the rest of the session's internal state. If the check hits an unrecoverable error, a new failure flag is set that causes later cleanup steps to be skipped.\n\n**Why**\n\nThis helps diagnose sessions that hang because of a broken or slow network filesystem mount (NFS or CSI), pointing operators at the mount as the likely cause instead of leaving the session silently stuck.\n\n- Area: Self-Hosted Runner\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}