title: How to solve a stuck Gitlab CI pipeline?
body: <p>We've been using Gitlab CI for some months, and in the last 1 week, we've been using the specific runner installed on a VPS. Currently, we are using "shell" as the executor.</p>
  
  <p>Today our pipeline got stuck out of sudden, when we looked into the server free RAM, it's only 48MB out of 996 MB, FYI, we're using CentOS 6.</p>
  
  <p>We've been struggling to get the answers, but we're stuck at the moment, and would like to know :</p>
  
  <blockquote>
    <ul>
    <li>What's causing the pipeline from getting stuck?</li>
    <li>is it true because of low free RAM?</li>
    <li>Should we use another executor, perhaps SSH or even docker?</li>
    <li>What is the best practices to deal with this kind of problem?</li>
    </ul>
  </blockquote>
  
  <p>We would appreciate any kind of help or directions.</p>