Title: PHP warnings blowing up debug log
Last modified: August 31, 2016

---

# PHP warnings blowing up debug log

 *  Resolved [whax](https://wordpress.org/support/users/whax/)
 * (@whax)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/php-warnings-blowing-up-debug-log/)
 * Since updating to 5.2.0 yesterday my debug log has been inundated with occurrences
   of these PHP notices (157MB of in under 24 hours):
 * [21-Jan-2016 15:09:18 America/Los_Angeles] PHP Notice: Undefined index: brute_force
   in 7/html/wp-content/plugins/better-wp-security/core/class-itsec-lockout.php 
   on line 205
 * [21-Jan-2016 15:15:31 America/Los_Angeles] PHP Notice: Undefined index: brute_force_admin_user
   in /html/wp-content/plugins/better-wp-security/core/class-itsec-lockout.php on
   line 205
 * I have tried deactivating and reactivating but the issue continues. When I did
   so I received the following warning.
 * [21-Jan-2016 15:47:56 America/Los_Angeles] PHP Warning: call_user_func_array()
   expects parameter 1 to be a valid callback, class ‘ITSEC_SSL_Setup’ does not 
   have a method ‘execute_deactivate’ in /html/wp-includes/plugin.php on line 525
 * This is a production site with a lot of traffic so I’m trying to replicate this
   on a staging site. In the mean time, does anyone have any insight into this? 
   Yesterday after seeing these notices reference “brute_force”, I disabled the 
   brute force detection but that obviously didn’t help.
 * Thank you,
    Ryan
 * [https://wordpress.org/plugins/better-wp-security/](https://wordpress.org/plugins/better-wp-security/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [dwinden](https://wordpress.org/support/users/dwinden/)
 * (@dwinden)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/php-warnings-blowing-up-debug-log/#post-6976538)
 * [@whax](https://wordpress.org/support/users/whax/)
 * Not sure what is happening with the brute force notices …
 * But the SSL related deactivation warning is a newly introduced bug in the 5.2.0
   release.
 * To fix it change the following line in the better-wp-security/core/modules/ssl/
   setup.php file:
 *     ```
       add_action( 'itsec_modules_do_plugin_deactivation', array( $this, 'execute_deactivate' )          );
       ```
   
 * into:
 *     ```
       //add_action( 'itsec_modules_do_plugin_deactivation', array( $this, 'execute_deactivate' )          );
       ```
   
 * But honestly it’s better to downgrade to the [5.1.1 release](https://downloads.wordpress.org/plugin/better-wp-security.5.1.1.zip)
   and wait for iThemes to fix all the issues introduced in the 5.2.0 release.
    
   Skip this release and wait for the next update. Can’t give you any better advice.
 * dwinden
 *  [dwinden](https://wordpress.org/support/users/dwinden/)
 * (@dwinden)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/php-warnings-blowing-up-debug-log/#post-6976576)
 * [@ryan](https://wordpress.org/support/users/ryan/)
 * To get a better understanding of the brute force notices a (Xdebug) error stacktrace
   would be helpfull.
    For more info on Xdebug visit [this](https://en.wikipedia.org/wiki/Xdebug)
   link.
 * dwinden
 *  [dwinden](https://wordpress.org/support/users/dwinden/)
 * (@dwinden)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/php-warnings-blowing-up-debug-log/#post-6976671)
 * [@ryan](https://wordpress.org/support/users/ryan/)
 * If you require no further assistance please mark this topic as ‘resolved’.
 * dwinden
 *  Thread Starter [whax](https://wordpress.org/support/users/whax/)
 * (@whax)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/php-warnings-blowing-up-debug-log/#post-6976673)
 * I’m sorry, I just turned off the debug log and haven’t had time to troubleshoot
   this further. I’ll reopen the issue when I can. Thank you for your suggestions.
 *  [dwinden](https://wordpress.org/support/users/dwinden/)
 * (@dwinden)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/php-warnings-blowing-up-debug-log/#post-6976700)
 * [@whax](https://wordpress.org/support/users/whax/)
 * Both the Brute Force PHP Notice and SSL deactivation PHP Warning are probably
   fixed in the iTSec plugin 5.2.1 update released yesterday.
 * From the 5.2.1 [Changelog](https://nl.wordpress.org/plugins/better-wp-security/changelog/):
 * >  Bug Fix: Fixed warning that could occur on a failed login when Local Brute
   > Force Detection is disabled.
   > Bug Fix: Fixed the cause of the following warning: call_user_func_array() expects
   > parameter 1 to be a valid callback, class ‘ITSEC_SSL_Setup’ does not have a
   > method ‘execute_deactivate’
 * dwinden

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘PHP warnings blowing up debug log’ is closed to new replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351)
 * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [dwinden](https://wordpress.org/support/users/dwinden/)
 * Last activity: [10 years, 3 months ago](https://wordpress.org/support/topic/php-warnings-blowing-up-debug-log/#post-6976700)
 * Status: resolved