MySQL queries spike after update

  • Resolved idearius

    (@idearius)


    1 year, 2 months ago

    Hello. We updated Ultimate Member from version 2.1.21 to 2.7.0, then 2.8.0 and finally to 2.8.1.

    Since the update we’ve been unable to keep the plugin enabled as MySQL queries go to the roof and in about 30 seconds the website becomes unresponsive (504 error), until we rename the plugin folder using sFTP.

    The required database update has not been possible either.

    Logs show the queries seem to come from 

    /wp-content/plugins/ultimate-member/includes/core/class-access.php:203

    We tried disabling/enabling plugins looking for incompatibilities but couldn’t find any. The theme used is https://mhthemes.com/themes/mh-magazine/. Everything is updated.

    We have 4000 registered users (have to delete some spammers, though) and premium hosting to stand daily the load.

    Any ideas anyone?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support yuriinalivaiko

    (@yuriinalivaiko)

    Hello @idearius

    Verify the setting “Enable the “Content Restriction” settings for post types” on wp-admin > Ultimate Member > Settings > Access > Restriction Content and the setting “Disable pre-queries for restriction content logic (advanced)” on wp-admin > Ultimate Member > Settings > Misc.

    Is the “Disable pre-queries for restriction content logic (advanced)” unchecked? Try to turn on this setting to do a test. Is there an influence on the MySQL queries spikes on your site?

    Thanks

    Thread Starter idearius

    (@idearius)

    Many thanks, @yuriinalivaiko. It is working now and we were able to make the DB upgrade from package 2.4.0 to 2.8.1!

    As per https://docs.ultimatemember.com/article/1620-restriction-content, it seems that option should not be kept enabled. Could you expand or point me to an URL on what it does?

    In case it’s related, we’re now having critical error messages when trying to update data from users (like email or password).

    Plugin Support yuriinalivaiko

    (@yuriinalivaiko)

    Hello @idearius,

    There are three ways to handle a page that is restricted:

    1. Return HTTP status 404 Not Found.
    2. Display the message instead of the page content.
    3. Redirect to another page (the Login page for example).

    These options are described in the article Individual Post and Term content restriction settings

    The second and third options (message and redirect) can work without pre-queries, but the first option (HTTP status 404) requires pre-queries.

    Returning the HTTP status 404 is a recommended way to handle restricted posts because this option can completely hide the restricted page, so everything looks like the page does not exist. But pre-queries are resource intensive and may slow the site.

    —

    Provide more details about critical error messages you have when trying to update data from users (like email or password). Share error details or attach screenshots with error messages you see. It’s better to start a new thread for this discussion because this is not related to MySQL queries spikes.

    Regards

    Plugin Support andrewshu

    (@andrewshu)

    Hi @idearius

    This thread has been inactive for a while so we’re going to go ahead and mark it Resolved.

    Please feel free to re-open this thread if any other questions come up and we’d be happy to help. ??

    Regards

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘MySQL queries spike after update’ is closed to new replies.