Update crashed the side

  • Resolved Konjunktion

    (@konjunktion)


    3 years, 7 months ago

    Hey there,

    after the last update the plugin crashed to whole side due to some heavy load on the sql server. the load exceeded the normal about 300 times.

    after i disabled the plugin the side works fine again.

    maybe you can have a log in to it?

    this is what my nginx error log shows with enabled plugin:
    FastCGI sent in stderr: “PHP message: PHP Warning: preg_match(): Compilation failed: quantifier does not follow a repeatable item at offset 1 in /var/www/konjunktion.info/html/wp-includes/class-wp.php on line 223

    the sql log is empty.

    greets

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    Yikes, that doesn’t sound good, and there weren’t many changes in the SQL for the latest update. Only one comes to mind, and it’s a schema modification connected to MySQL 5.7. Can you check your database version under Tools->Site Health->Info->Database and see what version of MySQL your site is running?

    It would also be helpful to know how many records are in the wp_ewwwio_images table, as I can’t imagine the schema change being intensive unless there are a LOT of records there.

    Thread Starter Konjunktion

    (@konjunktion)

    Thx for your fast reply.

    I use the MariaDB-Version 10.3.30 on my server.

    The records of wp_ewwwio_images is 32416. Is that a too large amount if images?

    Greets and thx again.

    Since deactivation of the plugin the site runs fine and fast.

    • This reply was modified 3 years, 7 months ago by Konjunktion.
    Plugin Author nosilver4u

    (@nosilver4u)

    That doesn’t seem to lineup, unless Maria 10.3 is listing 5.7 in the version string somehow, does it show “5.7” anywhere in that version info for the server?
    And I certainly wouldn’t expect 32k to be “too many” images since I’ve got over 150k on my dev site.

    What we can do to rule this out is just remove the code that I’m suspecting, so if you want to test that out, go to the common.php file of the plugin, to line 1646, where you will see this:
    $wpdb->query( "ALTER TABLE $wpdb->ewwwio_images MODIFY updated TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP" );

    Just completely remove that line, and re-activate the plugin and see what happens. If it still grinds to a halt, then we’re chasing down the wrong rabbit trail.

    Thread Starter Konjunktion

    (@konjunktion)

    Thx for your fast reply again.

    Sorry there is no additional information about the mariadb server respectively mysql 5.7

    I commented out the mentioned line. After 10 minutes I havent an increase of cpu and/or ram usage of the database server.

    greets

    Plugin Author nosilver4u

    (@nosilver4u)

    Thanks for the update, I’ll have to do more testing and see if we can definitively pin it on that line of SQL. Sounds like your site is fine now, but Let me know if anything changes!

    Thread Starter Konjunktion

    (@konjunktion)

    Until now everything seems fine.

    So I guess we could close the case.

    Thx for the outstanding fast support.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Update crashed the side’ is closed to new replies.

Tags