|
JijOnline
|
March 2, 2015 at 3:26 am
Hey guys,
It seems te second to last update is causing issues on our website. Since, we have problems with the server load and only when EE4 is enabled. Basically the server load jumps so high (adding 80-90%) and the whole website becomes unavailable (DB connection errors). After I disable EE it drops back to normal operating loads and everything is fine again.
How can we resolve this the best way? I can provide login information, and I can ask my host for logs, what would work best here?
Cheers,
|
|
Josh
|
March 2, 2015 at 10:46 am
Hi there,
A quick way to possibly find out the cause of the load increase is enable WP_DEBUG (and you can enable logging only so the errors do not display on the site) with EE4 activated, then check the log file in wp-content/debug.log.
|
|
JijOnline
|
March 4, 2015 at 8:47 am
It runs about half a minute, and then we get this:
Unable to allocate memory for pool.
Coming from wp-settings.php
nothing beforehand indicating of any significant issues.
Followed by a bunch of Lost connection to MySQL server during query and PHP running out of memory.
Currently running 4.6.12.p I saw an update message, which has magically disappeared too. Can I update by *just* uploading 13.p?
I might also note that previously I saw a bunch of these messages:
Database table wp_esp_answer existed when it shouldn’t, and probably contained erroneous data. You probably restored to a backup that didn’t remove old tables didn’t you? We recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from wp_esp_answer. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from wp_esp_answer manually then restore to the backup again.
Basically for every EE table I could see. And as we didn’t restore any backups it confused me so I removed the notices.
|
|
Josh
|
March 4, 2015 at 10:25 am
Hi there,
It may be the database warning has to do with the database connection issues right now. What could happen is the request that setup the database had a connection issue after setting up some tables; and then on the next request it tried to set up the tables again.
May I ask where you saw those messages?
We may be able to find out more information about what’s causing the database connection issues if you can send FTP + WP admin credentials. If that works for you, please send temporary credentials via the contact form on this page:
https://eventespresso.com/send-login-details/
|
|
JijOnline
|
March 4, 2015 at 1:56 pm
Hey Josh,
I’ve just submitted all info. The messages were in the admin environment. Can’t remember if they were on a specific page. It could very well be the case. I remember doing an update of the plugin and the messages appeared shortly after.
Please don’t debug by switching EE on, as it will cripple the server (getting those logs costed me half an hour of downtime).
Thanks for your time and effort, really appreciated!
|
|
Josh
|
March 4, 2015 at 5:11 pm
Hi there,
We’re not going to activate EE, so no worries there.
One thing that you can do that may help is go into phpmyAdmin, and go into the wp_options table and do a search for an option name using the LIKE %…% operator for this value: ee_ssn.
That will pull up quite a few transient records that you do not need, and those can be deleted. This will free up quite a bit of your options table and may help with the server load.
The current version of EE4.6 has a fix for those transients so they’ll correctly expire and garbage collection will kick in and automatically remove those. So you’ll only need to do this once before you update to the current version once you can activate EE again.
|
|
JijOnline
|
March 7, 2015 at 12:13 am
YES!
I removed ~41k lines and the updated the plugin. It seems to be running smoothly for the last ten minutes now. Previously it would lock up instantly.
Thank you for the time and effort!
With the cause, effect and new version I consider this issue resolved!
|
