runner icon indicating copy to clipboard operation
runner copied to clipboard

Auto update fails to restart runner due to missing file

Open maskati opened this issue 1 year ago • 1 comments

Describe the bug I am seeing failures in containerized runner restart following auto update. For some reason the update results in missing files resulting in bin/Runner.Listener: No such file or directory.

08:40:53.2260000Z: stdout - Current runner version: '2.308.0'
08:40:53.2300000Z: stdout - 2023-09-20 08:40:53Z: Listening for Jobs
08:41:00.5760000Z: stdout - Runner update in progress, do not shutdown runner.
08:41:01.4770000Z: stdout - Downloading 2.309.0 runner
08:41:34.6430000Z: stdout - Waiting for current job finish running.
08:41:34.7800000Z: stdout - Generate and execute update script.
08:41:34.9050000Z: stdout - Runner will exit shortly for update, should be back online within 10 seconds.
08:41:35.0680000Z: stdout - Runner update process finished.
08:41:35.5710000Z: stdout - Runner listener exit because of updating, re-launch runner after successful update
08:42:06.0680000Z: stdout - Restarting runner...
08:42:06.1730000Z: stdout - /home/actions/run-helper.sh: line 36: /home/actions/bin/Runner.Listener: No such file or directory
08:42:06.1730000Z: stdout - Exiting runner...
08:42:06.1730000Z: stdout - Exiting with unknown error code: 127

Runner Version and Platform

Linux 2.308.0 being updated to 2.309.0.

maskati avatar Sep 20 '23 09:09 maskati