SSH screen dies every now and then












1















I am trying to run node.js app. Every now and then I find that my app is not running & I have no idea why. I have used nodemon, forever, nohup. When I set screen, find few days later that my app is again down, I login into SSH and see that screen is dead.
When starting my app with forever I see warning saying I have not set --minUptime, --spinSleepTime and default 10000ms is used. Does that mean when my host server fails to reply in 10 seconds, my "forever" is getting terminated?



Edit: As It is my first project to host it like this, I am not sure what info to share and where to get it, as far as I know I am hosting my server at a2hosting.com, with server that has 2x2.1 ghz CPU and 3gb RAM.










share|improve this question









New contributor




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





















  • No. Spinning is when an app won't start and forever keeps trying to restart it in an endless loop. If it dies in less than 10 seconds forever will sleep a while before trying again. If it dies in more than 10 seconds forever will immediately restart it.

    – couling
    Jan 9 at 11:04











  • These type of failures are very difficult to diagnose. Generally you try to ensure adequate logging to a file not to screen. Could you edit into your question more information about the server you are running this on? There are some issues you can face with virtual machines where processes are killed due to memory or even CPU constraints.

    – couling
    Jan 9 at 11:06


















1















I am trying to run node.js app. Every now and then I find that my app is not running & I have no idea why. I have used nodemon, forever, nohup. When I set screen, find few days later that my app is again down, I login into SSH and see that screen is dead.
When starting my app with forever I see warning saying I have not set --minUptime, --spinSleepTime and default 10000ms is used. Does that mean when my host server fails to reply in 10 seconds, my "forever" is getting terminated?



Edit: As It is my first project to host it like this, I am not sure what info to share and where to get it, as far as I know I am hosting my server at a2hosting.com, with server that has 2x2.1 ghz CPU and 3gb RAM.










share|improve this question









New contributor




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





















  • No. Spinning is when an app won't start and forever keeps trying to restart it in an endless loop. If it dies in less than 10 seconds forever will sleep a while before trying again. If it dies in more than 10 seconds forever will immediately restart it.

    – couling
    Jan 9 at 11:04











  • These type of failures are very difficult to diagnose. Generally you try to ensure adequate logging to a file not to screen. Could you edit into your question more information about the server you are running this on? There are some issues you can face with virtual machines where processes are killed due to memory or even CPU constraints.

    – couling
    Jan 9 at 11:06
















1












1








1








I am trying to run node.js app. Every now and then I find that my app is not running & I have no idea why. I have used nodemon, forever, nohup. When I set screen, find few days later that my app is again down, I login into SSH and see that screen is dead.
When starting my app with forever I see warning saying I have not set --minUptime, --spinSleepTime and default 10000ms is used. Does that mean when my host server fails to reply in 10 seconds, my "forever" is getting terminated?



Edit: As It is my first project to host it like this, I am not sure what info to share and where to get it, as far as I know I am hosting my server at a2hosting.com, with server that has 2x2.1 ghz CPU and 3gb RAM.










share|improve this question









New contributor




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












I am trying to run node.js app. Every now and then I find that my app is not running & I have no idea why. I have used nodemon, forever, nohup. When I set screen, find few days later that my app is again down, I login into SSH and see that screen is dead.
When starting my app with forever I see warning saying I have not set --minUptime, --spinSleepTime and default 10000ms is used. Does that mean when my host server fails to reply in 10 seconds, my "forever" is getting terminated?



Edit: As It is my first project to host it like this, I am not sure what info to share and where to get it, as far as I know I am hosting my server at a2hosting.com, with server that has 2x2.1 ghz CPU and 3gb RAM.







ssh






share|improve this question









New contributor




user1203497 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




user1203497 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 Jan 9 at 11:32







user1203497













New contributor




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









asked Jan 9 at 10:56









user1203497user1203497

62




62




New contributor




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





New contributor





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






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













  • No. Spinning is when an app won't start and forever keeps trying to restart it in an endless loop. If it dies in less than 10 seconds forever will sleep a while before trying again. If it dies in more than 10 seconds forever will immediately restart it.

    – couling
    Jan 9 at 11:04











  • These type of failures are very difficult to diagnose. Generally you try to ensure adequate logging to a file not to screen. Could you edit into your question more information about the server you are running this on? There are some issues you can face with virtual machines where processes are killed due to memory or even CPU constraints.

    – couling
    Jan 9 at 11:06





















  • No. Spinning is when an app won't start and forever keeps trying to restart it in an endless loop. If it dies in less than 10 seconds forever will sleep a while before trying again. If it dies in more than 10 seconds forever will immediately restart it.

    – couling
    Jan 9 at 11:04











  • These type of failures are very difficult to diagnose. Generally you try to ensure adequate logging to a file not to screen. Could you edit into your question more information about the server you are running this on? There are some issues you can face with virtual machines where processes are killed due to memory or even CPU constraints.

    – couling
    Jan 9 at 11:06



















No. Spinning is when an app won't start and forever keeps trying to restart it in an endless loop. If it dies in less than 10 seconds forever will sleep a while before trying again. If it dies in more than 10 seconds forever will immediately restart it.

– couling
Jan 9 at 11:04





No. Spinning is when an app won't start and forever keeps trying to restart it in an endless loop. If it dies in less than 10 seconds forever will sleep a while before trying again. If it dies in more than 10 seconds forever will immediately restart it.

– couling
Jan 9 at 11:04













These type of failures are very difficult to diagnose. Generally you try to ensure adequate logging to a file not to screen. Could you edit into your question more information about the server you are running this on? There are some issues you can face with virtual machines where processes are killed due to memory or even CPU constraints.

– couling
Jan 9 at 11:06







These type of failures are very difficult to diagnose. Generally you try to ensure adequate logging to a file not to screen. Could you edit into your question more information about the server you are running this on? There are some issues you can face with virtual machines where processes are killed due to memory or even CPU constraints.

– couling
Jan 9 at 11:06












1 Answer
1






active

oldest

votes


















0














This is maybe a long shot.. Personally I have had problems in the past with other applications running in screen in case the application has been outputting data but the client connection has become blocked due to e.g. network problems. By default this blocks the application as well, which may trigger anomalous behaviour in the application. To stop a blocked client connection from affecting the application you can add this line to ~/.screenrc:



defnonblock on


You will need to restart screen for this to take effect. Hope it helps!






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',
    autoActivateHeartbeat: false,
    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
    });


    }
    });






    user1203497 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%2f493434%2fssh-screen-dies-every-now-and-then%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














    This is maybe a long shot.. Personally I have had problems in the past with other applications running in screen in case the application has been outputting data but the client connection has become blocked due to e.g. network problems. By default this blocks the application as well, which may trigger anomalous behaviour in the application. To stop a blocked client connection from affecting the application you can add this line to ~/.screenrc:



    defnonblock on


    You will need to restart screen for this to take effect. Hope it helps!






    share|improve this answer




























      0














      This is maybe a long shot.. Personally I have had problems in the past with other applications running in screen in case the application has been outputting data but the client connection has become blocked due to e.g. network problems. By default this blocks the application as well, which may trigger anomalous behaviour in the application. To stop a blocked client connection from affecting the application you can add this line to ~/.screenrc:



      defnonblock on


      You will need to restart screen for this to take effect. Hope it helps!






      share|improve this answer


























        0












        0








        0







        This is maybe a long shot.. Personally I have had problems in the past with other applications running in screen in case the application has been outputting data but the client connection has become blocked due to e.g. network problems. By default this blocks the application as well, which may trigger anomalous behaviour in the application. To stop a blocked client connection from affecting the application you can add this line to ~/.screenrc:



        defnonblock on


        You will need to restart screen for this to take effect. Hope it helps!






        share|improve this answer













        This is maybe a long shot.. Personally I have had problems in the past with other applications running in screen in case the application has been outputting data but the client connection has become blocked due to e.g. network problems. By default this blocks the application as well, which may trigger anomalous behaviour in the application. To stop a blocked client connection from affecting the application you can add this line to ~/.screenrc:



        defnonblock on


        You will need to restart screen for this to take effect. Hope it helps!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 9 at 11:45









        Jonas BerlinJonas Berlin

        43147




        43147






















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










            draft saved

            draft discarded


















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













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












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
















            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f493434%2fssh-screen-dies-every-now-and-then%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 make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            19世紀