|
Adam McLane
|
January 19, 2015 at 12:25 pm
Hi there. I’m trying to troubleshoot some issues I’m seeing in my error log. I’m not exactly sure what’s going on, but hoping the error log below will offer some insight.
WP- 4.1
EE- 4.4.8.p
Here’s a peak at a few items in my error log, lots more like this:
http://pastebin.com/1HywHePG
|
|
Sidney Harrell
|
January 19, 2015 at 1:35 pm
Apparently, any function call that takes longer than a fifth of a second gets logged. Whether that time is abnormal for that function would be impossible for us to determine. It greatly depends on your server’s physical hardware and it’s configuration, ie. how many other sites are hosted on that physical server, how much traffic they are getting, the load produced by them, how the load is spread over the apache threads, if the threads are configured to be guaranteed a minimum of physical resources, etc.
|
|
Adam McLane
|
January 19, 2015 at 2:26 pm
Hmm… I see your point. But you know I’m just the go between here, right? I’m trying to figure out what the problem is and the host is going to point to you and you are going to point to the host.
Are there any common problems you’ve had with WP Engine users?
|
|
Lorenzo Orlando Caum
|
January 19, 2015 at 3:51 pm
Hi, we aren’t aware of any major issues with Event Espresso and WP Engine.
We do need WP Engine to setup no-cache rules for Event Espresso to work correctly:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
This also applies to other ecommerce platforms for WordPress.
I also use WP Engine for my own WordPress projects and testing Event Espresso and have not run into any issues.
—
Lorenzo
|
|
Adam McLane
|
January 19, 2015 at 4:09 pm
OK, thanks for that. I’ll give them that documentation, we’ve opted out all of our WooCommerce stuff, I’m sure they know the drill. Hopefully this will clear up the errors, I’ll confirm in a little bit.
|
|
Adam McLane
|
January 19, 2015 at 5:15 pm
@lorenzo – Thanks, we’ve cleared up the cache issue. And the second item on there, Heartbeat API, was already resolved.
Still seeing errors in the log. Pretty much any time someone accesses the plugin it logs an error. I’m not sure if that’s really causing a problem which is slowing my site down or if it’s just a smoke screen… equivalent to “turn it on, turn it off.”
|
|
Dean
|
January 20, 2015 at 1:29 am
Hi,
According to the WP Engine site, this logging is standard procedure and is not meant for human eyes:
[WPE Monitoring] function.session_start:
Default PHP Function we’ve added to the error log to determine when sessions are resumed or opened; which is identified by either a GET, POST, or cookie. Session data is saved in a serialized format which PHP retrieves and unserializes in order to populate $_SESSION. This log is intended only for our platform to read and is not intended for humans to read. We use this log to help monitor, evaluate, and optimize sites on our platform.
(Bolded text by me)
http://wpengine.com/support/troubleshoot-wordpress-wp-engine-error-log/
|
|
Adam McLane
|
January 20, 2015 at 4:38 pm
@dean – Thanks for that. I’ll have to call that out to WPE. Seems like they are throwing up a smoke signal. I asked “why is my site running slow” and this is what they pointed to. Not cool.
Let’s close this thread. 🙂
|
