The stated above is on the official IPOWER server containing the database I want to upgrade. In the past, the conversion has worked perfectly fine converting to 3.0 and 3.1, now it doesn't. It keeps timing out on the first conversion step.
I run a copy of the old board database on my personal FatCow server for upgrade/style testing. FatCow apparently still runs MySQL 5.5.32. I believe IPOWER ran the same version before upgrading to 5.5.44. Doing the conversion to 3.1.9 works great on 5.5.32 without an issue and the converter loads to the first skip_rows page after hitting 'Continue conversion' within 30 seconds.
The PHP.INI for both IPOWER and FatCow servers are now identical and the issue persists so I am able to check that one off the list of causes. Both servers are running the default 5.3 config with the specified changes.
Code: Select all
memory_limit = 256M upload_max_filesize = 128M post_max_size = 256M max_input_time = -1 max_execution_time = -1 default_socket_timeout = -1
I've begun to wonder if the issue is caused by the database table type being MyISAM and collation being latin1_swedish_ci, BUT like I stated above, the conversion worked FINE before IPOWER upped to MySQL 5.5.44. I've also wondered if the conversion works fine on my FatCow server because the database was imported via BigDump in UTF-8. Both IPOWER and Fatcow phpMyAdmin show MySQL charset: UTF-8 Unicode (utf8) and MySQL connection collation: utf8_unicode_ci.
The only thing I haven't tried so far is exporting the old database and then re-importing it to a separate database on IPOWER via BigDump. If there is a language encoding issue causing the hiccup, that may or may not fix it. That said though, doing that would probably be my last effort at trying to get the conversion to work on MySQL 5.5.44. I'm just hesitant at using BigDump or anything risking a glitchy re-import.