SOLVED - SMF 1.1.8 > SMF 2.0 RC1 Upgrade Error Server Not Responded 30 Seconds

Started by FidelGonzales, March 06, 2009, 12:47:24 PM

Previous topic - Next topic

FidelGonzales

I have been having difficulty upgrading from SMF 1.1.8 to SMF 2.0 RC1.

I began the attempt to upgrade using every version from 1.1.4, which was what my site was using. Since 1.1.4 and all other versions were not successfully upgrading, I figured it would be best to use the latest version, 1.1.8, which is where I am at now.

The interesting thing about this is that several months back, I cloned this install of SMF to a GoDaddy Shared Linux Server account and have since upgraded that to SMF 2.0 RC1 with ease. This SMF install, which was the original of that clone, resides on a HostGator Dedicated Linux Server, where the PHP configuration has been set at some high limits so as to eliminate any issues that could be related to any PHP configuration limitations that I am aware of.

The problem I have having occurs immediately into the upgrade process, when I receive this error (SCREEN SHOTS ATTACHED).

QuoteSMF Executing upgrade script 1 of 2. Executing: "Updating and creating indexes..." (1 of 19 - of this script).

QuoteError!
Server has not responded for 30 seconds. It may be worth waiting a little longer or otherwise please click here to try this step again

Amid the threads I have monitored and solutions I have tried in attempt to overcome this error, is one within the thread that notes a similar issue, where I have also posted. I started this here thread, since it may be a separate issue and the thread, which is linked below, is also noted as solved.

http://www.simplemachines.org/community/index.php?topic=257751.0

Specifically, the solution I have tried is listed below, originally posted by khamseen. I have only gone as far as step 8 in this proposed solution. Prior to and after this, I also attempted other methods, which were similar but produced the same result.




http://www.simplemachines.org/community/index.php?topic=257751.msg1786070#msg1786070

QuoteThe Steps;

1. Create a back up of the SQL database via phpMYAdmin.

2. Delete the SMF 1.1.x install from the server (leave things like download folders, avatars or anything else you might want again.)

3. Upload the SMF 2.0 Beta Full Install files and run them via www.yourdomain.com/install.php

4. After running the install upload the repair_settings.php file and run it to make sure all directory paths are correct.

5. Open up phpMyadmin again and then delete ALL database tables.

6. Whilst still in phpMyAdmin upload your backup of the SQL database from your 1.1.x install.

7. From the SMF 2.0 Large Upgrade, upload "upgrade.php" along with the 5 "upgrade_*.php" files to the root directory of your server.

8. Run the upgrade via www.yourdomain.com/upgrade.php do not worry about creating database table backups at this point as you already have them. Simply have it repair and update table information.

9. Once the upgrade completes run the repair_settings.php again and turn off maintenance mode. **SECURITY RISK - DELETE THIS FILE AT THIS STAGE**

10. You should now have the forums up and running using 2.0 Beta 4 and all boards, topics and posts should be as they were along with any account details or member data. If you have kept your avatar folders for local storage they should not be affected either.




My most recent attempt, with all mods removed, I performed all maintenance procedures, such as repairing database, optimizing database and the like. It still dies on the same step. During upgrade and prior to producing this error, I can click away on all database-driven sites on server, and they work fine. If need be, I can submit database and/or files for review or simply provide access.

Thank you.




PHP CONFIGURATION - Screen Shot Also Attached

Sub Section     Directive     Info     Value
Language Options    asp_tags    Allow ASP-style <% %> tags.    Off
File Uploads    file_uploads    Whether to allow HTTP file uploads.    On
Paths and Directories    include_path    Windows: "\path1;\path2"    .:/usr/lib/php:/usr/local/lib/php
Resource Limits    max_execution_time       640
Resource Limits    max_input_time       640
Resource Limits    memory_limit       640M
Data Handling    register_globals    You should do your best to write your scripts so that they do not require register_globals to be on; Using form variables as globals can easily lead to possible security problems, if the code is not very well thought of.    Off
Language Options    safe_mode       Off
main    session.save_path    where N is an integer. Instead of storing all the session files in /path, what this will do is use subdirectories N-levels deep, and store the session data in those directories. This is useful if you or your OS have problems with lots of files in one directory, and is a more efficient layout for servers that handle lots of sessions. NOTE 1: PHP will not create this directory structure automatically. You can use the script in the ext/session dir for that purpose. NOTE 2: See the section on garbage collection below if you choose to use subdirectories for session storage    N;/path
File Uploads    upload_max_filesize    Maximum allowed size for uploaded files.    10M
main    zend_optimizer.version       3.3.0

FidelGonzales

This error has got to be due to error in database, even though all repair, optimization and maintenance procedures prior to upgrade check out good.

Is there a way to check where in the database upgrade process the error is produced?

Also, is it possible that issue is due to a bad character within a user name? I had this issue recently with the upgrade of another script. Are there any common characters I ought to look for specifically?

FidelGonzales

I recently eliminated all apparent spam accounts containing the following phrases in the email addresses or user names.

QuoteFREE SEX SOFTWARE HEALTH MED .INFO VIAGRA

I am now going to perform the suggestions here in this forum and attempt another upgrade. Will report back.

QuoteI just changed the options a little before the upgrade stage (unchecked the maintenance and checked the next two boxes below it). It seems to work after that.

http://www.simplemachines.org/community/index.php?topic=272413.msg1902342#msg1902342

FidelGonzales

No. This only produced the same errors. This install is on a dedicated server, but I am going to reload it first on a GoDaddy shared account, where I have the clone that upgraded without issue. I will report back thereafter.

FidelGonzales

Wow!!! AMAZING!!!

I moved all files and the database from a HostGator dedicated server to a GoDaddy shared server, and the upgrade from Simple Machines Forum 1.1.8 to SMF 2.0 RC1 went smooth in as little as five minutes. And that's after over a month of trying to migrate it on HG.

Anyone else have this issue and does not have access to a upgrade that is functional, let me know, and I will help by temporarily providing the platform.

Thanks.

Advertisement: