Runaway Debug Log

Hi,

Yes, we had checked those but the screen for enabling/disabling the debug log exists only in the network admin.

We did manage to stop the logging, unfortunately we’re not sure exactly what it was that really stopped it. We did discover what was stopping our efforts. In an earlier attempt to stop the debug logs, we defined these variables to see if they would have any effect:

define('LSCWP_LOG', false);
define('LSCWP_LOG_LEVEL', 0);

It didn’t and then we proceeded to clean up the entries in the database that had the option name “litespeed.conf.debug” set to “1”. We’re not sure why all the subsites had this value enabled but they were. This value remained set to “1” even after were uninstalled and reinstalled the plugin, which we weren’t expecting. However in multisite installs, the code reads and writes to the wp_sitemeta table as it should. So we still don’t know why in this instance toggling sitemeta on/off was having no effect either.

For reference we have an identical site and debug logging works as expected.

It’s possible there was a stuck value cached somewhere or, somehow we were reading subsite table entries but we don’t know. The actual fix was masked by our earlier attempt to disable the logging:

define('LSCWP_LOG', false);

Doesn’t actually do anything as the code in the debug function only checks for the existing of it, like this:

Line 503 in debug.2.cls.php

	public static function debug( $msg, $backtrace_limit = false ) {
		if ( ! defined( 'LSCWP_LOG' ) ) {
			return;
		}

If it sees ‘LSCWP_LOG’ it’s not going to exit. To save someone future troubleshooting headaches, might want to have it check both presence or value, so entering “define(‘LSCWP_LOG’, false);” will exit the function.