Announcement

Collapse
No announcement yet.

URGENT - Upgrade problem from 4.1.1 to 4.1.4

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

  • [Forum] URGENT - Upgrade problem from 4.1.1 to 4.1.4

    was upgrading from 4.1.1 to 4.1.4 Patch level 1

    --------------

    * 4.1.4
    * 4.1.4
    * 4.1.4
    * 4.1.4

    * vbulletin-style.xml:
    * vbulletin-settings.xml:
    * vbulletin-language.xml:
    * vbulletin-adminhelp.xml:

    vBulletin 4.1.4 Upgrade System
    (Please be patient as some parts may take some time)
    Startup Errors
    Due to the following errors, the install/upgrade can not continue:

    *

    Please Enter Your Customer Number
    This is the number with which you log in to the vBulletin.com Members' Area
    Version Mismatch
    Your upgrade log shows that your last upgrade was to version 4.1.1 but you are currently on version 4.1.1.
    Upgrade from 4.1.1 Upgrade from 4.1.1
    Upgrading to 4.1.4
    Status: Aborted
    44%

    Press the button below to begin the upgrade
    from 4.1.1 to 4.1.4
    Upgrade Progress

    * Upgrading to 4.1.1
    * Upgrading to 4.1.2 Beta 1
    * Upgrading to 4.1.2
    * Upgrading to 4.1.3 Beta 1
    * Step 1 - Creating index email on user
    * Upgrading to 4.1.3
    * Upgrading to 4.1.4 Beta 1
    * Step 1 - Altering language Table (1 of 2)
    * Step 2 - Altering language Table (2 of 2)
    * Step 3 - Altering phrase Table (1 of 2)
    * Step 4 - Altering phrase Table (2 of 2)
    * Step 5 - Updating phrasetype table
    * Step 6 - Creating autosave table

    Status: Aborted
    Action Required
    Action Required
    Unexpected Text:

    <?xml version="1.0" encoding="windows-1252"?>
    <?xml version="1.0" encoding="windows-1252"?>
    <errors>
    <error><![CDATA[<p>Database Error</p>

    Invalid SQL:

    SELECT contenttypeid
    FROM contenttype
    WHERE
    packageid = 1
    AND
    class = 'PrivateMessage';

    Incorrect information in file: './tellytv_zee/contenttype.frm']]></error>
    <error_html><![CDATA[<p>Database error in vBulletin 4.1.3</p>
    <p>Invalid SQL:

    SELECT contenttypeid
    FROM contenttype
    WHERE
    packageid = 1
    AND
    class = 'PrivateMessage';<p>
    <p>
    <strong>MySQL Error</strong> : Incorrect information in file: './tellytv_zee/contenttype.frm'<br />
    <strong>Error Number</strong> : 1033<br />
    <strong>Request Date</strong> : Monday, July 18th 2011 @ 02:20:50 PM<br />
    <strong>Error Date</strong> : Monday, July 18th 2011 @ 02:20:50 PM<br />
    <strong>Script</strong> : http://telly-tv.com/install/upgrade.php<br />
    <strong>Referrer</strong> : http://telly-tv.com/install/upgrade.php<br />
    <strong>Classname</strong> : vB_Database<br />
    <strong>MySQL Version</strong> : 5.0.92-community-log<br />
    </p>]]></error_html>
    </errors>

    vBulletin v4.1.1, Copyright ©, 2011 vBulletin Solutions, Inc. All rights reserved.

  • #2
    you did turn off all plugins board and hooks

    Comment


    • #3
      Turning off his plugins has no impact on the above error message. Your contenttype table is crashed and needs to be repaired. However it may not be able to be repaired. Do you have a backup of the database with that table in it?

      Comment


      • #4
        Originally posted by Krishan View Post
        <strong>MySQL Error</strong> : Incorrect information in file: './tellytv_zee/contenttype.frm'<br />
        <strong>Error Number</strong> : 1033<br />
        <strong>Request Date</strong> : Monday, July 18th 2011 @ 02:20:50 PM<br />
        that's possible corruption of contenttype table's definition file

        do you have server root user ssh2 telnet access ?

        1. Determine if contenttype is MyISAM or InnoDB storage engine based. Type this command when prompted for your mysqlusername's password enter it to proceed

        in ssh2 telnet type

        Code:
        mysql -u mysqlrootusername -p -e "select round(sum(innodb_data_size + innodb_index_size) / (innodb_data_free + sum(innodb_data_size + innodb_index_size))) * 100  as 'innodb_tablespace_utilization_perc'
        , (data_size + index_size) / gb as total_size_gb
        , index_size / gb as index_size_gb
        , data_size / gb as data_size_gb
        , sum(innodb_index_size + innodb_data_size) / pow(1024,3) as innodb_total_size_gb
        , innodb_data_size / pow(1024,3) as innodb_data_size_gb
        , innodb_index_size / pow(1024,3) as innodb_index_size_gb
        , sum(myisam_index_size + myisam_data_size) / pow(1024,3) as myisam_total_size_gb
        , myisam_data_size / pow(1024,3) as myisam_data_size_gb
        , myisam_index_size / pow(1024,3) as myisam_index_size_gb
        , index_size / (data_size + index_size) * 100 as perc_index
        , data_size / (data_size + index_size) * 100 as perc_data
        , innodb_index_size / (innodb_data_size + innodb_index_size) * 100 as innodb_perc_index
        , innodb_data_size / (innodb_data_size + innodb_index_size) * 100 as innodb_perc_data
        , myisam_index_size / (myisam_data_size + myisam_index_size) * 100 as myisam_perc_index
        , myisam_data_size / (myisam_data_size + myisam_index_size) * 100 as myisam_perc_data
        , innodb_index_size / index_size * 100 as innodb_perc_total_index
        , innodb_data_size / data_size * 100 as innodb_perc_total_data
        , myisam_index_size / index_size * 100 as myisam_perc_total_index
        , myisam_data_size / data_size * 100 as myisam_perc_total_data
        from ( select sum(data_length) data_size,
        	sum(index_length) index_size,
        	sum(if(engine = 'innodb', data_length, 0)) as innodb_data_size,
        	sum(if(engine = 'innodb', index_length, 0)) as innodb_index_size,
        	sum(if(engine = 'myisam', data_length, 0)) as myisam_data_size,
        	sum(if(engine = 'myisam', index_length, 0)) as myisam_index_size,
        	sum(if(engine = 'innodb', data_free, 0)) as innodb_data_free,
        	pow(1024, 3) gb from information_schema.tables )
        a\G
        post output here in [CODE][/CODE] tags

        2. Did you recently make any /etc/my.cnf mysql settings changes prior to upgrade ? If you have root user access, check the last 100 lines of your mysql error log usually /var/lib/mysql/hostname.err using command

        Code:
        tail -100 /var/lib/mysql/hostname.err
        post output here in [CODE][/CODE] tags

        3. If the result of first step shows contenttype storage engine = MyISAM, then proceed with below mysqlcheck commands to repair it





        step 1. backup database using mysqldump to sql file using ssh2 telnet and mysqldump as outlined here http://www.vbulletin.com/docs/html/m...nce_ssh_backup

        step 2. To repair such corruption log into server using ssh telnet as root user preferably try using mysqlcheck http://dev.mysql.com/doc/refman/5.1/en/mysqlcheck.html

        1. check database tables

        mysqlcheck -s -u mysqlusername -p vbforumdbname

        ignore session and cp session table messages and on mysql 5.1.x, ignore errors related to mysql.general_log and mysql.slow_log they don't support mysqlcheck.

        2. repair table

        mysqlcheck -r -q -u mysqlusername -p vbforumdbname


        3. recheck database tables

        mysqlcheck -s -u mysqlusername -p vbforumdbname

        if still get corruption errors that aren't related to vB session tables, then run

        mysqlcheck -r -u mysqlusername -p vbforumdbname

        if you want to do one table at a time then add tablename(s) to end of commandline

        i.e.

        mysqlcheck -s -u mysqlusername -p vbforumdbname tablename1 tablename2 tablename3
        :: Always Back Up Forum Database + Attachments BEFORE upgrading !
        :: Nginx SPDY SSL - World Flags Demo [video results]
        :: vBulletin hacked forums: Clean Up Guide for VPS/Dedicated hosting users [ vbulletin.com blog summary ]

        Comment

        widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
        Working...
        X