tblmodulelog too large to work with in phpmyadmin

[discordianfarmer]

Our WHMCS tblmodulelog is over 76 GB and we do not know how to trim it to work with it properly. Is there a SQL command I can use to trim it? PHPmyadmin times out when trying to load the table.

[discordianfarmer]

I think I found my answer with 

can clear all log records from admin area, or using this SQL command:TRUNCATE `tblmodulelog`;or delete all records before March 2016DELETE FROM `tblmodulelog` WHERE `date` < '2016-03-01 00:00:00';

[discordianfarmer]

Running DELETE FROM `tblmodulelog` WHERE `date` < '2015-12-01 00:00:00' gives a total number of locks exceeds the lock table size.

[brian!]

On 26/11/2019 at 17:20, discordianfarmer said:

Our WHMCS tblmodulelog is over 76 GB

wow! 😲

On 26/11/2019 at 18:16, discordianfarmer said:

Running DELETE FROM `tblmodulelog` WHERE `date` < '2015-12-01 00:00:00' gives a total number of locks exceeds the lock table size.

short of increasing the buffer size, another option might be to go further back than 2015 so that there are fewer results to delete? e.g run the query a few times starting with dates before 2000 (or whenever), and then add a year each time until you get to 2015.

[discordianfarmer]

Truncate was the magic word. After that we were able to turn off the debugging mode that had been running for who knows how long. 

[Remitur]

It's recommended to enable module logging only for debugging purposes.

And you can enable, disable and reset it in admin area, without the needs to truncate the table in phpmyadmin... 

[Jesús Yael Ortega Aguilar]

Hey, someone can please tell me where can i disable the tblmodulelog, because i can't find this setting 😞

[WHMCS Sachin]

14 hours ago, Jesús Yael Ortega Aguilar said:

Hey, someone can please tell me where can i disable the tblmodulelog, because i can't find this setting 😞

You can disable the Module Debug Log from the Module Log page (link can be found in the sidebar on the Activity Log page in v8 and in Utilities -> Logs menu in v7).