Announcement

Collapse
No announcement yet.

NEXTRUN error on install

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

  • NEXTRUN error on install

    Got this on the blog install. Looks like it couldn't install the crons properly. Maybe they haven't tested it on a master/slave combination? That would be a type of error you'd see if it didn't replicate an insert query in time before a select.

    I uninstalled it. Should I disable replication during install?

    Database error in vBulletin 3.6.8:

    Invalid SQL:

    UPDATE cron
    SET nextrun = 1194145140
    WHERE cronid = 33 AND nextrun =;

    MySQL Error : 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 '' at line 3
    Error Number : 1064
    Date : Saturday, November 3rd 2007 @ 08:43:20 PM
    Script : *******/forum/admincp/plugin.php?do=productimport
    Referrer : *******/forum/admincp/plugin.php?do=productadd
    IP Address : 24.226.*****
    Username : *****
    Classname : vB_Database_Slave_MySQLi
    Last edited by bigsoccer tech; Sun 4th Nov '07, 10:21am.
    The BIG Network: Soccer - Aussie Rules - Cricket - Travel - Lacrosse - Music

  • #2
    Fill out a support ticket at:

    http://members.vbulletin.com/members...ontactform.php

    Please include a complete description of the problem and be sure to include the login info to your Admin CP, phpMyAdmin and FTP in the 'Sensitive Data' field.
    Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
    Change CKEditor Colors to Match Style (for 4.1.4 and above)

    Steve Machol Photography


    Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


    Comment


    • #3
      Unfortunately, I suspect I will be told there that I don't have a standard, out of the box, VB install and won't receive support. Am I incorrect?

      This is the offending part of the code (it's part of vb, not the blogs). Really there should be no reason for that "AND nextrun =..." part, cronid is the primary key. (Around line 182 of functions_cron.php)

      // save it
      $vbulletin->db->query_write("
      UPDATE " . TABLE_PREFIX . "cron
      SET nextrun = " . $nextrun . "
      WHERE cronid = " . intval($cronid) . " AND nextrun = " . $crondata['nextrun']
      );
      We are considering patching it like this:

      // save it
      $vbulletin->db->query_write("
      UPDATE " . TABLE_PREFIX . "cron
      SET nextrun = " . $nextrun . "
      WHERE cronid = " . intval($cronid)
      );
      From what I can tell it should be fine. Though I want to run it by vb first to make sure it won't break other things.
      The BIG Network: Soccer - Aussie Rules - Cricket - Travel - Lacrosse - Music

      Comment


      • #4
        Well it worked for others who are curious.
        The BIG Network: Soccer - Aussie Rules - Cricket - Travel - Lacrosse - Music

        Comment


        • #5
          I think this error is caused by replicating servers. My host set up a http://nocache.forum.com (passworded) access to bypass the replication and only when I tried an install of a product via this did it work.
          Ultimately then this is a vBulletin issue.
          Stuart Wright, founder AVForums.com. [strike]13[/strike] 15 million posts and counting.
          vBulletin user from 2001. We stopped upgrading vB at 3.8.2 and sadly we're going no further.

          Comment


          • #6
            this error is still there
            regards
            Jens

            Open Source: TGS CMS (vB-Content-Bridge) / Planet 3DNow! / Change prefixes with AJAX

            Comment

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