Title: Debug too big Last modified: June 17, 2019 --- # Debug too big * Resolved [keengamer](https://wordpress.org/support/users/keengamer/) * (@keengamer) * [6 years, 11 months ago](https://wordpress.org/support/topic/debug-too-big/) * This is from our backup UpDraft Plus: * A very large file was encountered: plugins/404-solution/temp/abj404_debug.txt( size: 1629.9 Mb) * Our settings of 404: * Maximum log disk usage (MB): 10 * That file is HUUUUUGE without any reasons. Viewing 5 replies - 1 through 5 (of 5 total) * Plugin Author [Aaron](https://wordpress.org/support/users/aaron13100/) * (@aaron13100) * [6 years, 11 months ago](https://wordpress.org/support/topic/debug-too-big/#post-11646834) * keengamer, I see that you’ve been having a lot of issues with this plugin. Maybe it’s time to try a different redirection plugin? There are a few out there. * The debug file is different and separate than the “Maximum log disk usage” which refers to database usage. The debug file is limited in a different way. You can delete it manually, or wait for the daily maintenance to take care of it for you. * You can also turn off debug logging in the Options which will result in the file size not growing so quickly. * You can also specifically exclude a directory from UpDraft Plus by following the directions here. [https://updraftplus.com/faqs/how-can-i-exclude-particular-filesdirectories-from-the-backup/](https://updraftplus.com/faqs/how-can-i-exclude-particular-filesdirectories-from-the-backup/) * Thread Starter [keengamer](https://wordpress.org/support/users/keengamer/) * (@keengamer) * [6 years, 11 months ago](https://wordpress.org/support/topic/debug-too-big/#post-11646855) * I know and I don’t want to be a pain in the … And if something is mostly working as it should, I would like to help you to fix everything so not just we are happy. We have spend a lot of time searching for a lot of plugins and switching to something else is not that easy for us. * Debug is turned off by the way. So it is strange that it grew so big… * Plugin Author [Aaron](https://wordpress.org/support/users/aaron13100/) * (@aaron13100) * [6 years, 11 months ago](https://wordpress.org/support/topic/debug-too-big/#post-11648307) * Have you tried [https://wordpress.org/plugins/redirection/](https://wordpress.org/plugins/redirection/)? * Please paste some or all of the contents of the debug file to [https://pastebin.com/](https://pastebin.com/) or [https://www.file.io/](https://www.file.io/) or [https://uguu.se/](https://uguu.se/) or [https://file.town/](https://file.town/). Do not post any content here. * Thread Starter [keengamer](https://wordpress.org/support/users/keengamer/) * (@keengamer) * [6 years, 11 months ago](https://wordpress.org/support/topic/debug-too-big/#post-11648370) * Well, the debug file was most probably deleted or rewritten during the last update of your plugin so now it is small. Don’t know why. * Well, we use also permalink customizer and yoast. But your solution was for us best with the offered featured. We had to check, control, fix almost 10k of posts with our website transition. * In general, it is working fine. Just this debug bug appeared recently and that redirection to scheduled article. * Thread Starter [keengamer](https://wordpress.org/support/users/keengamer/) * (@keengamer) * [6 years, 11 months ago](https://wordpress.org/support/topic/debug-too-big/#post-11691592) * Hello again, * debug options is still set off. However the file size is over 40 MB (Debug file size: 40,884,812.57 KB (40,884.81 MB).). Is it possible to disable it?? This is what I see if I click view debug file: * 2019-07-02 07:14:52 CEST (INFO): deleteOldRedirectsCron. Old captured URLs removed: 0, Old automatic redirects removed: 0, Old manual redirects removed: 0, Old log lines removed: 0, New log size: 9.27MB, Duplicate rows deleted: 1, Debug file size limited: true, Admin email notification option turned off., Permlink cache rows updated: 0, User initiated: false * Credits: 404 Solution is maintained by Aaron J. Plugin version: 2.21.1, PHP: 7.2.19-1+ubuntu16.04.1+deb.sury.org+1, WordPress: 5.2.2, MySQL: 5.5.5, WP Memory Limit: 40M, mbstring Extension: true * I can see in Temp folder that there is also abj404_debug.txt_old.txt which has 40 MB. In my opinion the debug is running all the time and is not stopped even though we do not have it enabled. And when it reaches the limit 40 MB, then it shows php errors in our logs and creates a new file…? And what is even more strange, even though the file shows 40 MB, I have stopped copying the file after 260 MB. The debug files are quite strange and should not be created at all. * Below is also our php errors log: Jul 02, 01:50:31 * Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /home/keengamer/public_html/wp-content/plugins/404-solution/includes/ Logging.php on line 110 * Jul 02, 01:50:30 * Warning: implode(): Invalid arguments passed in /home/keengamer/public_html/wp- content/plugins/404-solution/includes/Functions.php on line 72 * Jul 02, 01:49:17 * Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0 * Regards, Karel - This reply was modified 6 years, 11 months ago by [keengamer](https://wordpress.org/support/users/keengamer/). Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Debug too big’ is closed to new replies. * ![](https://ps.w.org/404-solution/assets/icon-256x256.jpg?rev=1610739) * [404 Solution](https://wordpress.org/plugins/404-solution/) * [Frequently Asked Questions](https://wordpress.org/plugins/404-solution/#faq) * [Support Threads](https://wordpress.org/support/plugin/404-solution/) * [Active Topics](https://wordpress.org/support/plugin/404-solution/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/404-solution/unresolved/) * [Reviews](https://wordpress.org/support/plugin/404-solution/reviews/) * 5 replies * 2 participants * Last reply from: [keengamer](https://wordpress.org/support/users/keengamer/) * Last activity: [6 years, 11 months ago](https://wordpress.org/support/topic/debug-too-big/#post-11691592) * Status: resolved