error trying to update to version 3

goodguy100 · 2020-04-30 17:27:13

After clicking on UPDATE ALL, I get the following error

Unexpected error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 16493028 bytes) in Poster.php on line 111

Ben · 2020-04-30 18:02:03

It looks like your PHP setup has a maximum memory limit of 32 MB, which is very low. The zip file that's extracted during upgrade is 16 MB, so it's easy to see that reading that file and extracting it will exceed the memory limit.

Can you increase the memory_limit setting in PHP? A more reasonable value is 128M. How you do this will depend on your host. Possibly via the site's control panel.

SunFoxNC · 2020-04-30 22:53:04

FYI, The PHP memory_limit setting also bit me when I kicked off the upgrade (I made it to line 117 but the gist of the message was the same).

For Backlight users that are on a virtual private server (VPS) rather than shared hosting (Bluehost, HostGator, et al), you might have to fix the PHP memory_limit directive in a slightly different fashion. What follows worked on my VPS at inMotion...your VPS vendor may have a different set of tools available to you for managing the VPS.

Whilst debugging this on my server, I discovered that PHP 7.3 was ignoring the local php.ini files in the home directory and webserver root that the CPANEL php.ini editor can edit in favour of the default php.ini in the server-wide PHP installation directory.

Seeing that I'm on a VPS and don't mind kicking those settings up for every site I host on that server and can do so safely without wrecking anyone else on that physical box, I got round the error by going ahead and editing that base php.ini file using the php.ini editor available in Web Host Manager (WHM) as root.

Then it was back to Backlight's module screen and it was clear sailing for the upgrade! Woo hoo! I've got to admit to being rather spoilt by the Backlight 2+ update screens/processes compared to the old "copy all of this stuff hither and yon and fiddle with these things and for goodness sake don't trash the data directory and really ruin your day" README procedures from the CE3/CE4 days...

Ben · 2020-04-30 23:02:09

Thanks for sharing your experience and and advice. We also appreciate not having to support the old way of dong things, and the myriad of ways that things could go wrong.

oceanman22 · 2020-04-30 23:13:13

I had the same problem and had to go to my host site and found the PHP setting under CGI and somehow found it and changed it to 128M and then retried the update and it updated perfectly.

Question !! Should I go back and change the PHP memory back to 64M or leave it as is ?

Thanks,
Jim

goodguy100 · 2020-04-30 23:26:18

Thank You moving PHP to 128M resolved the issue

Ben · 2020-05-01 07:22:09

oceanman22 wrote:

Question !! Should I go back and change the PHP memory back to 64M or leave it as is ?

There shouldn't be any harm in leaving it at 128M. That's usually what I set my web servers at.

mikepio · 2020-05-01 08:23:51

Thanks for your help. Increasing PHP memory limit to 128M corrected the error.

Community @ The Turning Gate

#1 2020-04-30 17:27:13

error trying to update to version 3

#2 2020-04-30 18:02:03

Re: error trying to update to version 3

#3 2020-04-30 22:53:04

Re: error trying to update to version 3

#4 2020-04-30 23:02:09

Re: error trying to update to version 3

#5 2020-04-30 23:13:13

Re: error trying to update to version 3

#6 2020-04-30 23:26:18

Re: error trying to update to version 3

#7 2020-05-01 07:22:09

Re: error trying to update to version 3

#8 2020-05-01 08:23:51

Re: error trying to update to version 3

Board footer