Spiked DB Activity on v3.4.3

  • Resolved rpatton16

    (@rpatton16)


    6 months ago

    Hello,
    We recently upgraded Inactive Logout from v3.3.4 to v3.4.3. A few hours after doing so our daily traffic begin to build up and we noticed that the site performance began to degrade, then began throwing the error, “Error establishing database connection”. Additionally the server and WP monitoring began reporting issues with the InactiveLogout plugin:
    An error of type E_ERROR was caused in line 161 of the file [root]/[site]/wp-content/plugins/inactive-logout-addon/includes/Base.php. Error message: Uncaught Error: Undefined constant “Codemanas\InactiveLogoutAddon\INACTIVE_LOGOUT_VERSION” in [root]/[site]/wp-content/plugins/inactive-logout-addon/includes/Base.php:161
    Stack trace:
    #0 [root]/[site]/wp-content/plugins/inactive-logout-addon/includes/Base.php(89): Codemanas\InactiveLogoutAddon\Base->checkDependencies()
    #1 [root]/[site]/wp-includes/class-wp-hook.php(324): Codemanas\InactiveLogoutAddon\Base->loaded()
    #2 [root]/[site]/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #3 [root]/[site]/wp-includes/plugin.php(517): WP_Hook->do_action()
    #4 [root]/[site]/wp-settings.php(555): do_action()
    #5 [root]/[site]/wp-config.php(116): require_once(‘…/html/m…’)
    #6 [root]/[site]/wp-load.php(50): require_once(‘…/html/m…’)
    #7 [root]/[site]/wp-admin/admin-ajax.php(22): require_once(‘…/html/m…’)
    #8 {main}
    thrown

    When checking the database server we noticed multiple queries to the ‘wp_ina_user_log’ table that had very high latency. Immediately after we reverted the “/inactive-logout/” folder and contents from our v3.3.4 backup, into the plugins directory, everything was back to normal. The database queries cleared up, the latency on all queries dropped, and slowness and errors on the website went away. We are running Oracle Linux 8, MariaDB.
    We also have Inactive Logout Pro installed running v2.10.1 (latest), although this seemed to be more of a “Inactive Logout” issue versus a “Inactive Logout Pro” issue based on when and how the site responded after the rollback.
    Is this a known problem?
    I see there is a v3.4.4 update however the change log doesn’t appear to include anything related to this issue.
    Thanks in advance for any help you can provide,
    -Rob

    • This topic was modified 6 months ago by rpatton16.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Deepen

    (@j_3rk)

    Hi Rob,

    Thanks for reporting this.

    Judging by the stack trace, this is probably linked with pro version of inactive logout not being supportive with free version. I’ve tried to replicate but was not successful.

    Can you please reach out to [email protected] in this case to escalate this? Pro version support is not allowed in WordPress forums.

    Thread Starter rpatton16

    (@rpatton16)

    Sounds good, will do.
    Thanks, -Rob

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Spiked DB Activity on v3.4.3’ is closed to new replies.