Failed to start gunicorn.socket: Unit gunicorn.socket is masked

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












While trying to start gunicorn I get this error,



Failed to start gunicorn.socket: Unit gunicorn.socket is masked.


How do you solve it?










share|improve this question









New contributor




nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.























    up vote
    1
    down vote

    favorite












    While trying to start gunicorn I get this error,



    Failed to start gunicorn.socket: Unit gunicorn.socket is masked.


    How do you solve it?










    share|improve this question









    New contributor




    nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      While trying to start gunicorn I get this error,



      Failed to start gunicorn.socket: Unit gunicorn.socket is masked.


      How do you solve it?










      share|improve this question









      New contributor




      nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      While trying to start gunicorn I get this error,



      Failed to start gunicorn.socket: Unit gunicorn.socket is masked.


      How do you solve it?







      ubuntu systemd






      share|improve this question









      New contributor




      nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 3 hours ago









      Filipe Brandenburger

      5,2441624




      5,2441624






      New contributor




      nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 3 hours ago









      nvim

      61




      61




      New contributor




      nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      nvim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          You can unmask the unit with the following command:



          systemctl unmask gunicorn.socket


          That will allow you to start the unit again.



          A masked unit is an unit that has been prevented from starting. From the systemd documentation:




          masked: Completely disabled, so that any start operation on it fails (permanently in /etc/systemd/system/ or transiently in /run/systemd/systemd/).




          There might be a reason why the unit was masked in your system (maybe you or another system administrator masked it before?) So consider that fact while you ponder whether unmasking it is the correct approach.



          You can use the systemctl is-enabled command to check whether a unit is masked (or, more generally, what the enablement state of the unit is.)






          share|improve this answer






















            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            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',
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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
            );



            );






            nvim is a new contributor. Be nice, and check out our Code of Conduct.









             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481015%2ffailed-to-start-gunicorn-socket-unit-gunicorn-socket-is-masked%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            You can unmask the unit with the following command:



            systemctl unmask gunicorn.socket


            That will allow you to start the unit again.



            A masked unit is an unit that has been prevented from starting. From the systemd documentation:




            masked: Completely disabled, so that any start operation on it fails (permanently in /etc/systemd/system/ or transiently in /run/systemd/systemd/).




            There might be a reason why the unit was masked in your system (maybe you or another system administrator masked it before?) So consider that fact while you ponder whether unmasking it is the correct approach.



            You can use the systemctl is-enabled command to check whether a unit is masked (or, more generally, what the enablement state of the unit is.)






            share|improve this answer


























              up vote
              0
              down vote













              You can unmask the unit with the following command:



              systemctl unmask gunicorn.socket


              That will allow you to start the unit again.



              A masked unit is an unit that has been prevented from starting. From the systemd documentation:




              masked: Completely disabled, so that any start operation on it fails (permanently in /etc/systemd/system/ or transiently in /run/systemd/systemd/).




              There might be a reason why the unit was masked in your system (maybe you or another system administrator masked it before?) So consider that fact while you ponder whether unmasking it is the correct approach.



              You can use the systemctl is-enabled command to check whether a unit is masked (or, more generally, what the enablement state of the unit is.)






              share|improve this answer
























                up vote
                0
                down vote










                up vote
                0
                down vote









                You can unmask the unit with the following command:



                systemctl unmask gunicorn.socket


                That will allow you to start the unit again.



                A masked unit is an unit that has been prevented from starting. From the systemd documentation:




                masked: Completely disabled, so that any start operation on it fails (permanently in /etc/systemd/system/ or transiently in /run/systemd/systemd/).




                There might be a reason why the unit was masked in your system (maybe you or another system administrator masked it before?) So consider that fact while you ponder whether unmasking it is the correct approach.



                You can use the systemctl is-enabled command to check whether a unit is masked (or, more generally, what the enablement state of the unit is.)






                share|improve this answer














                You can unmask the unit with the following command:



                systemctl unmask gunicorn.socket


                That will allow you to start the unit again.



                A masked unit is an unit that has been prevented from starting. From the systemd documentation:




                masked: Completely disabled, so that any start operation on it fails (permanently in /etc/systemd/system/ or transiently in /run/systemd/systemd/).




                There might be a reason why the unit was masked in your system (maybe you or another system administrator masked it before?) So consider that fact while you ponder whether unmasking it is the correct approach.



                You can use the systemctl is-enabled command to check whether a unit is masked (or, more generally, what the enablement state of the unit is.)







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 3 hours ago

























                answered 3 hours ago









                Filipe Brandenburger

                5,2441624




                5,2441624




















                    nvim is a new contributor. Be nice, and check out our Code of Conduct.









                     

                    draft saved


                    draft discarded


















                    nvim is a new contributor. Be nice, and check out our Code of Conduct.












                    nvim is a new contributor. Be nice, and check out our Code of Conduct.











                    nvim is a new contributor. Be nice, and check out our Code of Conduct.













                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481015%2ffailed-to-start-gunicorn-socket-unit-gunicorn-socket-is-masked%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Bahrain

                    Postfix configuration issue with fips on centos 7; mailgun relay