[Resolved] URGENT! Abnormal Increasing Size of MySQL Binlog Files, when activate WPML plugins

Hi,

I'll continue to help you with this issue.

Please share WordPress's debug log (not WPML debug information). Please check this page for instructions.

https://wpml.org/documentation/support/debugging-wpml/

To enable it, open your wp-config.php file and look for:

define('WP_DEBUG', false);

Change it to:

define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Disable display of errors and warnings
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);

After this, repeat the action that caused the problem on your site—enable WPML to trigger the increase of the MySQL binlog file. In this case, the errors will be saved to a debug.log log file inside the /wp-content/ directory. Then, please share the errors with us.

Meanwhile, I'm also consulting our second-tier supporters about this issue.

Regards,
Itamar.

Hi,

There is no need for the procedures I asked you to check. Our second-tier supporter explains the following:

Binlog files record a log of every database activity that changes data (but not simply read data). So, they record actively "doing stuff," like saving translations, for example.

It may be possible to examine the log to detect problems, but the size of the file may just reflect the amount of work being done.

It is possible to make some edits to the MySQL configuration file to limit how long binlog files are retained and to limit the size of individual binlog files (once the size is reached, the server will start a new one), which seems like they would be useful in this context, e.g.

expire_logs_days = 7
max_binlog_size = 20M

I suspect very few clients ever need to use a binlog file (to recover data losses potentially), as they would be using a backup system for that.

Please let me know if you have any further questions.

Regards,
Itamar.

Hi,

We have new versions for WPML (4.6.12) and Strings Translation (3.2.13). The latest Strings Translation version should fix deprecated notices. Please update our plugins to the latest versions and check if the problem persists. Please clear the debug.log to check for only new errors. If you don't see we have new versions, please go to hidden link and click the Check for updates button.

Please note that the preg_match() errors are not related to your initial report about the MySQL binlog file.

Regards,
Itamar.