HTTP Error Error in your SQL syntax

Resolved fgilio
(@francogilio)

9 years, 1 month ago

Hello,

Hello,

I’ve just send an email to you, but figured out this may be a better place.

We are using the cloud version. Since today, we are experiencing a rarely big number of ‘HTTP Error’ while uploading images. Not all images, but many. And they DO get stored in the media library, only that they appear when you reload the page.

I wonder if this may have to be related with the change to the TinyPNG and TinyJPG APIs.

Plus, I found this error while looking ar our log and it’s from some minutes ago:

Error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '-853' at line 1 de la base de datos de WordPress para la consulta SELECT orig_size-image_size FROM wp_ewwwio_images LIMIT 24000, -853 realizada por do_action('wp_ajax_ewww_savings_loop'), call_user_func_array, ewww_image_optimizer_savings_loop, W3_Db->query, W3_DbCache->query, W3_DbCallUnderlying->query, W3_Db->query, W3_DbProcessor->query, W3_Db->default_query

Maybe this last one is related to this thread?

Thanks you,
FG

https://wordpress.org/plugins/ewww-image-optimizer/

Viewing 15 replies - 1 through 15 (of 20 total)

1 2 →

Plugin Author nosilver4u
(@nosilver4u)

9 years, 1 month ago

It’s very possible that it is related to the switch if you’re using the lossy options. you’ll probably need to increase the max_execution_time for php.

The SQL error is unrelated, and I thought I had fixed that, but I’ll have to double-check. It could be something I have in the queue for this coming release.

UPDATE: there appear to have been some larger delays in processing prior to when you originally posted your question, which also coincides with the time that my rep at TinyPNG emailed me about high CPU loads that they were seeing as well. They increased their processing capacity to cope with the influx of traffic as a result, and the response times seem to have improved dramatically. Let me know if you are still seeing the HTTP errors.

Thread Starter fgilio
(@francogilio)

9 years, 1 month ago

Thanks nosilver4u!

We will see tomorrow when the editors start working.
The max_execution_time is already 30sec, so I really hope it was just about more processing capacity.

I’ll be waiting for updates regarding the SQL error.

Thank you!
FG

Plugin Author nosilver4u
(@nosilver4u)

9 years, 1 month ago

What version of the plugin are you using? As far as I can tell, I fixed it in 2.2.0, and I don’t see how it can be querying a negative number anymore when I look at the code in question.

Thread Starter fgilio
(@francogilio)

9 years, 1 month ago

We are using version 2.2.2. Please tell me if you need more info

Plugin Author nosilver4u
(@nosilver4u)

9 years, 1 month ago

Can you turn on debugging, visit the settings page (which is what triggers that portion of code), and then take a look at the debug.log file in the ewww-image-optimizer folder to see what it says near the end. Depending on how many images you have, you might need to wait 30 seconds before looking at the file, or you can use the ‘tail’ command if you have shell access to just ‘watch’ the file until it completes.

What we’re looking for, is it loops through the records in the ewwwio_images table 1000 at a time, and it will output something like “querying X records, starting at XXX”.

Also, are you on multisite?

Plugin Author nosilver4u
(@nosilver4u)

9 years, 1 month ago

Nevermind all that, I just found a way to streamline that portion of code which should help avoid these kinds of problems. Let me know if you want to try it out, and I’ll push it to the dev branch.

Thread Starter fgilio
(@francogilio)

9 years, 1 month ago

Hi!

I could try it, but in another site cause that one is live. Would what help?

Plugin Author nosilver4u
(@nosilver4u)

9 years, 1 month ago

Download it from here: https://downloads.wordpress.org/plugin/ewww-image-optimizer.zip

Thread Starter fgilio
(@francogilio)

9 years, 1 month ago

Hi! I was about to test it but find out that it was the normal version, our problem is with the Cloud variant. Should I test this anyway?

We had the same error: Error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '-306' at line 1 de la base de datos de WordPress para la consulta SELECT orig_size-image_size FROM wp_ewwwio_images LIMIT 25000, -306 realizada por do_action('wp_ajax_ewww_savings_loop'), call_user_func_array, ewww_image_optimizer_savings_loop, W3_Db->query, W3_DbCache->query, W3_DbCallUnderlying->query, W3_Db->query, W3_DbProcessor->query, W3_Db->default_query

And yes, it fires when I open the settings page.

Plugin Author nosilver4u
(@nosilver4u)

9 years, 1 month ago

Nope, don’t bother then. I’ll let you know once I’ve had a chance to sync the changes to the cloud version, they share a lot of the same code base, so that bug affects both of them.

Thread Starter fgilio
(@francogilio)

9 years, 1 month ago

nosilver4u, we’re still having problems regarding that ‘HTTP Error’. Any recommendation?

Plugin Author nosilver4u
(@nosilver4u)

9 years, 1 month ago

The only thing I know to do is to change the php and Apache timeout limits. I’ve been working with someone else on the same problem, and Apache seems to be the root cause in that case. If you don’t control your own server, you’ll need to speak with your webhost about it.

Thread Starter fgilio
(@francogilio)

9 years, 1 month ago

Well It’s already 30s. So, I’ll start testing with 40s. Would it be ok?

Plugin Author nosilver4u
(@nosilver4u)

9 years, 1 month ago

I would just bump it to 60 (I usually do increments of 30s)

rassom
(@rassom)

9 years, 1 month ago

I also see HTTP errors (one occured right now), using the paid cloud version.

It seems it’s especially with larger PNGs that they happen and it smells like timeouts. Could you ramp up the speed of the cloud servers or do something else to avoid the errors?

Thanks 🙂

PS. The option “extra PNG compression (slower)” is NOT enabled on our site.