Announcement

Collapse
No announcement yet.

3.5.2 -> 5.5.6 upgrade issues

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Phoron
    replied
    Wayne,

    It looks like everything turned out ok after your last advice, solved the most recent impasse.

    I really appreciate the level of suport that you and your team delivered here. Two thumbs up.... Thanks!

    Leave a comment:


  • Wayne Luke
    replied
    The two issues are not related.

    The first is a MySQL issue. It closed the connection before returning the results of the query. Make sure your max_allowed_packet is at least 8 MB and that the wait_timeout and innodb_lock_wait_timeout values are at least 120 seconds. The 5.5.4 Alpha 4 steps are increasing the length of the IP Address fields throughout the database to accommodate IPv6. You may need to increase temp storage so that it is at least 3 times the largest table by size in the database. This is needed for temporary tables in adding fields and rebuilding indexes. The node table is probably the largest table in the database for this operation. Unfortunately, changing the size of the field can't be batched to only change a number of rows at one time.

    The second is a PHP Warning from the 5.0.0 Alpha 28 Step 6. That step would have been updating the postedithistory table. There would have been 100s of intervening steps and database modifications since this occurred and MySQL timed out. There are 154 versions of vBulletin between 5.0.0 Alpha 28 and 5.5.4 Alpha 4.

    Leave a comment:


  • Phoron
    replied
    Thanks for the patched files, Wayne. I installed them as required, mounted the same database iteration the dev grabbed, then ran the upgrader thru CLI.

    We got to 5.5.4 alpha 4 step 3 when it threw an error

    Code:
    Upgrading to 5.5.4 Alpha 4
    ----------------------------------
    Step 1 - Dropping Old picturecomment Table
    Step 2 - Dropping Old picturecomment_hash Table
    Step 3 - Altering node Table (1 of 1)
    
    
    
    MySQL server has gone away
    ----------------------------------
    
    ### vBulletin Database Alter ###
    ALTER TABLE node
    MODIFY ipaddress VARCHAR(45) NOT NULL DEFAULT ''
    Error_log in core folder:

    Code:
    [02-Mar-2020 17:24:22 America/Boise] Warning: Invalid argument supplied for foreach() in /xxx/core/install/includes/class_upgrade_500a28.php on line 142

    Leave a comment:


  • Phoron
    replied
    Originally posted by Wayne Luke View Post
    The problem with these steps is that they are old and haven't been looked at in a long time. My guess is that you're using something higher than PHP 7.1 and that is causing all the errors. I have a developer willing to work through all the issues and fix as necessary to get to the 5.X series of steps. However, to do that he needs a copy of the database that you're working to upgrade.

    If you can make the database available to us or provide access to the servers, please let us know how to proceed.

    The alternative is to downgrade to PHP 7.1 until you've upgraded to 4.2.5 and then change back to the newer version of PHP to continue the upgrade.
    Thanks Wayne... I set us to run on PHP 7.1 but the upgrader keeps on throwing the same error. I will PM you the logon info a little later on today.

    Leave a comment:


  • Wayne Luke
    replied
    The problem with these steps is that they are old and haven't been looked at in a long time. My guess is that you're using something higher than PHP 7.1 and that is causing all the errors. I have a developer willing to work through all the issues and fix as necessary to get to the 5.X series of steps. However, to do that he needs a copy of the database that you're working to upgrade.

    If you can make the database available to us or provide access to the servers, please let us know how to proceed.

    The alternative is to downgrade to PHP 7.1 until you've upgraded to 4.2.5 and then change back to the newer version of PHP to continue the upgrade.

    Leave a comment:


  • Phoron
    replied
    Replaced file and ran upgrade from browser window as per post 9 on this thread

    We got another error a little further down the line this time

    Code:
    An error has occurred with your database. Please contact vBulletin Support for assistance.
    Module: 370b6, Step 11 Database Error:1064
    You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 65536, 0)' at line 3
    Query:
    
    UPDATE moderator SET permissions2 = permissions2 | IF(permissions & , 65536, 0)
    
    Script: 370b6
    Step: 11


    Leave a comment:


  • Wayne Luke
    replied
    Replace the file in the /core/install/includes directory with the one below.
    Attached Files

    Leave a comment:


  • Wayne Luke
    replied
    I think this can be patched. Let me see if I can get the files.

    Leave a comment:


  • Phoron
    replied
    Originally posted by Wayne Luke View Post
    Can you try running the upgrader from the browser address bar using this command?

    upgrade.php?version=370b4&step=2
    Yes... it did this:


    Code:
    An error has occurred with your database. Please contact vBulletin Support for assistance.
    Module: 370b4, Step 15 Database Error:1064
    You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 0) | IF(permissions & 2, , 0) | IF(permissions & 131072, , 0) | ' at line 4
    Query:
    
    UPDATE moderator SET permissions2 = permissions2 | IF(permissions & 1, , 0) | IF(permissions & 2, , 0) | IF(permissions & 131072, , 0) | IF(permissions & 64, , 0)
    
    Script: 370b4
    Step: 15

    Leave a comment:


  • Wayne Luke
    replied
    Can you try running the upgrader from the browser address bar using this command?

    upgrade.php?version=370b4&step=2

    Leave a comment:


  • Phoron
    replied
    Originally posted by Wayne Luke View Post
    have no idea. What did the hosting provider say about the error: Resource Temporarily Unavailable?
    For some reason I am no longer getting that particular error.

    There is an error log being generated in the core folder whenever I attempt to run upgrade.php

    Error log reads:

    [21-Feb-2020 01:00:12 UTC] PHP Fatal error: The core/includes/xml/bitfield_vbulletin.xml file is out of date. Please ensure you have uploaded the correct file.
    in /home1/xxxxx/public_html/forum2/core/install/includes/class_upgrade_cli.php on line 384

    md5 checksum of my bitfield_vbulletin.xml

    b12134a75c7f254be2563927f07b226a

    I have deleted the old files, then reuploaded all the required folders and files from vbulletin 5.5.6, but when I attempt to run upgrade.php, I still wind up with an open prompt and the aforementioned error log that's generated as a result...
    Last edited by Phoron; Thu 20 Feb '20, 5:23pm.

    Leave a comment:


  • Wayne Luke
    replied
    have no idea. What did the hosting provider say about the error: Resource Temporarily Unavailable?

    Leave a comment:


  • Phoron
    replied
    My upgrade is stalled out. I have tried running the upgrade script several times again from the command line but wind up with an open command prompt

    screenshot:
    https://i.postimg.cc/HnvhTL7z/Clipboard04.jpg

    Any idea whats going on here?

    Leave a comment:


  • Phoron
    replied
    Originally posted by Wayne Luke View Post
    Run this query against the database:

    Code:
    DELETE r1 FROM reputation r1
    INNER JOIN reputation r2
    WHERE r1.reputationid < r2.reputationid
    AND r1.whoadded = r2.whoadded
    AND r1.postid = r2.postid;
    If you have a table prefix defined, you'll need to add it to the two instances of reputation in the query.
    Cool, that seemed to work. I dont think I have a prefix for that table.

    I am a noob when it comes to sql so I appreciate your forbearance

    Here's where I'm at now

    https://postimg.cc/v1V2Zq5B

    When it comes to 3.7 beta 4, I just get an open prompt and nothing


    Leave a comment:


  • Wayne Luke
    replied
    Run this query against the database:

    Code:
    DELETE r1 FROM reputation r1
      INNER JOIN reputation r2
    WHERE r1.reputationid < r2.reputationid
    AND   r1.whoadded = r2.whoadded
    AND   r1.postid  = r2.postid;
    If you have a table prefix defined, you'll need to add it to the two instances of reputation in the query.

    Leave a comment:

Related Topics

Collapse

Working...
X