Databank-Server crashed after Udpdate to Version 13.0.6

Well I saw the extreme db usage issue on a downgrade from 13 for testing.

• This reply was modified 3 years, 9 months ago by programmin.

downgrade? Means you have testes the Plugin with lower versions then 13 and the DB crashed?

I have a theory, maybe @veronalabs can say something about it:

In Version 13.xxx there are more connections to the Posts and Pages i have made so far. There is another Field showing up directly under each Post / Page in the Admin section which shows statistics as well (should show i would say). I have thousands of Postings created (newswebsite) and all this postings get a “configuration” from the Plug in at the same time. Maybe this destoys the Database? Please let me know what else i can try. Because as soon i update to a Version over 13 my website crashed because of to many database conecctions….

Thanks in advance!

Hi

Thank you for explaining and I’m sorry about the problem.

In this case, that would be great if you give me one of the queries that had the error, or any error on the error log file, I mean something that can help us to debug and fix it.

Because there is some ALTER table query in the plugin to upgrade and not sure which one is breaking your website.

Best

Hi @mostafas1990,

thanks for getting back. Basically i don’t have any error logs anymore as this is to long ago.

I guess that the “new Functions” you have implemented into the plug in (statistics etc in each post) creates this problems. My Website is big i have more then 6.500 Posts on the page and if a plug in is running into all the plug posts in the same tme the database server crashes because this is a huge amount of connections at the same time.

I have found only some older entries:

[Mon Feb 15 06:17:17.216368 2021] [proxy_fcgi:error] [pid 275689] [client xxx] AH01071: Got error 'PHP message: WordPress-Datenbank-Fehler You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 1 f\xc3\xbcr Abfrage SELECTpage_idFROM wp_statistics_pages WHEREdate= '2021-02-15' ANDtype= '' ANDid= von require('wp-blog-header.php'), wp, WP->main, WP->parse_request, do_action_ref_array('parse_request'), WP_Hook->do_action, WP_Hook->apply_filters, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, WP_REST_Server->respond_to_request, WP_Statistics_Rest->hit, WP_Statistics_Hits->Pages'

Maybe thet helps, but i guess not…

Hello @mostafas1990

Today i see another Update to Version 13.0.7. Actually i have fear to try it because of another pssoible horrible day with database crash.

I see thet there is an fix for “Fixes linking hits page from post meta box” what actually is this doing? This thing is inserting additional data into every post and page, right? Would it not be better to stop this kind of automatic things, because bigger websites will have a lot of trouble with it…

Ah @mostafas1990 i found another Error Log from an old Post frm my Website:

Fehler-Details
==============
Ein Fehler vom Typ E_ERROR wurde in der Zeile 78 der Datei /var/www/vhosts/PAGE/httpdocs/wp-content/plugins/wp-statistics/includes/classes/class-wp-statistics-welcome.php verursacht. Fehlermeldung: Uncaught Error: Class 'WP_Statistics_Updates' not found in /var/www/vhosts/PAGE/httpdocs/wp-content/plugins/wp-statistics/includes/classes/class-wp-statistics-welcome.php:78
Stack trace:
#0 /var/www/vhosts/PAGE/httpdocs/wp-includes/class-wp-hook.php(287): WP_Statistics_Welcome::do_welcome()
#1 /var/www/vhosts/PAGE/httpdocs/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#2 /var/www/vhosts/PAGE/httpdocs/wp-includes/plugin.php(484): WP_Hook->do_action()
#3 /var/www/vhosts/PAGE/httpdocs/wp-admin/includes/class-plugin-upgrader.php(371): do_action()
#4 /var/www/vhosts/PAGE/httpdocs/wp-admin/update.php(51): Plugin_Upgrader->bulk_upgrade()
#5 {main}
 thrown

Maybe that helps?

@veronalabs & @mostafas1990 any feedback on this?

Ah @mostafas1990 i found another Error Log from an old Post frm my Website:

This is not related to the new version, which occurred once while updating from v12 to greater than.

Also, the new version could not fix your problem because there is an SQL query problem.

Is it possible to upgrade the plugin manually and then going to the setting page to disable Track all page and pages as well?

Then we can continue with the issue.

Hi @mostafas1990 well is this “disable Track all page and pages” realted to this: I see thet there is an fix for “Fixes linking hits page from post meta box” what actually is this doing? This thing is inserting additional data into every post and page, right? Would it not be better to stop this kind of automatic things, because bigger websites will have a lot of trouble with it…

??

SQL query Problem means exactly what?

Manually Updating is a possibility i have, but i’m still in fear to destroy my website again…

This thing is inserting additional data into every post and page, right?

No, the improvement is related to the SELECT query and is not the INSERT query.

Would it not be better to stop this kind of automatic things, because bigger websites will have a lot of trouble with it…

Well, the recent migration works in the background with cronjob and I’m not sure exactly which one you’re website has the problem with. that log you provided is not very clear, is the WP_DEBUG_LOG configured on the wp-config.php?

This is from the Debug File….

It seems the log message has been removed from your reply ??

Hello @mostafas1990 all logs i have posted so far are from the Debug File, i don’t have posted any new log files ??

• This reply was modified 3 years, 7 months ago by leogc.

Actually It’s a little difficult to find the problem if there is no error log.

Can you let me know what’s your WP-Statistics table version? you can give the version number by this query:

SELECT * FROM wp_options WHERE option_name LIKE wp_statistics_plugin_version

• This reply was modified 3 years, 7 months ago by vitathemes.