Support

Home Forums Event Espresso Premium Internal Service Error and Data Migration issues

Internal Service Error and Data Migration issues

Posted: January 3, 2017 at 8:04 pm

Viewing 20 reply threads


lospoblanos

January 3, 2017 at 8:04 pm

Hi,

We recently updated our license and attempted to update the plugin from version 4.8.18.p to 4.9.24.p and received an internal server error. We attempted again to update the plugin manually via FTP and encountered the following Data Migration Error:
“<br /> <b>Fatal error</b>: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1749935 bytes) in <b>/home/ourusername/ourdomain.com/wp-includes/functions.php</b> on line <b>384</b><br />”

How can we resolve this?

Thanks,


Tony

  • Support Staff

January 4, 2017 at 5:37 am

Hi there,

Thank you for sending the migration logs, it helps 🙂

The error your getting means your site is running out of memory, however with 256MB of ram that’s usually fine for migrations (although it is heavily dependent on what plugins and theme you are using).

You could try increasing the amount of memory available to run the migration, to do that you would add something like:

define('WP_MEMORY_LIMIT', '512M');

To your wp-config.php file.

The above depends if you have that amount of memory available on the server and if you host allows you to change the available memory setting.

Another option is to reduce the migration step size EE uses to reduce the amount of memory needed for each step (the migration will take longer), for that you can use:

define( EE_MIGRATION_STEP_SIZE, 10 );

Again this is within the wp-config.php file

We recently updated our license and attempted to update the plugin from version 4.8.18.p to 4.9.24.p and received an internal server error.

Looking over the logs it looks like you updated from 4.8.18 to 4.9.1 previously then back down to 4.8.18.

Did you have problems with 4.9.1 back then?


lospoblanos

January 4, 2017 at 1:17 pm

Hi,

Thanks for the reply.

1. We already have our memory at 500M.

2. Yes, we updated to 4.9 but ran into the data migration error. We went back o 4.8 because we need a working calendar. We will try adding the migration step size code to wp-config and attempt to update again.

Thanks


Tony

  • Support Staff

January 4, 2017 at 4:07 pm

1. We already have our memory at 500M.

You may have set the value to 500MB however the error message indicates you are running out of memory around 256MB:

Allowed memory size of 268435456 bytes exhausted (tried to allocate 1749935 bytes)

268435456 bytes is roughly 256MB, so your server only has that amount of memory.

2. Yes, we updated to 4.9 but ran into the data migration error. We went back o 4.8 because we need a working calendar. We will try adding the migration step size code to wp-config and attempt to update again.

Please do keep us updated with this.


lospoblanos

January 4, 2017 at 6:19 pm

Hi again,

I reached out our hosting provider and they said we actually have a memory limit of 521M. We added “define( EE_MIGRATION_STEP_SIZE, 10 );” to wp-config and reattempted plugin update. We are still getting the memory exhaustion error during data migration. We just purchased the full version of your plugin and expect this work asap.


Tony

  • Support Staff

January 5, 2017 at 4:15 am

I reached out our hosting provider and they said we actually have a memory limit of 521M.

Unfortunately regardless of what the host is stating the error message indicates your site is running out of memory at 256MB.

Allowed memory size of 268435456 bytes exhausted (tried to allocate 1749935 bytes)

Although that error is being triggered during the migration, its not an error from Event Espresso, it’s a PHP error stating there is no more memory.

I can see in the migration log the local value is set to 500M however the host can override this and if you only have 256MB available from the host whatever higher value you set locally (within your site) is ignored.

We added “define( EE_MIGRATION_STEP_SIZE, 10 );” to wp-config and reattempted plugin update. We are still getting the memory exhaustion error during data migration.

You could try temporarily disabling some other plugins to free up memory before running the migration, for example some page builder plugins such as Visual Composer require at least 128MB but can often need more.

We just purchased the full version of your plugin and expect this work asap.

I understand you want this working, however so far the error message shows the site is running out of memory. Its not an issue with EE although EE is triggering the error simply because the migration requires memory to run.


Josh

  • Support Staff

January 5, 2017 at 7:02 am

Do you have this code set in the wp-config.php file before the line that says stop editing?

define('WP_MEMORY_LIMIT', '512M');


lospoblanos

January 5, 2017 at 11:06 pm

Hello again,

Unfortunately we’ve been unable to resolve the updating issue. Here’s what we’ve done:

1. Upgraded our memory limit with our hosting provider to 1GB and updated our wp-config.php file: define(‘WP_MEMORY_LIMIT’, ‘1000M’);
2. Added a migration step size to wp-config.php: define( EE_MIGRATION_STEP_SIZE, 10 );
3. We are still running into the same data migration error: <br /> <b>Fatal error</b>: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1749935 bytes) in <b>/home/lospob5/lospoblanos.com/wp-includes/functions.php</b> on line <b>384</b><br />

We have been quite patient regarding this update issue and will be requesting a full refund if this isn’t resolved.


Tony

  • Support Staff

January 6, 2017 at 2:03 am

Whilst we do understand your frustrated, the error shown is not coming from Event Espresso, its from your server.

1. Upgraded our memory limit with our hosting provider to 1GB and updated our wp-config.php file: define(‘WP_MEMORY_LIMIT’, ‘1000M’);

That does not actually do anything other than say ‘if the sever allows use, 1000M of available memory’, your server has 256MB available to it so that’s all it can use, which is why your still getting:

3. We are still running into the same data migration error:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1749935 bytes) in /home/lospob5/lospoblanos.com/wp-includes/functions.php on line 384

So Allowed memory size of 268435456 bytes exhausted is 256MB. Regardless of what setting you use for the above once the site gets to 256MB it will run out of memory, as that is all that is available.

This isn’t an error from Event Espresso, its from your server as EE is trying to run the migration and your server is running out of memory.

Did you try temporarily disabling the other plugins active on the site and then running the migration? Disabling other plugins will free up memory and should allow the migration to go through, you can then re-activate those other plugins.

I would also recommend creating a ticket with your hosting company asking why, if the site has 512MB available, is the PHP error showing only 256MB is available.


lospoblanos

January 6, 2017 at 6:17 pm

Our memory limit is 1024M:

http://www.lospoblanos.com/info.php

Our host confirmed our settings and we updated php.ini and phprc to reflect these values:

upload_max_filesize = 750M
post_max_size = 755M
max_execution_time = 15000
max_input_time = 15000
max_input_vars = 15000
memory_limit = 1024M

Also, we updated the memory limit value in wp-config.php to reflect 1024m.

The problem seems to be on your side.


Josh

  • Support Staff

January 6, 2017 at 8:43 pm

No, your server is throwing the out of memory errors, and Event Espresso does not set your server’s memory limits.

You can use the script included in this article to find out the actual memory limit:

https://magazine.joomla.org/issues/issue-dec-2010/item/295-Are-you-getting-your-fair-share-of-PHP-memory


lospoblanos

January 7, 2017 at 12:21 pm

Uploaded the script. Not sure how many lines are allowed on the script. If it’s only 99, then it doesn’t say much about typical memory limits (i.e. 512mb) but here are the results. No exhaustion errors:

You have allocated 1M (1267000) memory in this php script
You have allocated 2M (2315744) memory in this php script
You have allocated 3M (3364312) memory in this php script
You have allocated 4M (4412888) memory in this php script
You have allocated 5M (5461464) memory in this php script
You have allocated 6M (6510040) memory in this php script
You have allocated 7M (7558616) memory in this php script
You have allocated 8M (8607192) memory in this php script
You have allocated 9M (9655768) memory in this php script
You have allocated 10M (10704352) memory in this php script
You have allocated 11M (11752928) memory in this php script
You have allocated 12M (12801504) memory in this php script
You have allocated 13M (13850080) memory in this php script
You have allocated 14M (14898656) memory in this php script
You have allocated 15M (15947232) memory in this php script
You have allocated 16M (16995808) memory in this php script
You have allocated 17M (18044384) memory in this php script
You have allocated 18M (19092960) memory in this php script
You have allocated 19M (20141536) memory in this php script
You have allocated 20M (21190112) memory in this php script
You have allocated 21M (22238688) memory in this php script
You have allocated 22M (23287264) memory in this php script
You have allocated 23M (24335840) memory in this php script
You have allocated 24M (25384416) memory in this php script
You have allocated 25M (26432992) memory in this php script
You have allocated 26M (27481568) memory in this php script
You have allocated 27M (28530144) memory in this php script
You have allocated 28M (29578720) memory in this php script
You have allocated 29M (30627296) memory in this php script
You have allocated 30M (31675872) memory in this php script
You have allocated 31M (32724448) memory in this php script
You have allocated 32M (33773024) memory in this php script
You have allocated 33M (34821600) memory in this php script
You have allocated 34M (35870176) memory in this php script
You have allocated 35M (36918752) memory in this php script
You have allocated 36M (37967328) memory in this php script
You have allocated 37M (39015904) memory in this php script
You have allocated 38M (40064480) memory in this php script
You have allocated 39M (41113056) memory in this php script
You have allocated 40M (42161632) memory in this php script
You have allocated 41M (43210208) memory in this php script
You have allocated 42M (44258784) memory in this php script
You have allocated 43M (45307360) memory in this php script
You have allocated 44M (46355936) memory in this php script
You have allocated 45M (47404512) memory in this php script
You have allocated 46M (48453088) memory in this php script
You have allocated 47M (49501664) memory in this php script
You have allocated 48M (50550240) memory in this php script
You have allocated 49M (51598816) memory in this php script
You have allocated 50M (52647392) memory in this php script
You have allocated 51M (53695968) memory in this php script
You have allocated 52M (54744544) memory in this php script
You have allocated 53M (55793120) memory in this php script
You have allocated 54M (56841696) memory in this php script
You have allocated 55M (57890272) memory in this php script
You have allocated 56M (58938848) memory in this php script
You have allocated 57M (59987424) memory in this php script
You have allocated 58M (61036000) memory in this php script
You have allocated 59M (62084576) memory in this php script
You have allocated 60M (63133152) memory in this php script
You have allocated 61M (64181728) memory in this php script
You have allocated 62M (65230304) memory in this php script
You have allocated 63M (66278880) memory in this php script
You have allocated 64M (67327456) memory in this php script
You have allocated 65M (68376032) memory in this php script
You have allocated 66M (69424608) memory in this php script
You have allocated 67M (70473184) memory in this php script
You have allocated 68M (71521760) memory in this php script
You have allocated 69M (72570336) memory in this php script
You have allocated 70M (73618912) memory in this php script
You have allocated 71M (74667488) memory in this php script
You have allocated 72M (75716064) memory in this php script
You have allocated 73M (76764640) memory in this php script
You have allocated 74M (77813216) memory in this php script
You have allocated 75M (78861792) memory in this php script
You have allocated 76M (79910368) memory in this php script
You have allocated 77M (80958944) memory in this php script
You have allocated 78M (82007520) memory in this php script
You have allocated 79M (83056096) memory in this php script
You have allocated 80M (84104672) memory in this php script
You have allocated 81M (85153248) memory in this php script
You have allocated 82M (86201824) memory in this php script
You have allocated 83M (87250400) memory in this php script
You have allocated 84M (88298976) memory in this php script
You have allocated 85M (89347552) memory in this php script
You have allocated 86M (90396128) memory in this php script
You have allocated 87M (91444704) memory in this php script
You have allocated 88M (92493280) memory in this php script
You have allocated 89M (93541856) memory in this php script
You have allocated 90M (94590432) memory in this php script
You have allocated 91M (95639008) memory in this php script
You have allocated 92M (96687584) memory in this php script
You have allocated 93M (97736160) memory in this php script
You have allocated 94M (98784736) memory in this php script
You have allocated 95M (99833312) memory in this php script
You have allocated 96M (100881888) memory in this php script
You have allocated 97M (101930464) memory in this php script
You have allocated 98M (102979040) memory in this php script
You have allocated 99M (104027616) memory in this php script


Tony

  • Support Staff

January 9, 2017 at 4:22 am

We don’t need the full output, just whatever amount causes a memory exhausted error, that script stops at 99M due to this line:

for ($i=1; $i<100; $i++) {

Change $i<100; to $i<1025; to run the test for 1024MB.


lospoblanos

January 9, 2017 at 5:12 pm

Thanks for continuing to be responsive, we do appreciate it.

I edited and re-uploaded the php memory test script. We appear to have plenty of memory:


You have allocated 1023M (1072920960) memory in this php script

Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 1073741825 bytes) in /home/lospob5/lospoblanos.com/phpmemtest.php on line 15


Tony

  • Support Staff

January 10, 2017 at 6:43 am

Hmm in that case, yes you do have 1GB of memory available.

Something I didn’t think of is WP_MAX_MEMORY_LIMIT.

WP_MAX_MEMORY_LIMIT limits the available memory within the WP Admin, the ajax requested used during the migration run within the admin so will be subject to this limit.

Within your wp-config.php file add something like this:

define( 'WP_MAX_MEMORY_LIMIT', '512M' );

(Or a higher value if preferred)
Just below where you define WP_MEMORY_LIMIT.

If that doesn’t work we can investigate this further on your server.


lospoblanos

January 11, 2017 at 6:50 pm

Added the code to wp-config and reattempted update. Still receiving memory exhaustion message. <br /> <b>Fatal error</b>: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1749935 bytes) in <b>/home/lospob5/lospoblanos.com/wp-includes/functions.php</b> on line <b>384</b><br />


Josh

  • Support Staff

January 12, 2017 at 7:12 am

You’ll really need to ask your host to explain why you are still getting memory exhaustion messages. If your server really has that much memory, there’s no reason to continue getting that error.


lospoblanos

January 17, 2017 at 6:20 pm

Hi, we have already asked them. They are saying it’s an issue with your plugin. We are stuck in the middle.

We need to move forward with this. What options do we have for personalized tech support from you?


Josh

  • Support Staff

January 18, 2017 at 2:48 pm

I can recommend moving to another host. We don’t have control over your server’s settings, and it’s the server’s settings that’s the problem.


lospoblanos

January 24, 2017 at 7:59 pm

We’ve had the same hosting provider for years and have never experienced an issue like this before. Since your plugin is incompatible with our hosting provider and there are no disclaimers concerning this issue before purchasing the “EE4 Everything License,” we’d kindly request a full refund. Thank you.


Josh

  • Support Staff

January 25, 2017 at 8:04 am

You can request a refund by filling out this form:

https://eventespresso.com/refund-questionnaire/

Viewing 20 reply threads

The support post ‘Internal Service Error and Data Migration issues’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso