Import page stuck "loading" after porting post

[Ken Iovino]

I just ported over 3 million post from phpbb to vb. Everything worked fine, but when I try to go into the import section in the admincp to take the next step, the page just sits forever with my browser saying "loading...", and after about 10 mins it will say done and show only a white page. I've noticed this issue each time I ran a test post and I had to wait about 1-2 hours in order to get back into the import section.

Any idea why this is happening?

Edit Note #1: Every other loads fast and perfectly fine. The import page is the only problem I'm having this with.
Edit Note #2: I just logout of the control panel and log back in. I clicked on the import link and it asked me my customer number. I entered it in and it say it was entered in correctly, then redirected me back to this loading/whitepage of death.

[Ken Iovino]

Okay, so here is what I did in order to get it to work. Hopefully this won't mess anything up but I had no choice. The site has been down for 10 hours and my users are getting very antsy.

I purposely manipulated a query in the code to see if it would display an error and it did. So, that tells me that there is something going on with the vbfields table. I emptied that tables data and tricked file 011.php to think he didn't have any dependents since I already ran the users import. Once I did that the file started to actually display. Then I started to import the PMs since this is the only thing I have left to do. Whether or not this is going to cause a problem with userids, I'm not sure. After examining the all "my" PMs in the database using my new userid, it looks like its working just fine because all my PMs are showing up with the correct information.

I know this isn't recommend normally, but I couldn't afford to run a second port and I was willing to take the risk. For anyone else with this problem, I wouldn't really attempt this unless you really know what your doing.

[Jerry]

Okay, so here is what I did in order to get it to work. Hopefully this won't mess anything up but I had no choice. The site has been down for 10 hours and my users are getting very antsy.

The first and most important bit of information in the HOWTO and the manual is to test an import in isolation while leaving the source open.

Closing the source board to do an import is a recipe for disaster usually.

I purposely manipulated a query in the code to see if it would display an error and it did. So, that tells me that there is something going on with the vbfields table. I emptied that tables data and tricked file 011.php to think he didn't have any dependents since I already ran the users import. Once I did that the file started to actually display. Then I started to import the PMs since this is the only thing I have left to do. Whether or not this is going to cause a problem with userids, I'm not sure. After examining the all "my" PMs in the database using my new userid, it looks like its working just fine because all my PMs are showing up with the correct information.

I know this isn't recommend normally, but I couldn't afford to run a second port and I was willing to take the risk. For anyone else with this problem, I wouldn't really attempt this unless you really know what your doing.

I wouldn't advise anyone to hack an importer, I would advise them to run a test and respond with the results so they can be worked on before the planned live cut over.

What would of been happening with your import, is the final page of the post module updates the parent ids of the posts that it couldn't do during the import. That would of been timing out, and could of just been commented out.

[Ken Iovino]

The first and most important bit of information in the HOWTO and the manual is to test an import in isolation while leaving the source open.

Closing the source board to do an import is a recipe for disaster usually.



I wouldn't advise anyone to hack an importer, I would advise them to run a test and respond with the results so they can be worked on before the planned live cut over.

What would of been happening with your import, is the final page of the post module updates the parent ids of the posts that it couldn't do during the import. That would of been timing out, and could of just been commented out.

I've tested the port 3 times and everything worked aside from that white page issue. I don't understand what you mean "Closing the source board to do an import is a recipe for disaster usually." What I did was close the source board so no more data can get inserted into the database. I then backed up that database and placed the back up on my second web server and installed vbulletin on it. So it looks like this:

Web Server 1: original_phpbb_database
Web Server 2: backup_phpbb_database, vbulletin_database

I then began the merger using "backup_phpbb_database" and "vbulletin_database". Are you suggesting that I keep my phpbb board open for the members while I'm running the port?

One more thing. The post module was indeed finished. So, in theory when I ran the PM module I should be okay right? Everything looks okay and seems to have been ported just fine. I just don't want to have to start all over again, but if you think I should I will.

[Jerry]

I've tested the port 3 times and everything worked aside from that white page issue. I don't understand what you mean

I mean that if you had posted after the testing and pointed this out I could of helped you then opposed to now, just would of made your import go smoother and quicker that's all.

One more thing. The post module was indeed finished. So, in theory when I ran the PM module I should be okay right? Everything looks okay and seems to have been ported just fine. I just don't want to have to start all over again, but if you think I should I will.

99% sure it would of timed out on the update parent id's, so in theory changing the dependency so you could run the PM module would be fine. The usual clean up steps will take care of the rest of it.

[Ken Iovino]

Thank you Jerry, hopefully I won't have to do this again. So long as we don't buy anymore phpbb boards. If so, I will seek your advise before running another port. :)

[Jerry]

Thank you Jerry, hopefully I won't have to do this again. So long as we don't buy anymore phpbb boards. If so, I will seek your advise before running another port. :)

I'd much rather help during the testing phase and tune things just right, opposed to having a "My board is down, users are waiting, help" kind of post :)

Though looks like it's all well now :D