Error in Step 17: 2.3.x -> 3.6.8 PL2

[KryptonSite]

I have a large database with almost 3 million posts, and after having run a test upgrade from 2.3.x to 3.6.8, I keep getting errors during the first 3.0.0 step:

Step 17) Update Posts to Support Threaded View ModeIt usually starts stalling around page 30 of 169 pages. After it stalls, it usually loads a blank white page. I then hit refresh and it usually tells me that I can't connect to the server (Firefox's generic error message). I refresh again and it seems to continue where it left off. It only happens 2-3 times during the 169 pages.

I had no issues with my test board after the upgrade though, so should I be looking for any problems? I attributed the error to the fact that my server load was a little high due to other activities, but just now today I got the error again when upgrading my live non-testing database. :mad:

I don't intend to use or allow threaded mode, so am I going to encounter any problems?

Thanks.

[Steve Machol]

This may be a server time and/or memory limit. To temporarily up your limits edit your includes/config.php file and add these lines right under the <?php line:

ini_set('memory_limit', -1);
ini_set("max_execution_time", "2440");

[KryptonSite]

That really wasn't my question... I just need to know now if it's going to be OK since there were errors during the upgrade. (There's no way to go back now)

I don't use threaded mode, and I don't plan on ever using it, so I'm not sure there could even be a problem. I ended up having to refresh the same page I was on, when the upgrade script stalled, so I don't think it skipped any threads or anything.

So, like I had asked, is there a way to tell if any of the threads didn't get converted in the database? AND, since I don't allow threaded mode could it even be a problem? It happened on maybe 3 different pages during the upgrade, so at most I would guess there is only a few that may not have been converted properly or skipped entirely.

[Steve Machol]

I cannot say for sure. Errors during the upgrade should never be ignored. The only thing you can do know is continue running your forums and hope you do not have any errors due to this.

[KryptonSite]

Well aren't there some steps in the upgrade that you guys KNOW are able to be refreshed when they stall? (And is that step one of them?)

If someone can answer this from a technical background (one of the developers) and not from customer support, I would appreciate it. (No offense intended, Steve. :))

OR, if I have to submit a support ticket for this I will. I just need to know if refreshing those steps when my server stalled could have affected the rows TWICE (or not at all). One of your developers should be able to tell me right away, by finding the script it runs for that step in the upgrade script. I imagine if these were "INSERT" commands to insert the proper threaded fields into the thread table that it wouldn't INSERT twice?

[Mez]

Steve is correct. You can never be sure. If there are any errors in your upgrade, you should restore a backup, and start over, as as we are not doing the upgrade, we cannot guarantee that this issue will not have caused problems.

Issues could arise from this, as while you do not intend to run in threaded mode, we have to take into account this information, and have to deal with it whether or not the feature is enabled (to allow for it to work if you enable it in the future). Having missing data can cause issues with your service, so it's better to be safe now, than have issues later.

In this instance, repeating a set of threads will not cause any harm, as the posts in the thread are updated to have their parent posts set as the first post in the thread, however, missing data COULD cause problems.

If you are having problems with your upgrade, please feel free to open a support ticket, where our trained Customer Support staff can help you, or you can request an upgrade to be performed on your behalf.