Magento 2 - Turn on / off debug logHug size of debug.log file in Magento 2.2magento2: Enable and Disable logAll Forms Simply Reloading the PageTracking down DEBUG logged entriesMagento 2: Create custom log fileHow to roll over log files in magento 2?how to turn off conversion currencyTurn on template paths using command lineHow to disable debug.logHelp me understand what this log meansMagento 2 - Turn off Cart & Checkout off for 1 websiteHow to turn off browser auto-fill Magento2How to turn off URL rewrites for products not visible individually in Magento 2?

"It doesn't matter" or "it won't matter"?

Stack Interview Code methods made from class Node and Smart Pointers

Is it allowed to activate the ability of multiple planeswalkers in a single turn?

Taxes on Dividends in a Roth IRA

How to get directions in deep space?

What is Cash Advance APR?

A Trivial Diagnosis

Microchip documentation does not label CAN buss pins on micro controller pinout diagram

How many arrows is an archer expected to fire by the end of the Tyranny of Dragons pair of adventures?

Do we have to expect a queue for the shuttle from Watford Junction to Harry Potter Studio?

Does an advisor owe his/her student anything? Will an advisor keep a PhD student only out of pity?

What are some good ways to treat frozen vegetables such that they behave like fresh vegetables when stir frying them?

How to draw a matrix with arrows in limited space

Does the reader need to like the PoV character?

What is the difference between lands and mana?

The IT department bottlenecks progress, how should I handle this?

Does "he squandered his car on drink" sound natural?

Can you use Vicious Mockery to win an argument or gain favours?

Which Article Helped Get Rid of Technobabble in RPGs?

Which was the first story featuring espers?

What's the name of the logical fallacy where a debater extends a statement far beyond the original statement to make it true?

Were Persian-Median kings illiterate?

Why does this expression simplify as such?

Why should universal income be universal?



Magento 2 - Turn on / off debug log


Hug size of debug.log file in Magento 2.2magento2: Enable and Disable logAll Forms Simply Reloading the PageTracking down DEBUG logged entriesMagento 2: Create custom log fileHow to roll over log files in magento 2?how to turn off conversion currencyTurn on template paths using command lineHow to disable debug.logHelp me understand what this log meansMagento 2 - Turn off Cart & Checkout off for 1 websiteHow to turn off browser auto-fill Magento2How to turn off URL rewrites for products not visible individually in Magento 2?













9















How to turn off / on the var/debug.log of Magento 2? Is there a way to set the log level?










share|improve this question
























  • Duplicate: magento.stackexchange.com/questions/95327/…

    – seanbreeden
    Nov 13 '16 at 19:55











  • Hmm, I am running this: php bin/magento config:set dev/debug/debug_logging 1 and getting this error: There are no commands defined in the "config" namespace. Did you mean one of these? app:config setup:config setup:store-config I have tried running the command with each of those instead of just config and they don't work either. Any ideas? I had this working at one time. Probably before I dumped my config.

    – Patrick Steil
    yesterday











  • If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review

    – Jai
    yesterday











  • This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review

    – Shoaib Munir
    23 hours ago















9















How to turn off / on the var/debug.log of Magento 2? Is there a way to set the log level?










share|improve this question
























  • Duplicate: magento.stackexchange.com/questions/95327/…

    – seanbreeden
    Nov 13 '16 at 19:55











  • Hmm, I am running this: php bin/magento config:set dev/debug/debug_logging 1 and getting this error: There are no commands defined in the "config" namespace. Did you mean one of these? app:config setup:config setup:store-config I have tried running the command with each of those instead of just config and they don't work either. Any ideas? I had this working at one time. Probably before I dumped my config.

    – Patrick Steil
    yesterday











  • If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review

    – Jai
    yesterday











  • This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review

    – Shoaib Munir
    23 hours ago













9












9








9


2






How to turn off / on the var/debug.log of Magento 2? Is there a way to set the log level?










share|improve this question
















How to turn off / on the var/debug.log of Magento 2? Is there a way to set the log level?







magento2 log debug






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 26 '16 at 5:32









Khoa TruongDinh

21.9k64187




21.9k64187










asked Aug 26 '16 at 5:17









PaulPaul

1,81672661




1,81672661












  • Duplicate: magento.stackexchange.com/questions/95327/…

    – seanbreeden
    Nov 13 '16 at 19:55











  • Hmm, I am running this: php bin/magento config:set dev/debug/debug_logging 1 and getting this error: There are no commands defined in the "config" namespace. Did you mean one of these? app:config setup:config setup:store-config I have tried running the command with each of those instead of just config and they don't work either. Any ideas? I had this working at one time. Probably before I dumped my config.

    – Patrick Steil
    yesterday











  • If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review

    – Jai
    yesterday











  • This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review

    – Shoaib Munir
    23 hours ago

















  • Duplicate: magento.stackexchange.com/questions/95327/…

    – seanbreeden
    Nov 13 '16 at 19:55











  • Hmm, I am running this: php bin/magento config:set dev/debug/debug_logging 1 and getting this error: There are no commands defined in the "config" namespace. Did you mean one of these? app:config setup:config setup:store-config I have tried running the command with each of those instead of just config and they don't work either. Any ideas? I had this working at one time. Probably before I dumped my config.

    – Patrick Steil
    yesterday











  • If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review

    – Jai
    yesterday











  • This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review

    – Shoaib Munir
    23 hours ago
















Duplicate: magento.stackexchange.com/questions/95327/…

– seanbreeden
Nov 13 '16 at 19:55





Duplicate: magento.stackexchange.com/questions/95327/…

– seanbreeden
Nov 13 '16 at 19:55













Hmm, I am running this: php bin/magento config:set dev/debug/debug_logging 1 and getting this error: There are no commands defined in the "config" namespace. Did you mean one of these? app:config setup:config setup:store-config I have tried running the command with each of those instead of just config and they don't work either. Any ideas? I had this working at one time. Probably before I dumped my config.

– Patrick Steil
yesterday





Hmm, I am running this: php bin/magento config:set dev/debug/debug_logging 1 and getting this error: There are no commands defined in the "config" namespace. Did you mean one of these? app:config setup:config setup:store-config I have tried running the command with each of those instead of just config and they don't work either. Any ideas? I had this working at one time. Probably before I dumped my config.

– Patrick Steil
yesterday













If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review

– Jai
yesterday





If you have a new question, please ask it by clicking the Ask Question button. Include a link to this question if it helps provide context. - From Review

– Jai
yesterday













This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review

– Shoaib Munir
23 hours ago





This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. - From Review

– Shoaib Munir
23 hours ago










2 Answers
2






active

oldest

votes


















19














Enabling the debug log on Magento 2.2 and above



In Magento 2.2 and above, debugging can be enabled from either the GUI admin panel or from the command line.



First, check which mode your site is in by opening your Magento application directory (the one with index.php) in the shell. Then enter:



php bin/magento deploy:mode:show



If it says "production", only the command line method will work. Otherwise, the GUI method will work too.



GUI method



In the Magento admin panel, go to "Stores" -> "Configuration" -> "Advanced" -> "Developer" -> "Debug" -> "Log to File". Setting this to "Yes" will cause debug information to be logged to var/log/debug.log in your Magento application directory.



The log to File option in the control panel.



After saving the setting, you may get a prompt at the top of the page asking you to flush the cache. If this appears, flush the Magento cache with the link it gives you.



If production mode is enabled (as displayed by php bin/magento deploy:mode:show) then the GUI option will not be available. Note that this the admin panel normally hides this in production mode, so only use this if you're testing.



Command line method



First, open the Magento application directory (the one with index.php) in the shell. To enable debug logging enter:



php bin/magento config:set dev/debug/debug_logging 1 && php bin/magento cache:flush



This will cause debug information to be logged to var/log/debug.log in your Magento application directory. To disable debug logging, enter:



php bin/magento config:set dev/debug/debug_logging 0 && php bin/magento cache:flush






share|improve this answer






























    0














    The value you set has already been locked. To change the value, use the --lock option.






    share|improve this answer























    • if you get the above message after running @Michael Casey answer, add --lock as in the following command php bin/magento config:set --lock dev/debug/debug_logging 1 && php bin/magento cache:flush

      – bhaskarc
      Dec 7 '18 at 12:33










    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%2f133156%2fmagento-2-turn-on-off-debug-log%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    19














    Enabling the debug log on Magento 2.2 and above



    In Magento 2.2 and above, debugging can be enabled from either the GUI admin panel or from the command line.



    First, check which mode your site is in by opening your Magento application directory (the one with index.php) in the shell. Then enter:



    php bin/magento deploy:mode:show



    If it says "production", only the command line method will work. Otherwise, the GUI method will work too.



    GUI method



    In the Magento admin panel, go to "Stores" -> "Configuration" -> "Advanced" -> "Developer" -> "Debug" -> "Log to File". Setting this to "Yes" will cause debug information to be logged to var/log/debug.log in your Magento application directory.



    The log to File option in the control panel.



    After saving the setting, you may get a prompt at the top of the page asking you to flush the cache. If this appears, flush the Magento cache with the link it gives you.



    If production mode is enabled (as displayed by php bin/magento deploy:mode:show) then the GUI option will not be available. Note that this the admin panel normally hides this in production mode, so only use this if you're testing.



    Command line method



    First, open the Magento application directory (the one with index.php) in the shell. To enable debug logging enter:



    php bin/magento config:set dev/debug/debug_logging 1 && php bin/magento cache:flush



    This will cause debug information to be logged to var/log/debug.log in your Magento application directory. To disable debug logging, enter:



    php bin/magento config:set dev/debug/debug_logging 0 && php bin/magento cache:flush






    share|improve this answer



























      19














      Enabling the debug log on Magento 2.2 and above



      In Magento 2.2 and above, debugging can be enabled from either the GUI admin panel or from the command line.



      First, check which mode your site is in by opening your Magento application directory (the one with index.php) in the shell. Then enter:



      php bin/magento deploy:mode:show



      If it says "production", only the command line method will work. Otherwise, the GUI method will work too.



      GUI method



      In the Magento admin panel, go to "Stores" -> "Configuration" -> "Advanced" -> "Developer" -> "Debug" -> "Log to File". Setting this to "Yes" will cause debug information to be logged to var/log/debug.log in your Magento application directory.



      The log to File option in the control panel.



      After saving the setting, you may get a prompt at the top of the page asking you to flush the cache. If this appears, flush the Magento cache with the link it gives you.



      If production mode is enabled (as displayed by php bin/magento deploy:mode:show) then the GUI option will not be available. Note that this the admin panel normally hides this in production mode, so only use this if you're testing.



      Command line method



      First, open the Magento application directory (the one with index.php) in the shell. To enable debug logging enter:



      php bin/magento config:set dev/debug/debug_logging 1 && php bin/magento cache:flush



      This will cause debug information to be logged to var/log/debug.log in your Magento application directory. To disable debug logging, enter:



      php bin/magento config:set dev/debug/debug_logging 0 && php bin/magento cache:flush






      share|improve this answer

























        19












        19








        19







        Enabling the debug log on Magento 2.2 and above



        In Magento 2.2 and above, debugging can be enabled from either the GUI admin panel or from the command line.



        First, check which mode your site is in by opening your Magento application directory (the one with index.php) in the shell. Then enter:



        php bin/magento deploy:mode:show



        If it says "production", only the command line method will work. Otherwise, the GUI method will work too.



        GUI method



        In the Magento admin panel, go to "Stores" -> "Configuration" -> "Advanced" -> "Developer" -> "Debug" -> "Log to File". Setting this to "Yes" will cause debug information to be logged to var/log/debug.log in your Magento application directory.



        The log to File option in the control panel.



        After saving the setting, you may get a prompt at the top of the page asking you to flush the cache. If this appears, flush the Magento cache with the link it gives you.



        If production mode is enabled (as displayed by php bin/magento deploy:mode:show) then the GUI option will not be available. Note that this the admin panel normally hides this in production mode, so only use this if you're testing.



        Command line method



        First, open the Magento application directory (the one with index.php) in the shell. To enable debug logging enter:



        php bin/magento config:set dev/debug/debug_logging 1 && php bin/magento cache:flush



        This will cause debug information to be logged to var/log/debug.log in your Magento application directory. To disable debug logging, enter:



        php bin/magento config:set dev/debug/debug_logging 0 && php bin/magento cache:flush






        share|improve this answer













        Enabling the debug log on Magento 2.2 and above



        In Magento 2.2 and above, debugging can be enabled from either the GUI admin panel or from the command line.



        First, check which mode your site is in by opening your Magento application directory (the one with index.php) in the shell. Then enter:



        php bin/magento deploy:mode:show



        If it says "production", only the command line method will work. Otherwise, the GUI method will work too.



        GUI method



        In the Magento admin panel, go to "Stores" -> "Configuration" -> "Advanced" -> "Developer" -> "Debug" -> "Log to File". Setting this to "Yes" will cause debug information to be logged to var/log/debug.log in your Magento application directory.



        The log to File option in the control panel.



        After saving the setting, you may get a prompt at the top of the page asking you to flush the cache. If this appears, flush the Magento cache with the link it gives you.



        If production mode is enabled (as displayed by php bin/magento deploy:mode:show) then the GUI option will not be available. Note that this the admin panel normally hides this in production mode, so only use this if you're testing.



        Command line method



        First, open the Magento application directory (the one with index.php) in the shell. To enable debug logging enter:



        php bin/magento config:set dev/debug/debug_logging 1 && php bin/magento cache:flush



        This will cause debug information to be logged to var/log/debug.log in your Magento application directory. To disable debug logging, enter:



        php bin/magento config:set dev/debug/debug_logging 0 && php bin/magento cache:flush







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 3 '18 at 20:46









        Michael CaseyMichael Casey

        19113




        19113























            0














            The value you set has already been locked. To change the value, use the --lock option.






            share|improve this answer























            • if you get the above message after running @Michael Casey answer, add --lock as in the following command php bin/magento config:set --lock dev/debug/debug_logging 1 && php bin/magento cache:flush

              – bhaskarc
              Dec 7 '18 at 12:33















            0














            The value you set has already been locked. To change the value, use the --lock option.






            share|improve this answer























            • if you get the above message after running @Michael Casey answer, add --lock as in the following command php bin/magento config:set --lock dev/debug/debug_logging 1 && php bin/magento cache:flush

              – bhaskarc
              Dec 7 '18 at 12:33













            0












            0








            0







            The value you set has already been locked. To change the value, use the --lock option.






            share|improve this answer













            The value you set has already been locked. To change the value, use the --lock option.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 28 '18 at 19:53









            Davi BackendorfDavi Backendorf

            1




            1












            • if you get the above message after running @Michael Casey answer, add --lock as in the following command php bin/magento config:set --lock dev/debug/debug_logging 1 && php bin/magento cache:flush

              – bhaskarc
              Dec 7 '18 at 12:33

















            • if you get the above message after running @Michael Casey answer, add --lock as in the following command php bin/magento config:set --lock dev/debug/debug_logging 1 && php bin/magento cache:flush

              – bhaskarc
              Dec 7 '18 at 12:33
















            if you get the above message after running @Michael Casey answer, add --lock as in the following command php bin/magento config:set --lock dev/debug/debug_logging 1 && php bin/magento cache:flush

            – bhaskarc
            Dec 7 '18 at 12:33





            if you get the above message after running @Michael Casey answer, add --lock as in the following command php bin/magento config:set --lock dev/debug/debug_logging 1 && php bin/magento cache:flush

            – bhaskarc
            Dec 7 '18 at 12:33

















            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%2f133156%2fmagento-2-turn-on-off-debug-log%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

            Sum ergo cogito? 1 nng

            三茅街道4182Guuntc Dn precexpngmageondP