|
utahhockey
|
November 10, 2017 at 2:55 pm
EE is causing memory errors.
[Fri Nov 10 08:18:21.334002 2017] [:error] [pid 6523] [client 70.103.181.12:41911] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/vhosts/universityofutahhockey.com/httpdocs/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/dompdf/include/frame.cls.php on line 421, referer: https://universityofutahhockey.com/?ee=msg_url_trigger&snd_msgr=html&gen_msgr=html&message_type=receipt&context=purchaser&token=1-287afe96ad844e8594b5ecbc7fe0c4f7&GRP_ID=9&id=74153
[Fri Nov 10 12:48:41.570575 2017] [:error] [pid 6522] [client 128.110.74.1:51806] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 74 bytes) in /var/www/vhosts/universityofutahhockey.com/httpdocs/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/dompdf/include/frame.cls.php on line 574, referer: https://universityofutahhockey.com/?ee=msg_url_trigger&snd_msgr=html&gen_msgr=html&message_type=receipt&context=purchaser&token=1-750079b95d28a3a00170a15265b63730&GRP_ID=9&id=74159
|
|
Josh
|
November 10, 2017 at 3:13 pm
Hi utahhockey,
The error there does not mean Event Espresso is causing the issue, it means that at the time when someone tried to download a PDF from, the server was running low on memory and the memory limit was exceeded. You can prevent this by reducing the amount of memory needed to generate a PDF (it will likely help if this huge image is removed from the invoice) and by setting a higher memory limit:
http://www.wpbeginner.com/wp-tutorials/fix-wordpress-memory-exhausted-error-increase-php-memory/
|
|
utahhockey
|
November 10, 2017 at 3:37 pm
Josh,
XMission has tons of logs showing EE is the problem. Additionally, that “huge” image is only 482k in size. How could such a small file be causing an issue?
|
|
Josh
|
November 10, 2017 at 8:07 pm
It’s not the size in bytes, when DOMPDF renders larger pixel size photos it can take quite a bit of memory. Can you try removing or reducing the pixel size of the venue image?
If not, can you follow this guide to bump up the amount of memory?
|
|
utahhockey
|
November 11, 2017 at 12:22 pm
Josh, I’ve reduced the size of that image per your request. Will you let me know if its more effecient now?
|
|
Josh
|
November 13, 2017 at 10:16 am
Hi AJ,
That seemed to have helped because I can download an invoice now, where before the server would crash.
|
|
utahhockey
|
November 15, 2017 at 5:36 pm
XMission has reported the same issue with EE:
Jace: One thing we just noticed is that MySQL seems to be getting hammered pretty hard
Jace: Not sure what yet
Jace: Something to do with the plugin at /var/www/vhosts/universityofutahhockey.com/httpdocs/wp-content/plugins/event-espresso-core-reg/core/services/cache/TransientCacheStorage.php
|
|
utahhockey
|
November 15, 2017 at 5:43 pm
Additionally our site is taking 20-30 seconds to load with EE enabled. With it disabled, it takes less than a second.
|
|
utahhockey
|
November 15, 2017 at 5:53 pm
Hey AJ,
From what I can tell, that plugin is doing caching, but not clearing the cache periodically, so it just gets bigger and bigger and the site gets slower and slower.
—
|
|
utahhockey
|
November 15, 2017 at 6:00 pm
Jace: Hey
utahhockey.com: Hi!
utahhockey.com: Can you clarify something for me?
utahhockey.com: If I were to approve more RAM for this server, the caching issue would still continue correct?
Jace: Yeah it would just continue to build up until it fills even that
utahhockey.com: Would just take longer to fill?
Jace: But I mean, that wouldn’t take long
utahhockey.com: Ha!
utahhockey.com: Can I manually clear it?
Jace: Hey, you have lots of traffic this time of year! 🙂
utahhockey.com: Indeed.
utahhockey.com: I’ve allready submitted a bug to Event Espresso.
utahhockey.com: They are a Utah company so hopefully they resolve it quickly.
Jace: So, we cleared down the caches query down to 1 array, and then reopened it immediately and it was back up to 35. It was 150k when we cleared it
utahhockey.com: Unreal. And now the site is totally snappy.
utahhockey.com: So its safe to say we found the issue correct?
Jace: Yeah, seeing it try to push 150k arrays in to mysql was something to witness
utahhockey.com: hahahahaha
Jace: But yeah, that seems to be the big factor right now
utahhockey.com: Cool. I will relay this information to them.
utahhockey.com: Thanks again.
|
|
utahhockey
|
November 15, 2017 at 6:01 pm
Jace: Oh, I forgot to mention, the file that had it was all serialized
Jace: So manually clearing it is not advised
utahhockey.com: Understood. THanks!
|
|
Josh
|
November 16, 2017 at 8:26 am
Hi AJ,
Did they mention exactly what they cleared when they “we cleared down the caches query down to 1 array”?
|
|
utahhockey
|
November 16, 2017 at 12:20 pm
I don’t know.
|
|
Josh
|
November 16, 2017 at 12:39 pm
Can you find that out from them? I do not want to assume something incorrect, then give you some instructions on how to fix, which turn out to be an incorrect assumption.
|
|
utahhockey
|
November 16, 2017 at 12:41 pm
Probably be easiest for you to contact them. Ask for Benji.
I’m to busy handling pissed off customers right now…
|
|
Josh
|
November 16, 2017 at 12:57 pm
Hi AJ,
You’ll need to contact them and you can follow up here or send us an email.
For what it’s worth, I just checked your site and it’s not showing any signs of taking 20-30 seconds to load, and I see that Event Espresso is activated at the moment.
|
|
utahhockey
|
November 16, 2017 at 12:59 pm
They are refusing to help me anymore because of all the problems EE has caused. PLEASE call them directly to get your questions answered. It makes no sense to have me be a middle man.
|
|
Josh
|
November 16, 2017 at 1:09 pm
AJ,
You are their customer. If they refuse to help you then it’s time to find a new host. I can recommend any one of the hosts here:
https://eventespresso.com/requirements/
|
|
utahhockey
|
November 16, 2017 at 1:11 pm
But this is an EE problem. You know it and they know it, and has nothing to do with me. Their servers are working just fine. Why won’t you just call them?
|
|
Josh
|
November 16, 2017 at 2:01 pm
I actually disagree that the problem is caused by Event Espresso. What the host found is a symptom to a larger problem. They mentioned this:
So, we cleared down the caches query down to 1 array, and then reopened it immediately and it was back up to 35.
I’m interested in seeing the data for those 35 initial records (and the others after that). Event Espresso doesn’t spontaneously generate those, something else is.
If you can complete the secure form on this page someone from EE staff can take a look at that data.
Why won’t you just call them?
I think that would be a waste of time because your host would not respond to your questions. If they aren’t responding to you, a paying customer, is it reasonable to expect they would respond to someone who is not their customer?
|
|
utahhockey
|
November 16, 2017 at 2:33 pm
Josh,
Without EE there is no issue. Once EE is activated the problem returns. To say it is not an EE issue is ludicrous.
I pay Event Espresso and XMission. I’m asking two vendors to simply work together so I am absolutely miffed as to why you would think that its a waste of time. Especially when I, the customer, am simply asking to be eliminated as the middle man.
We have an IT problem that must be solved by the plugin developer (Event Espresso) and the ISP. Why in the world does this process need to be slowed down by me?
To clarify they are responding to me. Their response is that this is a plugin problem, which has been proven by disabling Event Espresso. So their answer is to not use the plugin, which isn’t helpful to anyone.
|
|
utahhockey
|
November 16, 2017 at 2:36 pm
Josh,
Here is your requested information. If you need anything else please contact XMission directly.
AJ,
We saw the mysql query with that:
4336 Query UPDATE wp_options SET option_value = ‘a:43:{s:39:”ee_ssn_7d0287a3f52700dc1943e4acd8e5dd88″;i:1510178400;s:39:”ee_ssn_dab258ee4ab35ea3711c8233e587848c”;i:1510797600;s:39:”ee_ssn_46bf8a6144c0bcd98b01d2723c653eb1″;i:1510797600;s:39:”ee_ssn_194b2037795ab9b89620dfefaa296bc4″;i:1510797600;s:39:”ee_ssn_9af16c5e300aae996d7f3fca9511e88b”;i:1510797600;s:39:”ee_ssn_1f6dcc0496623b56c2ea8b2aff48bf8e”;i:1510797600;s:39:”ee_ssn_e4d9ce90096b5d90e5fc698c5c42a64f”;i:1510797600;s:39:”ee_ssn_37b2f314147f9f7311811532106e77cc”;i:1510797600;s:39:”ee_ssn_6d6571ccad9efe2a785e81cf5de5ec5f”;i:1510797600;s:39:”ee_ssn_cd79729b2448144251aaca27504b3fa5″;i:1510797600;s:39:”ee_ssn_bb9bd9f55b57b1e2f9b4c231f1375e75″;i:1510797600;s:39:”ee_ssn_7e915618bef5a582ecee68be2bce76e8″;i:1510797600;s:39:”ee_ssn_832c4e5be070e579d33ac3de63e033fe”;i:1510797600;s:39:”ee_ssn_d8850aa8029c31c5334c08e49e7c0c17″;i:1510797600;s:39:”ee_ssn_aac7da5d44d8ee0afaf139c7d25982ec”;i:1510797600;s:39:”ee_ssn_ccfecf9af4713b587acde637e8
cb1145″;i:1510797600;s:39:”ee_ssn_4d3ff595a8db31f8f2ded8ea8c1cbbb9″;i:1510797600;s:39:”ee_ssn_1badc966a0ca0e4b9a312a59c47e3034″;i:1510797600;s:39:”ee_ssn_6363eae31df513dd71ff470efad31014″;i:1510797600;s:39:”ee_ssn_1b159e828277ce2b12394c3e543ffeaa”;i:1510797600;s:39:”ee_ssn_7ff1a67d9795d5ca5d016c69dcbd0945″;i:1510797600;s:39:”ee_ssn_f9c54650d559292d47126b3830a547a2″;i:1510797600;s:39:”ee_ssn_220bdd238cf2fa67e1a4b30bc7c0caab”;i:1510797600;s:39:”ee_ssn_6205bb7c3154bee815c8a0b80a3c2598″;i:1510797600;s:39:”ee_ssn_b2fcc5f42eb68379a4b54ad2dd6354dd”;i:1510797600;s:39:”ee_ssn_bdc2e4903120a414c89d52c381b97283″;i:1510797600;s:39:”ee_ssn_1b7d7a38622d810437c62800f844ecb7″;i:1510797600;s:39:”ee_ssn_3de27a99051e0ab7c8edabba6571c3c6″;i:1510797600;s:39:”ee_ssn_0322ac4f3db240a8daed73b1425883e3″;i:1510797600;s:39:”ee_ssn_c9a2415431b8170d2b82c2c950cc427f”;i:1510797600;s:39:”ee_ssn_edb8a87e48f5d1bcb689c988ea5e8468″;i:1510797600;s:39:”ee_ssn_33d04ed00223b7bbe4eec784f0fae9db”;i:1510797600;s:39:”ee_ssn_67c
ccb9325efa7873f296341360053e3″;i:1510797600;s:39:”ee_ssn_ae0deb516ddaaaaa1252282379696ca8″;i:1510797600;s:39:”ee_ssn_cba64430eb396e98d70dbbbd157c0ca6″;i:1510797600;s:39:”ee_ssn_e33599c58a265644606a9ccd9723a757″;i:1510797600;s:39:”ee_ssn_88bf803373e6412192645681c2935e0f”;i:1510797600;s:39:”ee_ssn_f3402862b73897e954fe194d31167b1a”;i:1510797600;s:39:”ee_ssn_edcfa48e07bfebb15efff0b7c7723c1b”;i:1510797600;s:39:”ee_ssn_13d8d9c86a98315a5034e74b686fe5d3″;i:1510797600;s:39:”ee_ssn_d5c72d5487c2542ef40f266a5c854e03″;i:1510797600;s:39:”ee_ssn_3e90ce25691c68cfcbdf8d0f34237cd3″;i:1510797600;s:39:”ee_ssn_ec476ca55f1471c8f88ac3902d5c1d20″;i:1510797600;}’ WHERE option_name = ‘ee_transient_schedule’
|
|
utahhockey
|
November 16, 2017 at 2:37 pm
This is what they can run to find what we did:
select option_id,option_name,length(option_value) as ValLength from wp_options where (option name like ‘ee_transient%’);
-Jace
[jwal – Thu Nov 16 13:54:33 2017]:
AJ,
We saw the mysql query with that:
4336 Query UPDATE wp_options SET option_value =
‘a:43:{s:39:”ee_ssn_7d0287a3f52700dc1943e4acd8e5dd88″;i:1510178400;s:39:”ee_ssn_dab258ee4ab35ea3711c8233e587848c”;i:1510797600;s:39:”ee_ssn_46bf8a6144c0bcd98b01d2723c653eb1″;i:1510797600;s:39:”ee_ssn_194b2037795ab9b89620dfefaa296bc4″;i:1510797600;s:39:”ee_ssn_9af16c5e300aae996d7f3fca9511e88b”;i:1510797600;s:39:”ee_ssn_1f6dcc0496623b56c2ea8b2aff48bf8e”;i:1510797600;s:39:”ee_ssn_e4d9ce90096b5d90e5fc698c5c42a64f”;i:1510797600;s:39:”ee_ssn_37b2f314147f9f7311811532106e77cc”;i:1510797600;s:39:”ee_ssn_6d6571ccad9efe2a785e81cf5de5ec5f”;i:1510797600;s:39:”ee_ssn_cd79729b2448144251aaca27504b3fa5″;i:1510797600;s:39:”ee_ssn_bb9bd9f55b57b1e2f9b4c231f1375e75″;i:1510797600;s:39:”ee_ssn_7e915618bef5a582ecee68be2bce76e8″;i:1510797600;s:39:”ee_ssn_832c4e5be070e579d33ac3de63e033fe”;i:1510797600;s:39:”ee_ssn_d8850aa8029c31c5334c08e49e7c0c17″;i:1510797600;s:39:”ee_ssn_aac7da5d44d8ee0afaf139c7d25982ec”;i:1510797600;s:39:”ee_ssn_ccfecf9af4713b587acde637e8cb1145″;i:1510797600;s:39:”ee_ssn_4d3ff595a8db3
1f8f2ded8ea8c1cbbb9″;i:1510797600;s:39:”ee_ssn_1badc966a0ca0e4b9a312a59c47e3034″;i:1510797600;s:39:”ee_ssn_6363eae31df513dd71ff470efad31014″;i:1510797600;s:39:”ee_ssn_1b159e828277ce2b12394c3e543ffeaa”;i:1510797600;s:39:”ee_ssn_7ff1a67d9795d5ca5d016c69dcbd0945″;i:1510797600;s:39:”ee_ssn_f9c54650d559292d47126b3830a547a2″;i:1510797600;s:39:”ee_ssn_220bdd238cf2fa67e1a4b30bc7c0caab”;i:1510797600;s:39:”ee_ssn_6205bb7c3154bee815c8a0b80a3c2598″;i:1510797600;s:39:”ee_ssn_b2fcc5f42eb68379a4b54ad2dd6354dd”;i:1510797600;s:39:”ee_ssn_bdc2e4903120a414c89d52c381b97283″;i:1510797600;s:39:”ee_ssn_1b7d7a38622d810437c62800f844ecb7″;i:1510797600;s:39:”ee_ssn_3de27a99051e0ab7c8edabba6571c3c6″;i:1510797600;s:39:”ee_ssn_0322ac4f3db240a8daed73b1425883e3″;i:1510797600;s:39:”ee_ssn_c9a2415431b8170d2b82c2c950cc427f”;i:1510797600;s:39:”ee_ssn_edb8a87e48f5d1bcb689c988ea5e8468″;i:1510797600;s:39:”ee_ssn_33d04ed00223b7bbe4eec784f0fae9db”;i:1510797600;s:39:”ee_ssn_67cccb9325efa7873f296341360053e3″;i:1510797600;s:3
9:”ee_ssn_ae0deb516ddaaaaa1252282379696ca8″;i:1510797600;s:39:”ee_ssn_cba64430eb396e98d70dbbbd157c0ca6″;i:1510797600;s:39:”ee_ssn_e33599c58a265644606a9ccd9723a757″;i:1510797600;s:39:”ee_ssn_88bf803373e6412192645681c2935e0f”;i:1510797600;s:39:”ee_ssn_f3402862b73897e954fe194d31167b1a”;i:1510797600;s:39:”ee_ssn_edcfa48e07bfebb15efff0b7c7723c1b”;i:1510797600;s:39:”ee_ssn_13d8d9c86a98315a5034e74b686fe5d3″;i:1510797600;s:39:”ee_ssn_d5c72d5487c2542ef40f266a5c854e03″;i:1510797600;s:39:”ee_ssn_3e90ce25691c68cfcbdf8d0f34237cd3″;i:1510797600;s:39:”ee_ssn_ec476ca55f1471c8f88ac3902d5c1d20″;i:1510797600;}’
WHERE option_name = ‘ee_transient_schedule’
|
|
Josh
|
November 16, 2017 at 2:59 pm
Hi AJ,
That last query shows that the ee_transient_schedule option has 43 records, which is a reasonable amount and would not cause any RAM issues.
We’re not going to contact your host. We’re more than happy to investigate further if you can complete the login details form.
|
|
utahhockey
|
November 16, 2017 at 3:05 pm
Josh,
I did exactly what you asked and now you are refusing to understand why XMISSION thinks this is a problem. Your refusal to bring in other opinions is ridiculous.
If you aren’t willing to help, please pass this ticket to someone who is. This back and forth is waisting everyone’s time.
|
|
Josh
|
November 16, 2017 at 3:21 pm
I completely understand why XMission sees it’s a problem that the ee_transient_schedule gets so huge. That’s a completely valid problem that it got to 150K as they found, but there’s something missing from this picture.
The question I have, and they may or may not have an idea about, is why is that option filling up so fast? I mentioned before that Event Espresso does not spontaneously start sessions to fill just to fill that option and bring your site down. So what they found is a symptom, not the cause.
The underlying issue needs to be addressed. I am more than happy to look at the actual transient record strings (which will include the user agent). That may shed some light on what’s happening and we can find a solution for you. For example your site might be getting hammered on by a content scraper bot. If that’s the case we can make an edit to the .htaccess file and block that bot before it hits your site.
|
