problem with size of debug.log file

debug.log is exactly what it sounds – it’s just a file that contains log information for debugging purposes.

You can easily delete it and without any fear.

But…

  1. Debugging should not be turned on on production site – it’s a security problem.

  2. If your debug.log file is so big, then your site has many problems. This file contains PHP notices, warnings and errors. If everything works fine, then this file is almost empty.

So the smart thing to do is:

  • download that file to your local machine,
  • delete it from server
  • check the content of that file and try to fix as much problems as you can
  • disable logging or at least make that file inaccessible.

Related Posts:

  1. Is it possible to change the log file location for WP_DEBUG_LOG?
  2. Define WP_DEBUG conditionally / for admins only / log errors (append query arg for all links?)
  3. How do I find the version of WordPress I have from the source code?
  4. Control verbosity level of WP DEBUG?
  5. How to check if debug is true and can I use it for my own code? [duplicate]
  6. Suppress deprecated notices
  7. Debugging in WordPress
  8. Debug.log file is never created?
  9. Debugging WordPress themes with Xdebug, real time html output
  10. Easy code troubleshooting in wordpress
  11. Tutorials for Unit-Testing in WordPress and for unit-test.svn.wordpress.org?
  12. Nginx – Prevent Access to Debug file [closed]
  13. How to make debug.log timestamps local time?
  14. How to debug when error_log not working as expected
  15. How can I determine what php files are being called by a given WP page?
  16. Where should I tell WordPress where error_log messages should be written?
  17. How to set up plugin project with XDebug remote debugging in PhpStorm
  18. Disable Debug Log Programmatically
  19. How to empty debug.log when file size is above xyMB?
  20. Intercepting wp_mail() to view contents
  21. Where’s The Best Place to use Register_Shutdown_Function()?
  22. Is it possible to set another language for debugging messages?
  23. Send specific users an email when posts are published
  24. Super WordPress debugging toolkit and triage procedures? [duplicate]
  25. if(!is_user_logged_in()) returns true when 404
  26. How to dump/log default values that are passed to hooks/filter functions?
  27. xdebug connects but won’t break in WordPress with vvv
  28. Using debug log in production, is that a security concern?
  29. The plugin generated xx characters of unexpected output. How to solve?
  30. debugging wordpress
  31. Enable WordPress Debug only for Admin
  32. wp-includes/comment-template.php:26 – Trying to get property of non-object
  33. PHP-FPM WordPress Debug
  34. Debugging preview not working problem
  35. Wordress debug log is not working
  36. Always keep a parameter in URL?
  37. How can I understand what is the cause of WP death (white screen)?
  38. Why does WordPress keep showing me error messages?
  39. Debug Notice: X is deprecated since version 4.5! Use Y instead
  40. Debug 500 Internal Server Error on WordPress blog
  41. “… logged-in …” seems top of my website
  42. PHP Notice – Custom Function
  43. Suddenly lots of bugs in my WP installation? [closed]
  44. Why does WP_DEBUG only work after wp_debug_mode() is called? [closed]
  45. Notice: Undefined index [closed]
  46. Notice: attribute_escape is deprecated
  47. How to disable JS? info windows from WP-FirePHP
  48. How do I acquire all the meta-information for a particular page I am on?
  49. How to find line of code causing wordpress deprecation notices
  50. Best location for a debugging script
  51. Debug Errors, site health
  52. What is debug.log.old? It seems to take up a lot of space
  53. Comment WP_DEBUG in wp-config file
  54. How can I remove text above the header? [closed]
  55. what are WP_DEBUG conditions?
  56. Best place to call xdebug helper functions?
  57. Cannot Modify Header Information – While trying logging in
  58. Running xDebug and NPM at the same time?
  59. 3,840 cronjobs with no action!
  60. Solution to White Screen of Death that does not require Web Server access?
  61. strange characters in debug file
  62. Notice on core function
  63. Step debug wp cron run – ideas how to get this working in PHPStorm with Xdebug?
  64. There is no any line related the error but it says critical error
  65. Display Custom Taxonomy Dropdown posts
  66. Correct my shortcode for displaying a category?
  67. error log is going to the wrong location, WP_DEBUG_LOG is ignored
  68. A bug happens in the Footer and the code keeps appearing
  69. debug.log is not created
  70. Error on add_submenu_page() declaration
  71. Debug info from request handler
  72. Debugging Mysterious PHP Addition
  73. WordPress seems broken when logged of
  74. Finding which functions were called
  75. Error on debug.log PHP Stric Standards and PHP notice
  76. Unable to load Posts list & Getting error 500 error
  77. Weird bug regarding the_excerpt()
  78. Debugging conundrum with a problem fixed by enabling WP_DEBUG
  79. Can’t show debug even after modifying wp-config
  80. how to error_log(wp_login_url())
  81. How do I issue a warning in a wordpress plugin?
  82. Method ‘post_title’ not found in class.
  83. How can I turn off WP_DEBUG_LOG messages coming from a specific plugin or theme?
  84. Theme parts path location dump
  85. Changes to WordPress database using phpMyAdmin not reflected on blog
  86. WP Debug set to true but still wsod
  87. How do you get the docroot directory?
  88. How to solve the fopen error?
  89. Why debug.log doesn’t work?
  90. debug notice on my WordPress site [closed]
  91. TGM plugin error in Theme Check Plugin
  92. How to check whether functions is deprecated or not?
  93. Why does my site generate .bt files?
  94. Any wordpress development tool to query its functions?
  95. WordPress not available to file using wp-env for xdebug requests
  96. when I Try to Create new Post or Page it goes Draft(I can’t post Anything)
  97. Integrating WP as a CMS with a Bug Tracker
  98. How to display SQL query that ran in WC_Order_Query?
  99. WordPress + Buddpyress – troubleshooting server overloading
  100. Stylesheet is getting removed/deregistered automatically