Flask error logging file not updating on VPS












0















I am following this tutorial on Digitalocean to set up my web application. https://www.digitalocean.com/community/tutorials/how-to-serve-flask-applications-with-gunicorn-and-nginx-on-ubuntu-16-04



I can run my code on my local machine and get the detailed traceback error messages from the error log, i.e., "flask.log", but this file is not updating on the virtual private server I am using (Ubuntu-16-04). How can I get Flask's traceback error messages from my VPS?



The python environment I am using is Anaconda. And the following is the code I am using to create the error log file. Debug mode is false.



from flask import Flask
import logging

app = Flask(__name__)
app.config.from_object('project.settings')

filehandler = logging.FileHandler('flask.log')
filehandler.setLevel(logging.ERROR)
app.logger.setLevel(logging.ERROR)
app.logger.addHandler(filehandler)









share|improve this question



























    0















    I am following this tutorial on Digitalocean to set up my web application. https://www.digitalocean.com/community/tutorials/how-to-serve-flask-applications-with-gunicorn-and-nginx-on-ubuntu-16-04



    I can run my code on my local machine and get the detailed traceback error messages from the error log, i.e., "flask.log", but this file is not updating on the virtual private server I am using (Ubuntu-16-04). How can I get Flask's traceback error messages from my VPS?



    The python environment I am using is Anaconda. And the following is the code I am using to create the error log file. Debug mode is false.



    from flask import Flask
    import logging

    app = Flask(__name__)
    app.config.from_object('project.settings')

    filehandler = logging.FileHandler('flask.log')
    filehandler.setLevel(logging.ERROR)
    app.logger.setLevel(logging.ERROR)
    app.logger.addHandler(filehandler)









    share|improve this question

























      0












      0








      0








      I am following this tutorial on Digitalocean to set up my web application. https://www.digitalocean.com/community/tutorials/how-to-serve-flask-applications-with-gunicorn-and-nginx-on-ubuntu-16-04



      I can run my code on my local machine and get the detailed traceback error messages from the error log, i.e., "flask.log", but this file is not updating on the virtual private server I am using (Ubuntu-16-04). How can I get Flask's traceback error messages from my VPS?



      The python environment I am using is Anaconda. And the following is the code I am using to create the error log file. Debug mode is false.



      from flask import Flask
      import logging

      app = Flask(__name__)
      app.config.from_object('project.settings')

      filehandler = logging.FileHandler('flask.log')
      filehandler.setLevel(logging.ERROR)
      app.logger.setLevel(logging.ERROR)
      app.logger.addHandler(filehandler)









      share|improve this question














      I am following this tutorial on Digitalocean to set up my web application. https://www.digitalocean.com/community/tutorials/how-to-serve-flask-applications-with-gunicorn-and-nginx-on-ubuntu-16-04



      I can run my code on my local machine and get the detailed traceback error messages from the error log, i.e., "flask.log", but this file is not updating on the virtual private server I am using (Ubuntu-16-04). How can I get Flask's traceback error messages from my VPS?



      The python environment I am using is Anaconda. And the following is the code I am using to create the error log file. Debug mode is false.



      from flask import Flask
      import logging

      app = Flask(__name__)
      app.config.from_object('project.settings')

      filehandler = logging.FileHandler('flask.log')
      filehandler.setLevel(logging.ERROR)
      app.logger.setLevel(logging.ERROR)
      app.logger.addHandler(filehandler)






      python logging flask digital-ocean vps






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 5:39









      renjie gerenjie ge

      65




      65
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Turns out that the program was killed before the logging file got the chance to update because the system is out of memory. I upgraded the VPS and the issue is resolved.






          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%2f53405852%2fflask-error-logging-file-not-updating-on-vps%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














            Turns out that the program was killed before the logging file got the chance to update because the system is out of memory. I upgraded the VPS and the issue is resolved.






            share|improve this answer




























              0














              Turns out that the program was killed before the logging file got the chance to update because the system is out of memory. I upgraded the VPS and the issue is resolved.






              share|improve this answer


























                0












                0








                0







                Turns out that the program was killed before the logging file got the chance to update because the system is out of memory. I upgraded the VPS and the issue is resolved.






                share|improve this answer













                Turns out that the program was killed before the logging file got the chance to update because the system is out of memory. I upgraded the VPS and the issue is resolved.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 27 '18 at 4:34









                renjie gerenjie ge

                65




                65
































                    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%2f53405852%2fflask-error-logging-file-not-updating-on-vps%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

                    Guess what letter conforming each word

                    Port of Spain

                    Run scheduled task as local user group (not BUILTIN)