|
Ian Cox
|
July 4, 2014 at 10:40 am
Hi, My site keeps error 502 bad gateway, the host has said to disable your plugin. Please advise.
My error log has long queries from your plugin?
Ian
|
|
Josh
|
July 4, 2014 at 11:05 am
Hi Ian,
Did your host say specifically why Event Espresso needs to be disabled? Can you let us know who the host is?
|
|
Ian Cox
|
July 4, 2014 at 11:51 am
Hi I am with wpengine
Ian
|
|
Josh
|
July 4, 2014 at 11:56 am
Hi Ian,
You might have missed the first and most important question I asked:
Did your host say specifically why Event Espresso needs to be disabled? Specifics are important because we need to know why they said this.
|
|
Ian Cox
|
July 4, 2014 at 12:58 pm
Sorry. They just said my error log is full of long queries and errors from this plug in. They then showed me my error log and it was indeed full of gibberish I don’t understand but it did say event espresso a lot!
Ian
|
|
Josh
|
July 4, 2014 at 1:47 pm
Hi Ian,
We’ll need more specific information in order to be able to help. Can you post one or two of the errors here?
|
|
Tony
|
July 4, 2014 at 2:10 pm
Hi Ian,
Unfortunately without specific errors we do not know what to look for.
If this was a common issue we would expect more reports of the same manor.
The site is running multiple shortcodes that appear to be pulling info from EE within the sidebar using the Shortcodes Ultimate plugin which may possibly be causing an issue but again without seeing the errors we can’t be sure what the issue is.
We would need to see some of the errors from within the error log, however I would advise against posting those here, at least not without removing the server path.
Do you have the error_log file?
|
|
Ian Cox
|
July 4, 2014 at 2:32 pm
[Fri Jul 04 08:40:42 2014] [error] [client 54.226.4.87] LONG QUERY (1504 characters long generated in /nas/wp/www/******/********/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php:478): SELECT Price.PRC_ID AS ‘Price.PRC_ID’, Price.PRT_ID AS ‘Price.PRT_ID’, Price.PRC_amount AS ‘Price.PRC_amount’, Price.PRC_name AS ‘Price.PRC_name’, Price.PRC_desc AS ‘Price.PRC_desc’, Price.PRC_is_default AS ‘Price.PRC_is_default’, Price.PRC_overrides AS ‘Price.PRC_overrides’, Price.PRC_order AS ‘Price.PRC_order’, Price.PRC_deleted AS ‘Price.PRC_deleted’, Price.PRC_parent AS ‘Price.PRC_parent’, Ticket_Price.TKP_ID AS ‘Ticket_Price.TKP_ID’, Ticket_Price.TKT_ID AS ‘Ticket_Price.TKT_ID’, Ticket_Price.PRC_ID AS ‘Ticket_Price.PRC_ID’, Ticket.TKT_ID AS ‘Ticket.TKT_ID’, Ticket.TTM_ID AS ‘Ticket.TTM_ID’, Ticket.TKT_name AS ‘Ticket.TKT_name’, Ticket.TKT_description AS ‘Ticket.TKT_description’, Ticket.TKT_start_date AS ‘Ticket.TKT_start_date’, Ticket.TKT_end_date AS ‘Ticket.TKT_end_date’, Ticket.TKT_min AS ‘Ticket.TKT_min’, Ticket.TKT_max AS ‘Ticket.TKT_max’, Ticket.TKT_price AS ‘Ticket.TKT_price’, Ticket.TKT_sold AS ‘Ticket.TKT_sold’, Ticket.TKT_qty AS ‘Ticket.TKT_qty’, Ticket.TKT_uses AS ‘Ticket.TKT_uses’, Ticket.TKT_taxable AS ‘Ticket.TKT_taxable’, Ticket.TKT_is_default AS ‘Ticket.TKT_is_default’, Ticket.TKT_order AS ‘Ticket.TKT_order’, Ticket.TKT_row AS ‘Ticket.TKT_row’, Ticket.TKT_deleted AS ‘Ticket.TKT_deleted’, Ticket.TKT_parent AS ‘Ticket.TKT_parent’ FROM wp_esp_price AS Price LEFT JOIN wp_esp_ticket_price AS Ticket_Price ON Ticket_Price.PRC_ID=Price.PRC_ID LEFT JOIN wp_esp_ticket AS Ticket ON Ticket.TKT_ID=Ticket_Price.TKT_ID WHERE Ticket.TKT_ID = 51 ORDER BY Price.PRC_order ASC
One of the many, hope this makes sense to you?
Ian
|
|
Josh
|
July 4, 2014 at 3:16 pm
Yes it does, and it turns out these are notices that WPEngine generates when there’s a query longer than 1024 characters. While we could make our queries shorter by abbreviating everything, doing so would not optimize them.
The notices you are seeing in the log file are examples of WP Engine doing everything they can to identify every little thing that may be preventing optimal performance and in some cases this warning may be identifying a valid performance concern. In the entry you posted here, there’s a single join which is fine.
More thoughts on this have been discussed by other developers here:
https://github.com/pods-framework/pods/issues/2093#issuecomment-38715948
And WPEngine has an explanation of the long query log entry here as well:
http://wpengine.com/support/long-query-killed-query-error-logs/
Note that they say “We have included it in the log to signify that the length of the query, which would be over 1,024 characters, is a Long Query and may be able to be optimized. We did not take any action on this query, it is just a notice to our customers.”
Summed up, according to WPEngine, it’s just a notice.
Please check back with WPEngine support and ask them if they can pinpoint the source of the 502 bad gateway errors. While they do so, it will be very helpful if they can avoid being misled by the ambiguous notices that they’re generating with regards to queries that are longer than 1024 characters.
|
|
Ian Cox
|
July 5, 2014 at 3:33 am
Thanks for your help, I will get back on to them.
Ian
|
