Failed to start nginx - high performance web server












2















I am trying to install Yii and use Nginx service to run my web application. When i try to do



sudo systemctl restart nginx.service, i have an error..



enter image description here



Then i try to see the status and i get this..



enter image description here



i found somewhere that i need to run nginx -t -c /etc/nginx/nginx.conf to see what is causing the error.. but everything is ok. it says, syntax is ok and test is successful.
enter image description here



what seems to be the problem with this.. please help.










share|improve this question























  • Hi, I am also facing this issue on my server. Were you able to solve this?

    – Sandeep C
    May 28 '18 at 12:35
















2















I am trying to install Yii and use Nginx service to run my web application. When i try to do



sudo systemctl restart nginx.service, i have an error..



enter image description here



Then i try to see the status and i get this..



enter image description here



i found somewhere that i need to run nginx -t -c /etc/nginx/nginx.conf to see what is causing the error.. but everything is ok. it says, syntax is ok and test is successful.
enter image description here



what seems to be the problem with this.. please help.










share|improve this question























  • Hi, I am also facing this issue on my server. Were you able to solve this?

    – Sandeep C
    May 28 '18 at 12:35














2












2








2








I am trying to install Yii and use Nginx service to run my web application. When i try to do



sudo systemctl restart nginx.service, i have an error..



enter image description here



Then i try to see the status and i get this..



enter image description here



i found somewhere that i need to run nginx -t -c /etc/nginx/nginx.conf to see what is causing the error.. but everything is ok. it says, syntax is ok and test is successful.
enter image description here



what seems to be the problem with this.. please help.










share|improve this question














I am trying to install Yii and use Nginx service to run my web application. When i try to do



sudo systemctl restart nginx.service, i have an error..



enter image description here



Then i try to see the status and i get this..



enter image description here



i found somewhere that i need to run nginx -t -c /etc/nginx/nginx.conf to see what is causing the error.. but everything is ok. it says, syntax is ok and test is successful.
enter image description here



what seems to be the problem with this.. please help.







nginx yii yii2






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 26 '16 at 6:25









ii--L--iiii--L--ii

94214




94214













  • Hi, I am also facing this issue on my server. Were you able to solve this?

    – Sandeep C
    May 28 '18 at 12:35



















  • Hi, I am also facing this issue on my server. Were you able to solve this?

    – Sandeep C
    May 28 '18 at 12:35

















Hi, I am also facing this issue on my server. Were you able to solve this?

– Sandeep C
May 28 '18 at 12:35





Hi, I am also facing this issue on my server. Were you able to solve this?

– Sandeep C
May 28 '18 at 12:35












3 Answers
3






active

oldest

votes


















0














Run ls -l /usr/share/nginx/ This is where it is looking to save the access logs, check the directory exists and that the user you are running nginx as has write access here.






share|improve this answer
























  • hi Luke. Thanks for your reply. When i run the command, i have access.log and error.log file and html which is a directory. what do you mean by has write access here?

    – ii--L--ii
    May 26 '16 at 6:40











  • This comes down to unix file permissions, your user 'root' needs the ability to write to the log files, check that you didn't create them as another user first, or that the directory itself you have the write permissions to. ls -la /usr/share/nginx . Check out, tutorialspoint.com/unix/unix-file-permission.htm If you include the output of that command it might help understanding your setup.

    – Luke Exton
    May 26 '16 at 6:52



















0














It seems 80 port is in use, just have a checked, like




sudo netstat -lnp | grep 0.0.0.0:80






share|improve this answer































    0














    You probably have a process bound to the HTTP port 80 (maybe apache2). You can run command



    sudo lsof -i:80 


    to get a list of processes using the port and then stop/disable web server.






    share|improve this answer























      Your Answer






      StackExchange.ifUsing("editor", function () {
      StackExchange.using("externalEditor", function () {
      StackExchange.using("snippets", function () {
      StackExchange.snippets.init();
      });
      });
      }, "code-snippets");

      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "1"
      };
      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%2fstackoverflow.com%2fquestions%2f37453097%2ffailed-to-start-nginx-high-performance-web-server%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Run ls -l /usr/share/nginx/ This is where it is looking to save the access logs, check the directory exists and that the user you are running nginx as has write access here.






      share|improve this answer
























      • hi Luke. Thanks for your reply. When i run the command, i have access.log and error.log file and html which is a directory. what do you mean by has write access here?

        – ii--L--ii
        May 26 '16 at 6:40











      • This comes down to unix file permissions, your user 'root' needs the ability to write to the log files, check that you didn't create them as another user first, or that the directory itself you have the write permissions to. ls -la /usr/share/nginx . Check out, tutorialspoint.com/unix/unix-file-permission.htm If you include the output of that command it might help understanding your setup.

        – Luke Exton
        May 26 '16 at 6:52
















      0














      Run ls -l /usr/share/nginx/ This is where it is looking to save the access logs, check the directory exists and that the user you are running nginx as has write access here.






      share|improve this answer
























      • hi Luke. Thanks for your reply. When i run the command, i have access.log and error.log file and html which is a directory. what do you mean by has write access here?

        – ii--L--ii
        May 26 '16 at 6:40











      • This comes down to unix file permissions, your user 'root' needs the ability to write to the log files, check that you didn't create them as another user first, or that the directory itself you have the write permissions to. ls -la /usr/share/nginx . Check out, tutorialspoint.com/unix/unix-file-permission.htm If you include the output of that command it might help understanding your setup.

        – Luke Exton
        May 26 '16 at 6:52














      0












      0








      0







      Run ls -l /usr/share/nginx/ This is where it is looking to save the access logs, check the directory exists and that the user you are running nginx as has write access here.






      share|improve this answer













      Run ls -l /usr/share/nginx/ This is where it is looking to save the access logs, check the directory exists and that the user you are running nginx as has write access here.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered May 26 '16 at 6:34









      Luke ExtonLuke Exton

      1,80221229




      1,80221229













      • hi Luke. Thanks for your reply. When i run the command, i have access.log and error.log file and html which is a directory. what do you mean by has write access here?

        – ii--L--ii
        May 26 '16 at 6:40











      • This comes down to unix file permissions, your user 'root' needs the ability to write to the log files, check that you didn't create them as another user first, or that the directory itself you have the write permissions to. ls -la /usr/share/nginx . Check out, tutorialspoint.com/unix/unix-file-permission.htm If you include the output of that command it might help understanding your setup.

        – Luke Exton
        May 26 '16 at 6:52



















      • hi Luke. Thanks for your reply. When i run the command, i have access.log and error.log file and html which is a directory. what do you mean by has write access here?

        – ii--L--ii
        May 26 '16 at 6:40











      • This comes down to unix file permissions, your user 'root' needs the ability to write to the log files, check that you didn't create them as another user first, or that the directory itself you have the write permissions to. ls -la /usr/share/nginx . Check out, tutorialspoint.com/unix/unix-file-permission.htm If you include the output of that command it might help understanding your setup.

        – Luke Exton
        May 26 '16 at 6:52

















      hi Luke. Thanks for your reply. When i run the command, i have access.log and error.log file and html which is a directory. what do you mean by has write access here?

      – ii--L--ii
      May 26 '16 at 6:40





      hi Luke. Thanks for your reply. When i run the command, i have access.log and error.log file and html which is a directory. what do you mean by has write access here?

      – ii--L--ii
      May 26 '16 at 6:40













      This comes down to unix file permissions, your user 'root' needs the ability to write to the log files, check that you didn't create them as another user first, or that the directory itself you have the write permissions to. ls -la /usr/share/nginx . Check out, tutorialspoint.com/unix/unix-file-permission.htm If you include the output of that command it might help understanding your setup.

      – Luke Exton
      May 26 '16 at 6:52





      This comes down to unix file permissions, your user 'root' needs the ability to write to the log files, check that you didn't create them as another user first, or that the directory itself you have the write permissions to. ls -la /usr/share/nginx . Check out, tutorialspoint.com/unix/unix-file-permission.htm If you include the output of that command it might help understanding your setup.

      – Luke Exton
      May 26 '16 at 6:52













      0














      It seems 80 port is in use, just have a checked, like




      sudo netstat -lnp | grep 0.0.0.0:80






      share|improve this answer




























        0














        It seems 80 port is in use, just have a checked, like




        sudo netstat -lnp | grep 0.0.0.0:80






        share|improve this answer


























          0












          0








          0







          It seems 80 port is in use, just have a checked, like




          sudo netstat -lnp | grep 0.0.0.0:80






          share|improve this answer













          It seems 80 port is in use, just have a checked, like




          sudo netstat -lnp | grep 0.0.0.0:80







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 21 '17 at 1:30









          FangnanFangnan

          11




          11























              0














              You probably have a process bound to the HTTP port 80 (maybe apache2). You can run command



              sudo lsof -i:80 


              to get a list of processes using the port and then stop/disable web server.






              share|improve this answer




























                0














                You probably have a process bound to the HTTP port 80 (maybe apache2). You can run command



                sudo lsof -i:80 


                to get a list of processes using the port and then stop/disable web server.






                share|improve this answer


























                  0












                  0








                  0







                  You probably have a process bound to the HTTP port 80 (maybe apache2). You can run command



                  sudo lsof -i:80 


                  to get a list of processes using the port and then stop/disable web server.






                  share|improve this answer













                  You probably have a process bound to the HTTP port 80 (maybe apache2). You can run command



                  sudo lsof -i:80 


                  to get a list of processes using the port and then stop/disable web server.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 27 '18 at 6:33









                  Yevgeniy AfanasyevYevgeniy Afanasyev

                  8,89155472




                  8,89155472






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Stack Overflow!


                      • 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%2fstackoverflow.com%2fquestions%2f37453097%2ffailed-to-start-nginx-high-performance-web-server%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

                      A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

                      Calculate evaluation metrics using cross_val_predict sklearn

                      Insert data from modal to MySQL (multiple modal on website)