<div id="readability-page-1" class="page"><div id="dkContent" role="main">

					

					<p>
						<h2><span>솜씨좋은장씨</span></h2>
					</p>

					                
                    
						


						
							
							<div>
								<p><strong><a href="/category/%EC%9C%A0%EC%9A%A9%ED%95%9C%20%EC%A0%95%EB%B3%B4/Git%20%7C%20GitHub">유용한 정보/Git | GitHub</a></strong></p><h3>[GitHub] actions-runner svc.sh 활용하여 서비스 등록 후 실행 시 발생하는 Active: failed (code=exited, status=203/EXEC) 해결 방법</h3>
								<p><span>솜씨좋은장씨
                                <span></span>2023. 8. 11. 00:05
								
							</span>
							</p></div>

							<div><figure data-ke-mobilestyle="widthOrigin" data-origin-width="1200" data-origin-height="630"><span data-url="https://blog.kakaocdn.net/dn/dKt5VU/btsqR9XPXiA/l4Tx8NF7k2vHMQ0bPXBAsK/img.png" data-lightbox="lightbox"><img src="https://blog.kakaocdn.net/dn/dKt5VU/btsqR9XPXiA/l4Tx8NF7k2vHMQ0bPXBAsK/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="1200" data-origin-height="630"></span></figure>

<p data-ke-size="size18">최근 작업을 하면서 GitHub 에 있는 actions runner 를 알게되었습니다.</p>
<p data-ke-size="size18">GitHub Repo 의 actions-runner 추가 페이지에 들어가서 나오는 코드들을 복사 붙여넣기만 하면&nbsp;</p>
<p data-ke-size="size18"><span>누구나<span>&nbsp;초기설정을 쉽게 할 수 있는 장점이 있어서</span></span></p>
<p data-ke-size="size18">개발 서버 코드 배포에도 테스트에도 잘 활용을 하고 있습니다.</p>

<p data-ke-size="size18">그러던 오늘! 오늘도 여느 때와 같이 신나게 세팅을 하고!&nbsp;</p>
<p data-ke-size="size18"><a href="https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service" target="_blank" rel="noopener">https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service</a></p>
<figure id="og_1691678336477" contenteditable="false" data-ke-type="opengraph" data-ke-align="alignCenter" data-og-type="article" data-og-title="Configuring the self-hosted runner application as a service - GitHub Docs" data-og-description="You can configure the self-hosted runner application as a service to automatically start the runner application when the machine starts." data-og-host="docs.github.com" data-og-source-url="https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service" data-og-url="https://ghdocs-prod.azurewebsites.net/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service" data-og-image="https://scrap.kakaocdn.net/dn/ERW1I/hyTBFoj2vy/sTSYKXWmCMqgHqwa4KVXx0/img.png?width=1200&amp;height=1200&amp;face=0_0_1200_1200"><a href="https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service" target="_blank" rel="noopener" data-source-url="https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service">

<div>
<p data-ke-size="size16">Configuring the self-hosted runner application as a service - GitHub Docs</p>
<p data-ke-size="size16">You can configure the self-hosted runner application as a service to automatically start the runner application when the machine starts.</p>
<p data-ke-size="size16">docs.github.com</p>
</div>
</a><img src="https://scrap.kakaocdn.net/dn/ERW1I/hyTBFoj2vy/sTSYKXWmCMqgHqwa4KVXx0/img.png?width=1200&amp;height=1200&amp;face=0_0_1200_1200"></figure>
<p data-ke-size="size18">위 방법 따라서 서비스로 띄우려고 하던 때였습니다.</p>
<h3 data-ke-size="size23"><b>🚨 에러 발생 🚨</b></h3>
<p data-ke-size="size18">svc.sh 를 활용하여 install 한 뒤 start 를 하려고 했을때 에러가 발생했습니다.</p>
<pre id="code_1691678678922" data-ke-language="bash" data-ke-type="codeblock"><code>[root@dev actions-runner]# sudo ./svc.sh start

/etc/systemd/system/actions.runner.dev.service
● actions.runner.42maru-ai-qa-solution-api.sitebunny-qa-dev.service - GitHub Actions Runner (42maru-ai-qa-solution-api.sitebunny-qa-dev)
   Loaded: loaded (/etc/systemd/system/actions.runner.dev.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2023-08-10 22:48:11 KST; 6ms ago
  Process: 15642 ExecStart=/home/dev/actions-runner/runsvc.sh (code=exited, status=203/EXEC)
 Main PID: 15642 (code=exited, status=203/EXEC)

Aug 10 22:48:11 dev systemd[1]: Started GitHub Actions Runner (dev).
Aug 10 22:48:11 dev systemd[1]: actions.runner.dev.service: Main process exited, code=exited, status=203/EXEC
Aug 10 22:48:11 dev systemd[1]: actions.runner.dev.service: Failed with result 'exit-code'.</code></pre>

<p data-ke-size="size18">평소에는 잘 동작했던지라 당황스러웠지만!</p>
<p data-ke-size="size18">Active: failed 와 (code=exited, status=203/EXEC) 라는 단서를 가지고 찾아보니&nbsp;</p>
<p data-ke-size="size18">뭔가 ExecStart= ~~ 이 값 관련하여 수정하면 될 것 같았습니다.</p>
<h3 data-ke-size="size23"><b>📝 수정해보기 📝</b></h3>
<p data-ke-size="size18">ExecStart 를 바꾸려고 보니 조금 전 실행했던 svc.sh 에는 ExecStart 라는 값이 보이지 않았습니다.</p>
<pre id="code_1691679442785" data-ke-language="bash" data-ke-type="codeblock"><code>[root@sitebunny-qa-dev actions-runner]# grep ExecStart */*
bin/actions.runner.service.template:ExecStart={{RunnerRoot}}/runsvc.sh
grep: bin/checkScripts: Is a directory
grep: bin/hashFiles: Is a directory
grep: externals/node12: Is a directory
grep: externals/node12_alpine: Is a directory
grep: externals/node16: Is a directory
grep: externals/node16_alpine: Is a directory</code></pre>
<p data-ke-size="size18">grep 명령어로 찾아보니! bin 하위 actons.runner.service.template 위치에 있었습니다.</p>
<pre id="code_1691679612107" data-ke-language="bash" data-ke-type="codeblock"><code>[root@sitebunny-qa-dev actions-runner]# vi bin/actions.runner.service.template</code></pre>
<p data-ke-size="size18">바로 vi 로 수정해주었습니다.&nbsp;</p>
<pre id="code_1691679599099" data-ke-language="bash" data-ke-type="codeblock"><code># 기존 
[Unit]
Description={{Description}}
After=network.target

[Service]
ExecStart={{RunnerRoot}}/runsvc.sh
User={{User}}
WorkingDirectory={{RunnerRoot}}
KillMode=process
KillSignal=SIGTERM
TimeoutStopSec=5min


# 변경
[Install]
WantedBy=multi-user.target

[Unit]
Description={{Description}}
After=network.target

[Service]
ExecStart=/bin/bash {{RunnerRoot}}/runsvc.sh
User={{User}}
WorkingDirectory={{RunnerRoot}}
KillMode=process
KillSignal=SIGTERM
TimeoutStopSec=5min

[Install]
WantedBy=multi-user.target</code></pre>
<p data-ke-size="size18">기존 ExecStart={{RunnerRoot}}/runsvc.sh 에서</p>
<p data-ke-size="size18">{{RunnerRoot}} 앞에 /bin/bash 를 붙인 다음</p>
<p data-ke-size="size18">ExecStart=/bin/bash {{RunnerRoot}}/runsvc/sh 로 변경하고 저장하였습니다.</p>
<h3 data-ke-size="size23"><b>😃 해결! 😃</b></h3>
<p data-ke-size="size18">위와 같이 수정하고 다시 sudo ./svc.sh start 를 진행하니!</p>
<pre id="code_1691679894044" data-ke-language="bash" data-ke-type="codeblock"><code>[root@dev actions-runner]# sudo ./svc.sh start

/etc/systemd/system/actions.runner.dev.service
● actions.runner.dev.service - GitHub Actions Runner (dev)
   Loaded: loaded (/etc/systemd/system/actions.runner.dev.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2023-08-10 22:48:36 KST; 13ms ago
 Main PID: 15811 (bash)
    Tasks: 2 (limit: 383893)
   Memory: 4.8M
   CGroup: /system.slice/actions.runner.dev.service
           ├─15811 /bin/bash /home/qa42/actions-runner/runsvc.sh
           └─15814 ./externals/node16/bin/node ./bin/RunnerService.js

Aug 10 22:48:36 dev systemd[1]: Started GitHub Actions Runner (dev).
Aug 10 22:48:36 dev bash[15811]: .path=/home/qa42/.local/bin:/home/qa42/bin:/sbin:/bin:/usr/sbin:/usr/bin</code></pre>
<p data-ke-size="size18">문제없이 잘 진행되는 것을 확인하였습니다.</p>

<p data-ke-size="size18">앞으로 actions-runner 를 활용하여 이것 저것 많이 해볼 예정입니다.</p>
<p data-ke-size="size18">읽어주셔서 감사합니다.</p></div>
							

							
								
							

							


						
					
                    
                

					

					

					

					

					

					
				</div></div>

솜씨좋은장씨

최근 작업을 하면서 GitHub 에 있는 actions runner 를 알게되었습니다.
GitHub Repo 의 actions-runner 추가 페이지에 들어가서 나오는 코드들을 복사 붙여넣기만 하면 
누구나 초기설정을 쉽게 할 수 있는 장점이 있어서
개발 서버 코드 배포에도 테스트에도 잘 활용을 하고 있습니다.
 
그러던 오늘! 오늘도 여느 때와 같이 신나게 세팅을 하고! 
https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service
위 방법 따라서 서비스로 띄우려고 하던 때였습니다.
  에러 발생  
svc.sh 를 활용하여 install 한 뒤 start 를 하려고 했을때 에러가 발생했습니다.
[root@dev actions-runner]# sudo ./svc.sh start
/etc/systemd/system/actions.runner.dev.service
● actions.runner.42maru-ai-qa-solution-api.sitebunny-qa-dev.service - GitHub Actions Runner (42maru-ai-qa-solution-api.sitebunny-qa-dev)
   Loaded: loaded (/etc/systemd/system/actions.runner.dev.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2023-08-10 22:48:11 KST; 6ms ago
  Process: 15642 ExecStart=/home/dev/actions-runner/runsvc.sh (code=exited, status=203/EXEC)
 Main PID: 15642 (code=exited, status=203/EXEC)
Aug 10 22:48:11 dev systemd[1]: Started GitHub Actions Runner (dev).
Aug 10 22:48:11 dev systemd[1]: actions.runner.dev.service: Main process exited, code=exited, status=203/EXEC
Aug 10 22:48:11 dev systemd[1]: actions.runner.dev.service: Failed with result 'exit-code'.
 
평소에는 잘 동작했던지라 당황스러웠지만!
Active: failed 와 (code=exited, status=203/EXEC) 라는 단서를 가지고 찾아보니 
뭔가 ExecStart= ~~ 이 값 관련하여 수정하면 될 것 같았습니다.
  수정해보기  
ExecStart 를 바꾸려고 보니 조금 전 실행했던 svc.sh 에는 ExecStart 라는 값이 보이지 않았습니다.
[root@sitebunny-qa-dev actions-runner]# grep ExecStart */*
bin/actions.runner.service.template:ExecStart={{RunnerRoot}}/runsvc.sh
grep: bin/checkScripts: Is a directory
grep: bin/hashFiles: Is a directory
grep: externals/node12: Is a directory
grep: externals/node12_alpine: Is a directory
grep: externals/node16: Is a directory
grep: externals/node16_alpine: Is a directory
grep 명령어로 찾아보니! bin 하위 actons.runner.service.template 위치에 있었습니다.
[root@sitebunny-qa-dev actions-runner]# vi bin/actions.runner.service.template
바로 vi 로 수정해주었습니다. 
# 기존 
[Unit]
Description={{Description}}
After=network.target
[Service]
ExecStart={{RunnerRoot}}/runsvc.sh
User={{User}}
WorkingDirectory={{RunnerRoot}}
KillMode=process
KillSignal=SIGTERM
TimeoutStopSec=5min
# 변경
[Install]
WantedBy=multi-user.target
[Unit]
Description={{Description}}
After=network.target
[Service]
ExecStart=/bin/bash {{RunnerRoot}}/runsvc.sh
User={{User}}
WorkingDirectory={{RunnerRoot}}
KillMode=process
KillSignal=SIGTERM
TimeoutStopSec=5min
[Install]
WantedBy=multi-user.target
기존 ExecStart={{RunnerRoot}}/runsvc.sh 에서
{{RunnerRoot}} 앞에 /bin/bash 를 붙인 다음
ExecStart=/bin/bash {{RunnerRoot}}/runsvc/sh 로 변경하고 저장하였습니다.
  해결!  
위와 같이 수정하고 다시 sudo ./svc.sh start 를 진행하니!
[root@dev actions-runner]# sudo ./svc.sh start
/etc/systemd/system/actions.runner.dev.service
● actions.runner.dev.service - GitHub Actions Runner (dev)
   Loaded: loaded (/etc/systemd/system/actions.runner.dev.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2023-08-10 22:48:36 KST; 13ms ago
 Main PID: 15811 (bash)
    Tasks: 2 (limit: 383893)
   Memory: 4.8M
   CGroup: /system.slice/actions.runner.dev.service
           ├─15811 /bin/bash /home/qa42/actions-runner/runsvc.sh
           └─15814 ./externals/node16/bin/node ./bin/RunnerService.js
Aug 10 22:48:36 dev systemd[1]: Started GitHub Actions Runner (dev).
Aug 10 22:48:36 dev bash[15811]: .path=/home/qa42/.local/bin:/home/qa42/bin:/sbin:/bin:/usr/sbin:/usr/bin
문제없이 잘 진행되는 것을 확인하였습니다.
 
앞으로 actions-runner 를 활용하여 이것 저것 많이 해볼 예정입니다.
읽어주셔서 감사합니다.

[GitHub] actions-runner svc.sh 활용하여 서비스 등록 후 실행 시 발생하는 Active: failed (code=exited, status=203/EXEC) 해결 방법

댓글