Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: Asia/Singapore (GMT+08:00)

Tagged: 

This topic contains 71 replies, has 2 voices.

Last updated by Kor 1 year, 3 months ago.

Assisted by: Kor.

Author Posts
October 14, 2023 at 7:00 pm #14577885

louisN-4

Since yesterday (friday) noon - We keep seeing in Query Monitor the following queries non stop in the past over 24 hours

And our DB spiked in CPU

1.
SELECT wpml_translations.element_id, tax.term_id, tax.taxonomy
FROM lsk_icl_translations wpml_translations JOIN lsk_term_taxonomy tax
ON wpml_translations.element_id = tax.term_taxonomy_id
AND wpml_translations.element_type = CONCAT('tax_', tax.taxonomy) JOIN lsk_terms terms
ON terms.term_id = tax.term_id
WHERE tax.term_id != tax.term_taxonomy_id

2.
SELECT jobs.rid, jobs.job_id as jobId, jobs.editor_job_id as ateJobId, jobs.automatic , translation_status.status, translation_status.review_status, jobs.ate_sync_count > 100 as isLongstanding
FROM lsk_icl_translate_job as jobs
INNER JOIN lsk_icl_translation_status translation_status
ON translation_status.rid = jobs.rid
INNER JOIN lsk_icl_translations translations
ON translation_status.translation_id = translations.translation_id
INNER JOIN lsk_icl_translations parent_translations
ON translations.trid = parent_translations.trid
AND parent_translations.source_language_code IS NULL
LEFT JOIN lsk_posts posts
ON parent_translations.element_id = posts.ID
WHERE jobs.job_id IN (
SELECT MAX(job_id)
FROM lsk_icl_translate_job
GROUP BY rid )
AND jobs.editor = 'ate'
AND ( translation_status.status IN (1,2,40)
OR 1=0 )
AND translations.language_code IN ('nl','en','de','he','ru')
AND ( posts.post_status IS NULL
OR posts.post_status <> 'trash' )

3.
SELECT COUNT(jobs.job_id)
FROM lsk_icl_translate_job as jobs
WHERE jobs.editor = 'ate'

4.
SELECT jobs.rid, jobs.job_id as jobId, jobs.editor_job_id as ateJobId, jobs.automatic , translation_status.status, translation_status.review_status, jobs.ate_sync_count > 100 as isLongstanding
FROM lsk_icl_translate_job as jobs
INNER JOIN lsk_icl_translation_status translation_status
ON translation_status.rid = jobs.rid
INNER JOIN lsk_icl_translations translations
ON translation_status.translation_id = translations.translation_id
INNER JOIN lsk_icl_translations parent_translations
ON translations.trid = parent_translations.trid
AND parent_translations.source_language_code IS NULL
LEFT JOIN lsk_posts posts
ON parent_translations.element_id = posts.ID
WHERE jobs.job_id IN (
SELECT MAX(job_id)
FROM lsk_icl_translate_job
GROUP BY rid )
AND jobs.editor = 'ate'
AND ( translation_status.status IN (30)
OR translation_status.review_status IN ( 'NEEDS_REVIEW','EDITING' ) )
AND translations.language_code IN ('nl','en','de','he','ru')
AND ( posts.post_status IS NULL
OR posts.post_status <> 'trash' )

We believe our case is similar to these:
A. https://wpml.org/forums/topic/unknown-column-errors-in-database-after-wpml-upgrade/
B. https://wpml.org/forums/topic/loads-forever/

And we would like for your assistance

October 15, 2023 at 6:07 pm #14580339

louisN-4

we ran this, and now db is more calm, but i guess something needs to be fixed on the db level

function wpmlsupp_1706_reset_wpml_capabilities() {
if ( function_exists( 'icl_enable_capabilities' ) ) {
icl_enable_capabilities();
}
}
add_action( 'shutdown', 'wpmlsupp_1706_reset_wpml_capabilities' );

October 15, 2023 at 10:32 pm #14580807

louisN-4

Edit : https://pastebin.com/4guASzws

October 16, 2023 at 9:08 am #14582771

louisN-4

WHY NO ONE ANSWERS?

October 16, 2023 at 9:30 am #14582911

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Hello,

Thank you for reaching out to WPML support.

I would like to extend my apologies for the delayed response, which was due to the weekend.

I have taken the liberty of copying your database logs into Pastebin. While we proceed with the investigation, could you please perform a complete backup of your website and update all WPML plugins to their latest versions? After completing this step, please go to WPML > Support > Troubleshooting and execute the options available on that page.

Once you have completed these tasks, kindly verify whether the database issue still persists, and please provide me with an update on the results here. Your cooperation is greatly appreciated.

October 16, 2023 at 9:39 am #14583015

louisN-4

1. Their is no need to update to latest plugin, it will cause more problems, before we fix the DB problem that clearly is showing - we have 4.6.4, and we are waiting for 4.7 (as shown in ticket
https://wpml.org/forums/topic/options-autoload-slow-ttfb/page/4/)

2. i will also not execute the support troubleshooting, before you enter our phpmyadmin and check the db issues, as its clearly db issues

3. i ask you not to stall time and open private box, so i can give you admin and i can give you phpmyadmin access, so you can see what column is missing on the db, clearly someting happened while we were string translating

October 16, 2023 at 9:42 am #14583017

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply.

It looks like our 2nd Tier Support is aware of your issue. I will escalate this and I've enabled a private reply option for you. I apologize for the inconvenience.

October 16, 2023 at 11:16 am #14583971

louisN-4

the 2nd tier on the other ticket is related to some caching issue

this issue is new, and its probably while we were string transalting, a flag on the db went missing,

are you handling it?

October 16, 2023 at 2:16 pm #14585865

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

I appreciate your response.

I have provided another private message box for your convenience. Could you please outline the necessary steps to reproduce the problem and share some screenshots? This would greatly assist in expediting the resolution process, eliminating the need for multiple follow-up requests for additional information.

October 16, 2023 at 6:44 pm #14588175

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply.

I can't seem to open your login link and also your Website. Could you possibly check with your hosting provider and ask them to temporarily remove the restrictions?

October 16, 2023 at 6:52 pm #14588217

louisN-4

Kor,

Your behaviour is not right

I reported this 2 days ago, i said its URGENT, you know its URGENT, and you wait for 21:47PM my time to finally open an admin link i gave you 12 hours ago

I told you our DB is looping and you are relaxed enough to not investigate right away

i will now approach the hosting company to restart the server,

BUT I AM TELLING YOU TAKE THIS CASE REAL SERIOUSLY,

THE SERVER DB IS LOOPING AND CAUSING CPU AND RAM TO SPIKE AND BURN

AND IT COULD CRASH EVERYTHING BECAUSE OF YOUR LAID BACK APPROACH !

October 16, 2023 at 6:58 pm #14588227

louisN-4

the server was restarted

PLEASE DO NOT TAKE YOUR TIME - PLEASE ACT NOW TO FIX THIS

October 16, 2023 at 7:01 pm #14588293

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply.

I'm able to access the site now. Please allow me to escalate this to our second-tier support now and I will get back to you once I've feedback.

October 16, 2023 at 7:10 pm #14588319

louisN-4

what is the reason not to handle and escalate it 12 hours ago, when i wrote its urgent and i showed you the issue?

i keep getting newrelic notices about cpu spike up and down, THIS IS CRITICAL MAN

and i am sure for someone in your team, it would be very easy to resolve what column is missing what in our db due to something malfunctioning with your plugin

October 16, 2023 at 7:20 pm #14588341

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply.

Sorry, it took some time to verify the issue due to the ticketing queue. I've already escalated this and I will come back to once I've feedback.

The topic ‘[Closed] URGENT – WPML DB LOOPING’ is closed to new replies.