so read about installing the Memory Bump plugin here, but that didn’t work.
That’s no surprise. That plugin was built into WP core a few versions back. From the look of the initial error message, PHP memory was already set at 256M. Are you sure that you didn’t inadvertently introduce a problem in your php.ini?
I also thought it was odd that php.ini listed 128M initially, but that the error listed 256M…
The only thing I changed in php.ini was the memory_limit:
; Maximum amount of memory a script may consume (128MB)
; http://php.net/memory-limit
memory_limit = 512M
Full php.ini is here: http://pastebin.com/LQaeMuje
Changing the limit from 512M back to 256M gets rid of the seg-faults, but brings back the previous error message:
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 32 bytes) in /var/www/wp-includes/option.php on line 35, referer: https://my.domain.org/project/wp-admin/network/upgrade.php
Try deactivating as many plugins as you can for now. You’re only just over the memory limit, so that might be enough for you get the upgrade done.
No dice. I deactivated every plugin save for the SSL bypass that needs to run, & still got the same exhausted memory error.
Like I said, this is a totally fresh (so fresh, so clean) install….
Sorry – you may have to wait until someone with a little more apache+multisite-fu comes along. My multisite experience is very sparse. I’ll see if I can get some more eyes on this for you.
Appreciate it. Thanks for looking 🙂
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
It’s a long shot but depending on your setup your INI setting may not have taken effect.
Can you double check that by putting a <?php phpinfo(); ?> file on your WordPress installation and load that into your browser?
When I visit the one on my install I see this.
memory_limit 128M
Which is a lot BTW. 😉 Can you confirm what your setting say when you visit that file?
I just created it & checked it out. It’s consistent with what WP System Health is telling me: http://i.imgur.com/EkzJ8DW.png
& yeah, I know 128M is a bunch… should be more than sufficient.
I’m off for lunch shortly, so sorry if I don’t respond immediately for the next hour or so…
Some questions/comments from a colleague of mine who wrote the book (literally) on multisites…
How big a site are we talking?
In theory, you don’t actually have to run the db part of the upgrade, since visiting each site should do it on its own, but just on a wild shot, get the URL it’s failing on.
If it’s ending with a site number, increment that by one and see if it works. It may just be one site!
Thanks again for looking into it, esmi. As stated, I have no sub-sites yet, save for the initial one created during installation. It’s a fresh install.
Maybe I’ll create a couple of test sub-sites and see what happens…?
Forget trying to adjust memory size. That’s not going to solve the problem for you.
This error message:
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted
… indicates that the memory size is 256 meg. That’s fine and should be plenty.
The question isn’t how to increase the memory size, the question is what in the heck can be eating up 256 meg?
What URL are you getting this error on?
Here are the rest of the details of the error message:
Allowed memory size of 268435456 bytes exhausted (tried to allocate 32 bytes) in /path/to/root/wp-includes/option.php on line 35, referer: https://my.domain.org/project/wp-admin/network/upgrade.php
& other files w/diff lines are throwing the same error: link-template.php on line 1969 is another.
What is the URL in the browser when you get this error on the screen? Is it /network/upgrade.php?
