Nginx frequently exits within docker while using supervisord












0














Following is the output for command docker run -p 9898:80 myContaineron stdout:



2019-01-03 17:23:08,600 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-03 17:23:10,109 INFO exited: nginx (exit status 1; not expected)
2019-01-03 17:23:11,115 INFO spawned: 'nginx' with pid 87
2019-01-03 17:23:12,176 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-03 17:23:13,681 INFO exited: nginx (exit status 1; not expected)
2019-01-03 17:23:14,683 INFO spawned: 'nginx' with pid 88
2019-01-03 17:23:15,710 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-03 17:23:17,214 INFO exited: nginx (exit status 1; not expected)
2019-01-03 17:23:18,218 INFO spawned: 'nginx' with pid 89
2019-01-03 17:23:19,281 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-03 17:23:20,787 INFO exited: nginx (exit status 1; not expected)
2019-01-03 17:23:21,788 INFO spawned: 'nginx' with pid 90
2019-01-03 17:23:22,840 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-03 17:23:24,344 INFO exited: nginx (exit status 1; not expected)
2019-01-03 17:23:25,346 INFO spawned: 'nginx' with pid 91
2019-01-03 17:23:26,361 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-03 17:23:27,869 INFO exited: nginx (exit status 1; not expected)


supervisord.conf:



[supervisord]
nodaemon=true

[program:nginx]
command=/usr/sbin/nginx

[program:php-fpm]
command=/usr/sbin/php-fpm -D


Dockerfile:



from centos
run yes | yum install epel-release -y
run yes | yum install nginx -y
run yes | yum install vim -y
run yes | yum install php-fpm
run yes | yum install supervisor

copy supervisord.conf /etc/supervisord.conf
copy nginx.conf /etc/nginx/nginx.conf
copy index.html /usr/share/nginx/html
copy cal.php /usr/share/nginx/html
copy 404.html /usr/share/nginx/html

CMD ["/usr/bin/supervisord"]


I am able to access web-server from host machine and php code is also being processed by the php-fpm installed therein.



I am worried about the frequent restart required for nginx by supervisord. What is it that I am doing wrong?



PS: Please ask for details before downvoting the question. I have posted after enough research on my own. This is my last resort!!!










share|improve this question







New contributor




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

























    0














    Following is the output for command docker run -p 9898:80 myContaineron stdout:



    2019-01-03 17:23:08,600 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2019-01-03 17:23:10,109 INFO exited: nginx (exit status 1; not expected)
    2019-01-03 17:23:11,115 INFO spawned: 'nginx' with pid 87
    2019-01-03 17:23:12,176 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2019-01-03 17:23:13,681 INFO exited: nginx (exit status 1; not expected)
    2019-01-03 17:23:14,683 INFO spawned: 'nginx' with pid 88
    2019-01-03 17:23:15,710 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2019-01-03 17:23:17,214 INFO exited: nginx (exit status 1; not expected)
    2019-01-03 17:23:18,218 INFO spawned: 'nginx' with pid 89
    2019-01-03 17:23:19,281 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2019-01-03 17:23:20,787 INFO exited: nginx (exit status 1; not expected)
    2019-01-03 17:23:21,788 INFO spawned: 'nginx' with pid 90
    2019-01-03 17:23:22,840 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2019-01-03 17:23:24,344 INFO exited: nginx (exit status 1; not expected)
    2019-01-03 17:23:25,346 INFO spawned: 'nginx' with pid 91
    2019-01-03 17:23:26,361 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2019-01-03 17:23:27,869 INFO exited: nginx (exit status 1; not expected)


    supervisord.conf:



    [supervisord]
    nodaemon=true

    [program:nginx]
    command=/usr/sbin/nginx

    [program:php-fpm]
    command=/usr/sbin/php-fpm -D


    Dockerfile:



    from centos
    run yes | yum install epel-release -y
    run yes | yum install nginx -y
    run yes | yum install vim -y
    run yes | yum install php-fpm
    run yes | yum install supervisor

    copy supervisord.conf /etc/supervisord.conf
    copy nginx.conf /etc/nginx/nginx.conf
    copy index.html /usr/share/nginx/html
    copy cal.php /usr/share/nginx/html
    copy 404.html /usr/share/nginx/html

    CMD ["/usr/bin/supervisord"]


    I am able to access web-server from host machine and php code is also being processed by the php-fpm installed therein.



    I am worried about the frequent restart required for nginx by supervisord. What is it that I am doing wrong?



    PS: Please ask for details before downvoting the question. I have posted after enough research on my own. This is my last resort!!!










    share|improve this question







    New contributor




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























      0












      0








      0







      Following is the output for command docker run -p 9898:80 myContaineron stdout:



      2019-01-03 17:23:08,600 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:10,109 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:11,115 INFO spawned: 'nginx' with pid 87
      2019-01-03 17:23:12,176 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:13,681 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:14,683 INFO spawned: 'nginx' with pid 88
      2019-01-03 17:23:15,710 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:17,214 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:18,218 INFO spawned: 'nginx' with pid 89
      2019-01-03 17:23:19,281 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:20,787 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:21,788 INFO spawned: 'nginx' with pid 90
      2019-01-03 17:23:22,840 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:24,344 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:25,346 INFO spawned: 'nginx' with pid 91
      2019-01-03 17:23:26,361 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:27,869 INFO exited: nginx (exit status 1; not expected)


      supervisord.conf:



      [supervisord]
      nodaemon=true

      [program:nginx]
      command=/usr/sbin/nginx

      [program:php-fpm]
      command=/usr/sbin/php-fpm -D


      Dockerfile:



      from centos
      run yes | yum install epel-release -y
      run yes | yum install nginx -y
      run yes | yum install vim -y
      run yes | yum install php-fpm
      run yes | yum install supervisor

      copy supervisord.conf /etc/supervisord.conf
      copy nginx.conf /etc/nginx/nginx.conf
      copy index.html /usr/share/nginx/html
      copy cal.php /usr/share/nginx/html
      copy 404.html /usr/share/nginx/html

      CMD ["/usr/bin/supervisord"]


      I am able to access web-server from host machine and php code is also being processed by the php-fpm installed therein.



      I am worried about the frequent restart required for nginx by supervisord. What is it that I am doing wrong?



      PS: Please ask for details before downvoting the question. I have posted after enough research on my own. This is my last resort!!!










      share|improve this question







      New contributor




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











      Following is the output for command docker run -p 9898:80 myContaineron stdout:



      2019-01-03 17:23:08,600 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:10,109 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:11,115 INFO spawned: 'nginx' with pid 87
      2019-01-03 17:23:12,176 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:13,681 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:14,683 INFO spawned: 'nginx' with pid 88
      2019-01-03 17:23:15,710 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:17,214 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:18,218 INFO spawned: 'nginx' with pid 89
      2019-01-03 17:23:19,281 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:20,787 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:21,788 INFO spawned: 'nginx' with pid 90
      2019-01-03 17:23:22,840 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:24,344 INFO exited: nginx (exit status 1; not expected)
      2019-01-03 17:23:25,346 INFO spawned: 'nginx' with pid 91
      2019-01-03 17:23:26,361 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
      2019-01-03 17:23:27,869 INFO exited: nginx (exit status 1; not expected)


      supervisord.conf:



      [supervisord]
      nodaemon=true

      [program:nginx]
      command=/usr/sbin/nginx

      [program:php-fpm]
      command=/usr/sbin/php-fpm -D


      Dockerfile:



      from centos
      run yes | yum install epel-release -y
      run yes | yum install nginx -y
      run yes | yum install vim -y
      run yes | yum install php-fpm
      run yes | yum install supervisor

      copy supervisord.conf /etc/supervisord.conf
      copy nginx.conf /etc/nginx/nginx.conf
      copy index.html /usr/share/nginx/html
      copy cal.php /usr/share/nginx/html
      copy 404.html /usr/share/nginx/html

      CMD ["/usr/bin/supervisord"]


      I am able to access web-server from host machine and php code is also being processed by the php-fpm installed therein.



      I am worried about the frequent restart required for nginx by supervisord. What is it that I am doing wrong?



      PS: Please ask for details before downvoting the question. I have posted after enough research on my own. This is my last resort!!!







      php docker nginx supervisord






      share|improve this question







      New contributor




      juggernaut108 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




      juggernaut108 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






      New contributor




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









      asked 2 days ago









      juggernaut108

      1




      1




      New contributor




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





      New contributor





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






      juggernaut108 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


















          0














          It looks like nginx is immediately exiting. That could be from a configuration file error, permission problem, etc, and the best way to find out is to run it by hand inside the container to make sure it starts and remains running. Given that this is nginx, at least one issue is that you are not starting it in the foreground. The standard way nginx is run in other containers is with:



          nginx -g "daemon off;"


          You can see this in the Dockerfile used to build nginx.






          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
            });


            }
            });






            juggernaut108 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%2fsuperuser.com%2fquestions%2f1390252%2fnginx-frequently-exits-within-docker-while-using-supervisord%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            It looks like nginx is immediately exiting. That could be from a configuration file error, permission problem, etc, and the best way to find out is to run it by hand inside the container to make sure it starts and remains running. Given that this is nginx, at least one issue is that you are not starting it in the foreground. The standard way nginx is run in other containers is with:



            nginx -g "daemon off;"


            You can see this in the Dockerfile used to build nginx.






            share|improve this answer


























              0














              It looks like nginx is immediately exiting. That could be from a configuration file error, permission problem, etc, and the best way to find out is to run it by hand inside the container to make sure it starts and remains running. Given that this is nginx, at least one issue is that you are not starting it in the foreground. The standard way nginx is run in other containers is with:



              nginx -g "daemon off;"


              You can see this in the Dockerfile used to build nginx.






              share|improve this answer
























                0












                0








                0






                It looks like nginx is immediately exiting. That could be from a configuration file error, permission problem, etc, and the best way to find out is to run it by hand inside the container to make sure it starts and remains running. Given that this is nginx, at least one issue is that you are not starting it in the foreground. The standard way nginx is run in other containers is with:



                nginx -g "daemon off;"


                You can see this in the Dockerfile used to build nginx.






                share|improve this answer












                It looks like nginx is immediately exiting. That could be from a configuration file error, permission problem, etc, and the best way to find out is to run it by hand inside the container to make sure it starts and remains running. Given that this is nginx, at least one issue is that you are not starting it in the foreground. The standard way nginx is run in other containers is with:



                nginx -g "daemon off;"


                You can see this in the Dockerfile used to build nginx.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered yesterday









                BMitch

                1385




                1385






















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










                    draft saved

                    draft discarded


















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













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












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
















                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f1390252%2fnginx-frequently-exits-within-docker-while-using-supervisord%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

                    How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                    is 'sed' thread safe

                    How to make a Squid Proxy server?