Announcement

Collapse
No announcement yet.

Fatal error: vBulletin datastore cache incomplete or corrupt

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

  • [Forum] Fatal error: vBulletin datastore cache incomplete or corrupt

    We're about to migrate to a new server, running vB 4.2 PL3 with php 5.4 and Xcache 2.1. I was working on some last minute tweaks to our installed themes. I ran the repair/optimize table command from the AdminCP, and now I get these errors:
    Code:
    vBulletin datastore error caused by one or more of the following:
    You may have uploaded vBulletin files without also running the vBulletin upgrade script. If you have not run the upgrade script, do so now.
    The datastore cache may have been corrupted. Run Rebuild Bitfields from tools.php, which you can upload from the do_not_upload folder of the vBulletin package.
    
    Fatal error: vBulletin datastore cache incomplete or corrupt in [path]/includes/init.php on line 252
    I followed the instructions and uploaded tools.php to the admincp folder and ran the bitfields cache script. However rather than fixing the problem, it returns a different error message:
    Code:
    fatal error: The requested language does not exist, reset via tools.php. in [path]/includes/class_core.php on line 4020
    Again, I followed the steps outlined in the error message and tried resetting the language, but all it does is return a database error, as though it can't find the language.xml file (which is in the install folder, where it's supposed to be). I've tried replacing the language file with a new one, but it doesn't yield any different results. I've also tried running the upgrade.php script from the install folder, however this too fails with errors. As a last resort I did an optimize/repair on the database through the command line, but all that did was cause the return of the original datastore cache error message. As an aside, I've disabled all plugins via config.php, and reset vBulletin back to using the vb_file_datastore cache, instead of xcache, but that hasn't made one iota of difference. At this point I feel like I'm going in circles.

  • #2
    Dont use 5.4.x, roll back to 5.3.x latest for starters, then report back.
    Gentoo Geek

    Comment


    • #3
      Snakes, I've been running 5.4 in this same test environment for over 2 months now, without incident. I did have to modify 1 or 2 core files, all solutions I found by searching the forums here. php 5.4 works fine, it's faster than 5.3, and it's been out for more than long enough to be considered stable and mainstream. A Google search on the error messages regarding tools.php and the datastore cache issue returned results from the vbulletin.com support forums dating back as far as 2010, but none of them provide any answers.

      Comment


      • #4
        ok, good luck.
        Gentoo Geek

        Comment


        • #5
          That's not much to go on. I'd happily roll back to 5.3 if I had any confidence it would fix the problem. But there's no evidence so far that 5.4 is the cause. I would really appreciate some guidance for better troubleshooting the source of the problem.

          Comment


          • #6
            In your /includes/config.php file, what is listed for "$config['Datastore']['class']" or is that commented out (which is the default)?

            Also, if it seems to be missing that language.xml file, I'd suggest reuploading all the default files.

            Please don't PM or VM me for support - I only help out in the threads.
            vBulletin Manual & vBulletin 4.0 Code Documentation (API)
            Want help modifying your vbulletin forum? Head on over to vbulletin.org
            If I post CSS and you don't know where it goes, throw it into the additional.css template.

            W3Schools <- awesome site for html/css help

            Comment


            • #7
              Curios as to what database errors you were getting and when.

              Comment


              • #8
                Lynne, I had "$config['Datastore']['class']" commented out. I had installed Xcache with the intent of using it, however when these problems began I changed the datastore class value back to the default: "vB_Datastore_Filecache". Joe, the database error I mentioned was the generic one you'd get if MySQL lost the connection to the requested database. However I've consulted the error log, and December 27 is where the trouble starts. I'm seeing these same messages over and over again:
                Code:
                [27-Dec-2012 22:02:54 America/Montreal] PHP Strict Standards:  Non-static method vB_Bitfield_Builder::save() should not be called statically in /home/user/public_html/forums/tools.php on line 495[27-Dec-2012 22:02:54 America/Montreal] PHP Strict Standards:  Non-static method vB_Bitfield_Builder::init() should not be called statically in /home/user/public_html/forums/includes/class_bitfield_builder.php on line 276
                [27-Dec-2012 22:10:19 America/Montreal] PHP Strict Standards:  Declaration of vB_Database_Alter_MySQL::drop_index() should be compatible with vB_Database_Alter::drop_index() in /home/user/public_html/forums/includes/class_dbalter.php on line 882
                [27-Dec-2012 22:10:19 America/Montreal] PHP Strict Standards:  Declaration of vB_Database_Alter_MySQL::drop_index() should be compatible with vB_Database_Alter::drop_index() in /home/user/public_html/forums/includes/class_dbalter.php on line 882
                [27-Dec-2012 22:11:03 America/Montreal] PHP Strict Standards:  Declaration of vB_Database_Alter_MySQL::add_index() should be compatible with vB_Database_Alter::add_index() in /home/user/public_html/forums/includes/class_dbalter.php on line 882

                Comment


                • #9
                  I've now reinstalled php 5.3, but no fix. I guess I'll have to replace my files, too.

                  Comment


                  • #10
                    Leave the files, re-install xcache 2.x.x series now & report back.
                    Gentoo Geek

                    Comment

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