Huge amount of session data in /var/sessions





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















The website just went down, restarted the server and within a minute it went down again.



I quickly found out the problem was that the disk quota had been exceeded and allowed memory exhausted.



This was due to hundreds of thousands if not millions of sess_* files in var/session folder.



I tried lots of ways to remove them and this is what worked:



find . -name 'sess_*' | xargs rm


My Website is now back in good condition and no errors for now but within minutes I can see there are over 500 new session files.



Is this normal?



What should I do to prevent the server going down?










share|improve this question
















bumped to the homepage by Community 7 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















    2















    The website just went down, restarted the server and within a minute it went down again.



    I quickly found out the problem was that the disk quota had been exceeded and allowed memory exhausted.



    This was due to hundreds of thousands if not millions of sess_* files in var/session folder.



    I tried lots of ways to remove them and this is what worked:



    find . -name 'sess_*' | xargs rm


    My Website is now back in good condition and no errors for now but within minutes I can see there are over 500 new session files.



    Is this normal?



    What should I do to prevent the server going down?










    share|improve this question
















    bumped to the homepage by Community 7 hours ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      2












      2








      2


      1






      The website just went down, restarted the server and within a minute it went down again.



      I quickly found out the problem was that the disk quota had been exceeded and allowed memory exhausted.



      This was due to hundreds of thousands if not millions of sess_* files in var/session folder.



      I tried lots of ways to remove them and this is what worked:



      find . -name 'sess_*' | xargs rm


      My Website is now back in good condition and no errors for now but within minutes I can see there are over 500 new session files.



      Is this normal?



      What should I do to prevent the server going down?










      share|improve this question
















      The website just went down, restarted the server and within a minute it went down again.



      I quickly found out the problem was that the disk quota had been exceeded and allowed memory exhausted.



      This was due to hundreds of thousands if not millions of sess_* files in var/session folder.



      I tried lots of ways to remove them and this is what worked:



      find . -name 'sess_*' | xargs rm


      My Website is now back in good condition and no errors for now but within minutes I can see there are over 500 new session files.



      Is this normal?



      What should I do to prevent the server going down?







      session performance customer-session php-7 hosting






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 10 '16 at 10:44









      7ochem

      5,84493768




      5,84493768










      asked Aug 10 '16 at 9:37









      Mike Tim TurnerMike Tim Turner

      564421




      564421





      bumped to the homepage by Community 7 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 7 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          It sounds to me like you might have been hit by heavy load potentially. You might not be able to effectively handle a sudden spike without some form of load balancing and auto scaling such as using AWS and multiple servers.



          However, alternatively it could just be that it grew to excessive size because nothing is cleaning up the sessions.



          I would recommend you consider switching to use Redis as a caching service for sessions. Redis comes with a build in TTL on sessions and as a consequence of this, old sessions would simply drop from the database and stop filling the hard drive with old files.



          Official Documentation:



          Magento 1: http://devdocs.magento.com/guides/m1x/ce18-ee113/using_redis.html



          Magento 2: http://devdocs.magento.com/guides/v2.0/config-guide/redis/config-redis.html



          Hope that helps.






          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "479"
            };
            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f130756%2fhuge-amount-of-session-data-in-var-sessions%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 sounds to me like you might have been hit by heavy load potentially. You might not be able to effectively handle a sudden spike without some form of load balancing and auto scaling such as using AWS and multiple servers.



            However, alternatively it could just be that it grew to excessive size because nothing is cleaning up the sessions.



            I would recommend you consider switching to use Redis as a caching service for sessions. Redis comes with a build in TTL on sessions and as a consequence of this, old sessions would simply drop from the database and stop filling the hard drive with old files.



            Official Documentation:



            Magento 1: http://devdocs.magento.com/guides/m1x/ce18-ee113/using_redis.html



            Magento 2: http://devdocs.magento.com/guides/v2.0/config-guide/redis/config-redis.html



            Hope that helps.






            share|improve this answer




























              0














              It sounds to me like you might have been hit by heavy load potentially. You might not be able to effectively handle a sudden spike without some form of load balancing and auto scaling such as using AWS and multiple servers.



              However, alternatively it could just be that it grew to excessive size because nothing is cleaning up the sessions.



              I would recommend you consider switching to use Redis as a caching service for sessions. Redis comes with a build in TTL on sessions and as a consequence of this, old sessions would simply drop from the database and stop filling the hard drive with old files.



              Official Documentation:



              Magento 1: http://devdocs.magento.com/guides/m1x/ce18-ee113/using_redis.html



              Magento 2: http://devdocs.magento.com/guides/v2.0/config-guide/redis/config-redis.html



              Hope that helps.






              share|improve this answer


























                0












                0








                0







                It sounds to me like you might have been hit by heavy load potentially. You might not be able to effectively handle a sudden spike without some form of load balancing and auto scaling such as using AWS and multiple servers.



                However, alternatively it could just be that it grew to excessive size because nothing is cleaning up the sessions.



                I would recommend you consider switching to use Redis as a caching service for sessions. Redis comes with a build in TTL on sessions and as a consequence of this, old sessions would simply drop from the database and stop filling the hard drive with old files.



                Official Documentation:



                Magento 1: http://devdocs.magento.com/guides/m1x/ce18-ee113/using_redis.html



                Magento 2: http://devdocs.magento.com/guides/v2.0/config-guide/redis/config-redis.html



                Hope that helps.






                share|improve this answer













                It sounds to me like you might have been hit by heavy load potentially. You might not be able to effectively handle a sudden spike without some form of load balancing and auto scaling such as using AWS and multiple servers.



                However, alternatively it could just be that it grew to excessive size because nothing is cleaning up the sessions.



                I would recommend you consider switching to use Redis as a caching service for sessions. Redis comes with a build in TTL on sessions and as a consequence of this, old sessions would simply drop from the database and stop filling the hard drive with old files.



                Official Documentation:



                Magento 1: http://devdocs.magento.com/guides/m1x/ce18-ee113/using_redis.html



                Magento 2: http://devdocs.magento.com/guides/v2.0/config-guide/redis/config-redis.html



                Hope that helps.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Aug 10 '16 at 10:53









                John CuthbertJohn Cuthbert

                2,261828




                2,261828






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Magento 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%2fmagento.stackexchange.com%2fquestions%2f130756%2fhuge-amount-of-session-data-in-var-sessions%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

                    What other Star Trek series did the main TNG cast show up in?

                    Berlina muro

                    Berlina aerponto