How do you stop or prevent gitlab from running on startup?












11















I've installed gitlab on Ubuntu 14.04, from the following deb file:



gitlab_6.9.2-omnibus-1_amd64.deb


It works beautifully. But I want to perform some maintenance on the box without gitlab running, and I can't find anyway to do this.



There is nothing in cron, nothing in /etc/init.d that I can see.



All the documentation points to /home/gitlab as the root folder, where in mine it's /var/opt/gitlab and some others.



I see it's running nginx, postgres & redis. I can kill the individual components, and hopefully that would be enough, but I'd rather it shutdown cleanly, or just not start. These components are not part of the /etc/init.d system ...



Any ideas?










share|improve this question























  • see stackoverflow.com/a/35902817 for systemd based systems

    – x29a
    Mar 21 '17 at 5:20
















11















I've installed gitlab on Ubuntu 14.04, from the following deb file:



gitlab_6.9.2-omnibus-1_amd64.deb


It works beautifully. But I want to perform some maintenance on the box without gitlab running, and I can't find anyway to do this.



There is nothing in cron, nothing in /etc/init.d that I can see.



All the documentation points to /home/gitlab as the root folder, where in mine it's /var/opt/gitlab and some others.



I see it's running nginx, postgres & redis. I can kill the individual components, and hopefully that would be enough, but I'd rather it shutdown cleanly, or just not start. These components are not part of the /etc/init.d system ...



Any ideas?










share|improve this question























  • see stackoverflow.com/a/35902817 for systemd based systems

    – x29a
    Mar 21 '17 at 5:20














11












11








11


5






I've installed gitlab on Ubuntu 14.04, from the following deb file:



gitlab_6.9.2-omnibus-1_amd64.deb


It works beautifully. But I want to perform some maintenance on the box without gitlab running, and I can't find anyway to do this.



There is nothing in cron, nothing in /etc/init.d that I can see.



All the documentation points to /home/gitlab as the root folder, where in mine it's /var/opt/gitlab and some others.



I see it's running nginx, postgres & redis. I can kill the individual components, and hopefully that would be enough, but I'd rather it shutdown cleanly, or just not start. These components are not part of the /etc/init.d system ...



Any ideas?










share|improve this question














I've installed gitlab on Ubuntu 14.04, from the following deb file:



gitlab_6.9.2-omnibus-1_amd64.deb


It works beautifully. But I want to perform some maintenance on the box without gitlab running, and I can't find anyway to do this.



There is nothing in cron, nothing in /etc/init.d that I can see.



All the documentation points to /home/gitlab as the root folder, where in mine it's /var/opt/gitlab and some others.



I see it's running nginx, postgres & redis. I can kill the individual components, and hopefully that would be enough, but I'd rather it shutdown cleanly, or just not start. These components are not part of the /etc/init.d system ...



Any ideas?







linux ubuntu git gitlab






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Sep 23 '14 at 10:36









Jim TJim T

366128




366128













  • see stackoverflow.com/a/35902817 for systemd based systems

    – x29a
    Mar 21 '17 at 5:20



















  • see stackoverflow.com/a/35902817 for systemd based systems

    – x29a
    Mar 21 '17 at 5:20

















see stackoverflow.com/a/35902817 for systemd based systems

– x29a
Mar 21 '17 at 5:20





see stackoverflow.com/a/35902817 for systemd based systems

– x29a
Mar 21 '17 at 5:20










4 Answers
4






active

oldest

votes


















17














Found the answer. Most of the configuration appears to be in:



/var/opt/gitlab/gitlab-rails/etc


Whose config.yml file mentions gitlab-ctl, which is available everywhere as a command:



gitlab-ctl stop


Stops gitlab fully.






share|improve this answer



















  • 4





    But how do I stop it loading at startup?

    – mjaggard
    Oct 20 '15 at 13:52



















4














To disable gitlab from autostarting in ubuntu 14.04



echo manual | sudo tee /etc/init/gitlab-runsvdir.override


how does it work?






share|improve this answer

































    0














    For those who want to reenable their gitlab autostart script and corrupted their
    startup script like I did.

    This is the default config of /etc/init/gitlab-runsvdir.override



    start on runlevel [2345]
    stop on shutdown
    respawn
    post-stop script
    # To avoid stomping on runsv's owned by a different runsvdir
    # process, kill any runsv process that has been orphaned, and is
    # now owned by init (process 1).
    pkill -HUP -P 1 runsv$
    end script
    exec /opt/gitlab/embedded/bin/runsvdir-start





    share|improve this answer


























    • Yes, this is the answere to re-enable it. Because after using the command mdma provided, you wont be able to re-enable gitlab because the default content of gitlab-runsvdir.override will be lost. I had this issue by reading this answere

      – leabut
      Sep 30 '17 at 21:56





















    0














    For those who have /etc/inittab, check if it contains a line such as



    CS:123456:respawn:/opt/gitlab/embedded/bin/runsvdir-start


    and comment this line.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f815464%2fhow-do-you-stop-or-prevent-gitlab-from-running-on-startup%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      17














      Found the answer. Most of the configuration appears to be in:



      /var/opt/gitlab/gitlab-rails/etc


      Whose config.yml file mentions gitlab-ctl, which is available everywhere as a command:



      gitlab-ctl stop


      Stops gitlab fully.






      share|improve this answer



















      • 4





        But how do I stop it loading at startup?

        – mjaggard
        Oct 20 '15 at 13:52
















      17














      Found the answer. Most of the configuration appears to be in:



      /var/opt/gitlab/gitlab-rails/etc


      Whose config.yml file mentions gitlab-ctl, which is available everywhere as a command:



      gitlab-ctl stop


      Stops gitlab fully.






      share|improve this answer



















      • 4





        But how do I stop it loading at startup?

        – mjaggard
        Oct 20 '15 at 13:52














      17












      17








      17







      Found the answer. Most of the configuration appears to be in:



      /var/opt/gitlab/gitlab-rails/etc


      Whose config.yml file mentions gitlab-ctl, which is available everywhere as a command:



      gitlab-ctl stop


      Stops gitlab fully.






      share|improve this answer













      Found the answer. Most of the configuration appears to be in:



      /var/opt/gitlab/gitlab-rails/etc


      Whose config.yml file mentions gitlab-ctl, which is available everywhere as a command:



      gitlab-ctl stop


      Stops gitlab fully.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Sep 23 '14 at 10:45









      Jim TJim T

      366128




      366128








      • 4





        But how do I stop it loading at startup?

        – mjaggard
        Oct 20 '15 at 13:52














      • 4





        But how do I stop it loading at startup?

        – mjaggard
        Oct 20 '15 at 13:52








      4




      4





      But how do I stop it loading at startup?

      – mjaggard
      Oct 20 '15 at 13:52





      But how do I stop it loading at startup?

      – mjaggard
      Oct 20 '15 at 13:52













      4














      To disable gitlab from autostarting in ubuntu 14.04



      echo manual | sudo tee /etc/init/gitlab-runsvdir.override


      how does it work?






      share|improve this answer






























        4














        To disable gitlab from autostarting in ubuntu 14.04



        echo manual | sudo tee /etc/init/gitlab-runsvdir.override


        how does it work?






        share|improve this answer




























          4












          4








          4







          To disable gitlab from autostarting in ubuntu 14.04



          echo manual | sudo tee /etc/init/gitlab-runsvdir.override


          how does it work?






          share|improve this answer















          To disable gitlab from autostarting in ubuntu 14.04



          echo manual | sudo tee /etc/init/gitlab-runsvdir.override


          how does it work?







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 13 '17 at 12:23









          Community

          1




          1










          answered Sep 16 '16 at 9:57









          zenithzenith

          1412




          1412























              0














              For those who want to reenable their gitlab autostart script and corrupted their
              startup script like I did.

              This is the default config of /etc/init/gitlab-runsvdir.override



              start on runlevel [2345]
              stop on shutdown
              respawn
              post-stop script
              # To avoid stomping on runsv's owned by a different runsvdir
              # process, kill any runsv process that has been orphaned, and is
              # now owned by init (process 1).
              pkill -HUP -P 1 runsv$
              end script
              exec /opt/gitlab/embedded/bin/runsvdir-start





              share|improve this answer


























              • Yes, this is the answere to re-enable it. Because after using the command mdma provided, you wont be able to re-enable gitlab because the default content of gitlab-runsvdir.override will be lost. I had this issue by reading this answere

                – leabut
                Sep 30 '17 at 21:56


















              0














              For those who want to reenable their gitlab autostart script and corrupted their
              startup script like I did.

              This is the default config of /etc/init/gitlab-runsvdir.override



              start on runlevel [2345]
              stop on shutdown
              respawn
              post-stop script
              # To avoid stomping on runsv's owned by a different runsvdir
              # process, kill any runsv process that has been orphaned, and is
              # now owned by init (process 1).
              pkill -HUP -P 1 runsv$
              end script
              exec /opt/gitlab/embedded/bin/runsvdir-start





              share|improve this answer


























              • Yes, this is the answere to re-enable it. Because after using the command mdma provided, you wont be able to re-enable gitlab because the default content of gitlab-runsvdir.override will be lost. I had this issue by reading this answere

                – leabut
                Sep 30 '17 at 21:56
















              0












              0








              0







              For those who want to reenable their gitlab autostart script and corrupted their
              startup script like I did.

              This is the default config of /etc/init/gitlab-runsvdir.override



              start on runlevel [2345]
              stop on shutdown
              respawn
              post-stop script
              # To avoid stomping on runsv's owned by a different runsvdir
              # process, kill any runsv process that has been orphaned, and is
              # now owned by init (process 1).
              pkill -HUP -P 1 runsv$
              end script
              exec /opt/gitlab/embedded/bin/runsvdir-start





              share|improve this answer















              For those who want to reenable their gitlab autostart script and corrupted their
              startup script like I did.

              This is the default config of /etc/init/gitlab-runsvdir.override



              start on runlevel [2345]
              stop on shutdown
              respawn
              post-stop script
              # To avoid stomping on runsv's owned by a different runsvdir
              # process, kill any runsv process that has been orphaned, and is
              # now owned by init (process 1).
              pkill -HUP -P 1 runsv$
              end script
              exec /opt/gitlab/embedded/bin/runsvdir-start






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Sep 30 '17 at 22:02

























              answered Sep 29 '17 at 14:15









              leabutleabut

              11




              11













              • Yes, this is the answere to re-enable it. Because after using the command mdma provided, you wont be able to re-enable gitlab because the default content of gitlab-runsvdir.override will be lost. I had this issue by reading this answere

                – leabut
                Sep 30 '17 at 21:56





















              • Yes, this is the answere to re-enable it. Because after using the command mdma provided, you wont be able to re-enable gitlab because the default content of gitlab-runsvdir.override will be lost. I had this issue by reading this answere

                – leabut
                Sep 30 '17 at 21:56



















              Yes, this is the answere to re-enable it. Because after using the command mdma provided, you wont be able to re-enable gitlab because the default content of gitlab-runsvdir.override will be lost. I had this issue by reading this answere

              – leabut
              Sep 30 '17 at 21:56







              Yes, this is the answere to re-enable it. Because after using the command mdma provided, you wont be able to re-enable gitlab because the default content of gitlab-runsvdir.override will be lost. I had this issue by reading this answere

              – leabut
              Sep 30 '17 at 21:56













              0














              For those who have /etc/inittab, check if it contains a line such as



              CS:123456:respawn:/opt/gitlab/embedded/bin/runsvdir-start


              and comment this line.






              share|improve this answer




























                0














                For those who have /etc/inittab, check if it contains a line such as



                CS:123456:respawn:/opt/gitlab/embedded/bin/runsvdir-start


                and comment this line.






                share|improve this answer


























                  0












                  0








                  0







                  For those who have /etc/inittab, check if it contains a line such as



                  CS:123456:respawn:/opt/gitlab/embedded/bin/runsvdir-start


                  and comment this line.






                  share|improve this answer













                  For those who have /etc/inittab, check if it contains a line such as



                  CS:123456:respawn:/opt/gitlab/embedded/bin/runsvdir-start


                  and comment this line.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 7 at 22:10









                  Jong BorJong Bor

                  211128




                  211128






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f815464%2fhow-do-you-stop-or-prevent-gitlab-from-running-on-startup%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Plaza Victoria

                      Puebla de Zaragoza

                      Musa