Upgrade from 4.2.1 to 4.2.3 questions

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tandeejay
    New Member
    • Apr 2016
    • 7
    • 4.2.x

    Upgrade from 4.2.1 to 4.2.3 questions

    Hi,

    I've recently taken on the role of administrator for a vb forum which is currently on v4.2.1

    Just recently, there was a security problem with another site hosted on the same server (not a vbulletin site), and the mitigation actions to fix the other site included upgrading some of the underlying products.

    Along with all the updates, MySQL was updated from 5.1 to MariaDB 10.

    Unfortunately, this broke the forum, as PHP 5.3 does not seem to support MariaDB10, and unfortunately no supported way to roll back to MySQL (cPanel doesn't provide an option to install the earlier version once you've upgraded )

    I was able to get the forum back up and running by upgrading PHP to 5.4 which does support MariaDB10, but there are issues with VB4.2.1 on PHP 5.4,

    So, I'm biting the bullet, and upgrading vbulletin to 4.2.3.


    As I've been reading through documentation about performing the upgrade, I see lots of comments about "test test test"... so just trying to come up with a valid method of testing.

    From what I can work out, for testing I need to dump the database, and import it into a new database with a command something like this:

    mysqldump --opt -Q -u dbusername -p databasename > /path/to/backupname.sql
    mysql -u dbusername -p test_databasename < /path/to/backupname.sql

    and make a full copy of the public_html folder to test in, and update the includes/config.php file in the test to point to the test database, that is, change the lines:

    $config['Database']['dbname'] = 'databasename';

    $config['Misc']['forumpath'] = '/path/to/forum/public_html'

    to :

    $config['Database']['dbname'] = 'test_databasename';

    $config['Misc']['forumpath'] = '/path/to/forum/public_html_test'


    And then run the update process from the test location

    My guess is that this location should be web accessible so that I can test the copy after the upgrade to make sure there were no issues. So, do I need to set up a new domain name to point at this test, or can I locate the test somewhere like /path/to/forum/public_html/testforum (given that the path to the current forum is /path/to/forum/public_html


    (Apparently someone had a go at updating the forum to 4.2.3 a while back, but they got errors and never followed up how to resolve those errors. My hope is that I can either get the correct procedure sorted so that the upgrade goes smoothly, or to get assistance from this forum for any errors that do occur. Hence why I'm wanting to test the update process thoroughly)


    current product versions:
    PHP 5.4.45
    vBulletin 4.2.1
    MySQL 10.0.27-MariaDB

    (Upgrading PHP version to 5.5 or 5.6 is potentially on the cards after this vbulletin upgrade is successfull.)

    All pointers/tips/help much appreciated



    Regards,
    John.
  • wda2015
    Senior Member
    • May 2001
    • 1135

    #2
    Personally I would risk it on the live site, backup the database & files from cPanel run the upgrade script and if it fails note the errors and put the old database & files back.
    Simple Straight Forward EU cPanel vBulletin Web Hosting Provider.

    Comment

    • tandeejay
      New Member
      • Apr 2016
      • 7
      • 4.2.x

      #3
      I've been a unix admin for the past 20 years, and kind of used to the command line only been admin of this VB site for some months... I'll have a dig through cpanel to check out its backup options.

      Comment

      • tandeejay
        New Member
        • Apr 2016
        • 7
        • 4.2.x

        #4
        Hmmm I'm not familiar with cPanel or how it's backup functions work. much more comfortable doing a backup from commandline...

        Something like:
        cp -a public_html public_htmm_421
        mysqldump --opt -Q -u myforum -p myforum > /backup/upgrade/myforumbackup.sql


        Then if restore required:
        mv public_html public_html_423
        mv public_html_421 public_html
        mysql -u myforum -p myforum < /backup/upgrade/myforumbackup.sql


        (of course with all the required closing of the forum...)

        If my steps above are flawed, and I'd be better off using cPanel, let me know.

        Comment

        • tandeejay
          New Member
          • Apr 2016
          • 7
          • 4.2.x

          #5
          Originally posted by wda2015
          Personally I would risk it on the live site, backup the database & files from cPanel run the upgrade script and if it fails note the errors and put the old database & files back.
          Happy with by backout plan...

          so I attempted to run the upgrade and got this:

          Comment

          • tandeejay
            New Member
            • Apr 2016
            • 7
            • 4.2.x

            #6
            Upgrading to 4.2.2 Alpha 1
            Upgrading to 4.2.2 Beta 1
            Upgrading to 4.2.2
            Upgrading to 4.2.3 Alpha 1
            Upgrading to 4.2.3 Beta 1
            Upgrading to 4.2.3 Beta 2
            Upgrading to 4.2.3 Beta 3
            Upgrading to 4.2.3 Beta 4
            Step 1 - Altering postlog Table (1 of 1)
            Step 2 - Altering session Table (1 of 2)
            Step 3 - Altering session Table (2 of 2)
            Upgrading to 4.2.3 Release Candidate 1
            Upgrading to 4.2.3
            Step 1 - Updating filedata table (1 of 1)
            Processing Blog
            An error has occurred. Please contact vBulletin Support for assistance.

            Module: vbblog, Step 1 Error.

            Mismatch between product version 4.2.1 and vBulletin version 4.2.3

            Were all of the files for this release uploaded?

            Comment

            • tandeejay
              New Member
              • Apr 2016
              • 7
              • 4.2.x

              #7
              my rollback plan worked..

              Ok, so what is the next step I need to follow to get this upgrade to work?

              Comment

              • Mark.B
                vBulletin Support
                • Feb 2004
                • 24287
                • 6.0.X

                #8
                What happens if you try to run the upgrade via the web interface?
                MARK.B
                vBulletin Support
                ------------
                My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
                My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

                Comment

                • tandeejay
                  New Member
                  • Apr 2016
                  • 7
                  • 4.2.x

                  #9
                  I had to run the upgrade via the web interface, as running via the commandline directly, just output the html code for the web page that asks for the member number. The output I pasted here came directly from the web page output popup.

                  I raised a support ticket with vBulletin support, and they said:
                  Hello,

                  This can happen when you try to upgrade a VB4 Publishing Suite with a VB4 Forum Only software package.

                  As you have both a VB4 Publishing Suite license and a VB4 Forum Only license it is likely this is the issue.

                  Make sure you download the right version upgrading.

                  Please let me know if you require any further assistance.

                  - Joe D.
                  vBulletin Support Staff

                  So I tried downloading the VB4 Publishing Suite update package, and it worked perfectly!

                  Thankyou everyone for your support.

                  Regards
                  John (now one not quite so green vB administrator...)

                  Comment

                  Related Topics

                  Collapse

                  Working...