Problem upgrading to step 7 (3.6b1)

[rt-dubt]

Hi, hoping someone can help with a step in the upgrade process.

We have a fairly large forum database (10+GB), and currently in the process of upgrading to v3.6.5. Currently, we're stuck on step 7 of v3.6.0 beta 1. We're running into the memory_limit problem that other people have experienced.

In previous steps where I have seen this error, bypassing the PHP memory limit variable did the trick:

ini_set("memory_limit", -1);

However, for step 7, that bit of code doesn't seem to matter:

Step 7) Signature Permissions
Creating sigpic table
Altering usergroup Table (1 of 9)
Altering usergroup Table (2 of 9)
Altering usergroup Table (3 of 9)
Altering usergroup Table (4 of 9)
Altering usergroup Table (5 of 9)
Altering usergroup Table (6 of 9)
Altering usergroup Table (7 of 9)
Altering usergroup Table (8 of 9)
Altering usergroup Table (9 of 9)
Altering user Table (1 of 1)
Creating sigparsed table
Altering setting Table (1 of 1)
Renaming post_parsed table to postparsed
Updating Thread Redirects
Altering forum Table (1 of 3)
Altering forum Table (2 of 3)
Altering forum Table (3 of 3)
Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 1584686 bytes) in /wwwroot/vine2/includes/adminfunctions.php on line 3216

In going through the code I suspect it is trying to allocate too much memory either build_forum_genealogy() or when it attempts to rebuild the datastore build_datastore()

Any helps/hints/suggestions would be appreciated.

Thanks!

[Steve Machol]

That is a ridiculously low PHP memory limit. Your PHP does not have enough memory allocated to it to complete this operation. Ask your host to increase the 'memory_limit' variable in php.ini to at least 32M.

To temporarily up your limits edit your includes/config.php file and add these lines right under the <?php line:

ini_set('memory_limit', 32 * 1024 * 1024);

[rt-dubt]

Actually, I grabbed that bit of code from as a response from Colin F, of the vBulletin Team, in this thread:

http://www.vbulletin.com/forum/showthread.php?t=241174&highlight=memory_limit%2C+-1

Which, as it states, disables the memory limit in PHP.

Alternatively, I have tried incrementally bumping up the memory settings, upwards to a ridiculous amount of 10GB:

ini_set("memory_limit", "10000M");

and still get a memory error:

Fatal error: Allowed memory size of 1895825408 bytes exhausted (tried to allocate 226178714 bytes) in /wwwroot/vine2/includes/adminfunctions.php on line 3102

Finally, I have added, as you suggested to config.php:

ini_set('memory_limit', 32 * 1024 * 1024);

And the memory error I receive then is:

Fatal error: Out of memory (allocated -2088239104) (tried to allocate 263787991 bytes) in /wwwroot/vine2/includes/class_core.php on line 906

Any other possible things to try?

Thanks!

[Steve Machol]

There is something seriously wrong with that server if it requires that much memory.

For help with optimizing your server, please see this thread:

http://www.vbulletin.com/forum/showthread.php?threadid=70117

[rt-dubt]

Thanks for the link Steve.

I'm not sure if the server is unoptimized since it's just a dev box that our techops guys set up for our dev environment. It's basically a webserver that connects to another server that hosts the MySQL dbs, both are pretty clean outside of their designated functions.

I'll go through the thread you passed along and try to gather as much info as I can. Should I PM that info to you and/or eva2000?

[Steve Machol]

You need to post that info in the Server Configuration forum.