Announcement

Collapse
No announcement yet.

SQL error after upgrade to 5.6.3

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

  • craigyb
    replied
    I have not seen the error since replacing this file.
    thanks

    Leave a comment:


  • Wayne Luke
    commented on 's reply
    Thank you for the update.

  • OrganForum
    commented on 's reply
    Just wanted to report that there has been no reoccurrence of this error since applying the patch 9 days ago.

  • OrganForum
    commented on 's reply
    So replaced. Will report back if error re-occurs.

  • Wayne Luke
    replied
    Please replace the /core/packages/vbdbsearch/db/mysql/querydefs.php file with the one attached to the topic. Let me know if the issue continues.
    Attached Files

    Leave a comment:


  • Wayne Luke
    replied
    The issue appears to be related to this: https://tracker.vbulletin.com/vbulle...sues/VBV-20258

    It is being investigated.

    Leave a comment:


  • craigyb
    replied
    Originally posted by Wayne Luke View Post
    Do any vBulletin files show as modified when you run the suspect file diagnostic under Maintenance -> Diagnostics.
    Nothing appears updated after I upgraded, so i would have overwritten all the files at that time.

    Leave a comment:


  • Wayne Luke
    replied
    I asked the developers to take a look.

    Leave a comment:


  • OrganForum
    replied
    I've seen this error twice since upgrading to 5.6.3. Diagnostic scan is clean.
    Code:
    Database error in vBulletin 5.6.3:
    
    Invalid SQL:
    
    SELECT DISTINCT CASE WHEN starter.nodeid IN (13,656370,715474,731877,645988) OR starter.parentid in (13,656370,715474,731877,645988)
    THEN starter.nodeid ELSE node.lastcontentid END AS nodeid
    FROM vb_node as node
    
    
    JOIN vb_closure AS closure ON node.nodeid = closure.child
    WHERE node.starter = node.nodeid AND
    node.contenttypeid <> 21 AND
    node.showpublished = 1 AND
    closure.parent = '44' AND
    node.nodeid <> closure.parent AND
    node.inlist = 1 AND
    node.protected <> '1' AND
    node.lastcontent >= 1596030483
    AND (node.public_preview = 1 OR ( ( ( (node.parentid IN (1,2,29,30,34,41,42,43,46,54,55,80,87,88,89,90,92,729108,3,17,32,35,39,47,18,49,51,6,25,36 ,23,31,59,12,24,33,16,19,40,44,73,81,93,21,14,45,60,78,94,48,57,58,95,74,50,96,98,99,100,1 01,38,102,37,97,103,104) ) AND node.showapproved > 0 AND node.viewperms > 1 AND node.showpublished > 0 )) OR ( node.nodeid IN (13,656370,715474,731877,645988) OR node.parentid IN (13,656370,715474,731877,645988) ) OR node.parentid = 9 AND node.userid IN (0)))
    
    
    ORDER BY node.lastcontent DESC
    LIMIT 500
    
    /**getSearchResults**/;
    
    MySQL Error : Unknown column 'starter.nodeid' in 'field list'
    Error Number : 1054
    Request Date : Saturday, August 29th 2020 @ 06:48:03 AM
    Error Date : Saturday, August 29th 2020 @ 06:48:03 AM
    Script : https://organforum.com/forums/activity/get
    Referrer : https://organforum.com/forums/forum/...ity-stream-tab
    IP Address : 71.32.140.166
    Username : Guest
    Classname : vB_Database_MySQLi
    MySQL Version :

    Leave a comment:


  • craigyb
    replied
    Originally posted by Wayne Luke View Post
    None of those files should be considered legitimate and should be deleted from your server. Adminer is spelled Adminer not admeener.
    It is Adminer they just changed the name of the file to admeener.php probably to evade detection.
    When i acesss the file it was adminer with a database login page.
    Yes i deleted them right away but just noticed them today.

    Leave a comment:


  • Wayne Luke
    replied
    Do any vBulletin files show as modified when you run the suspect file diagnostic under Maintenance -> Diagnostics.

    Leave a comment:


  • Wayne Luke
    replied
    None of those files should be considered legitimate and should be deleted from your server. Adminer is spelled Adminer not admeener.

    Leave a comment:


  • craigyb
    replied
    I now see they installed adminer on both my forums as of August 14, I assume that is related to the patch.
    May be related to this problem. I have only upgraded my slower forum.

    admeener.php File not recognized as part of vBulletin
    config.sample.php File not recognized as part of vBulletin
    license.php File not recognized as part of vBulletin
    widjet.php File not recognized as part of vBulletin

    Leave a comment:


  • craigyb
    started a topic SQL error after upgrade to 5.6.3

    SQL error after upgrade to 5.6.3

    After upgrading from 5.6.2 pl1 to 5.6.3, I am getting this sql error regularly.
    I am on PHP 7.3 and Maria DB 10.3

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

    Database error in vBulletin 5.6.3:

    Invalid SQL:

    SELECT DISTINCT CASE WHEN starter.nodeid IN (27,23) OR starter.parentid in (27,23)
    THEN starter.nodeid ELSE node.lastcontentid END AS nodeid
    FROM node as node


    JOIN closure AS closure ON node.nodeid = closure.child
    WHERE node.starter = node.nodeid AND
    node.contenttypeid <> 29 AND
    node.showpublished = 1 AND
    closure.parent = '22' AND
    node.nodeid <> closure.parent AND
    node.inlist = 1 AND
    node.protected <> '1' AND
    node.lastcontent >= 1596194843
    AND (node.public_preview = 1 OR ( ( ( (node.parentid IN (13,1,2,22,29,30,34,43,45,47,3,8,20,28,33,36,38,46,48,18,31,39,41,6,24,25,17,26,32,12,19,1 5,762778,915140) ) AND node.showapproved > 0 AND node.viewperms > 1 AND node.showpublished > 0 ))
    OR ( node.nodeid IN (27,23) OR node.parentid IN (27,23) )
    OR node.parentid = 9 AND node.userid IN (0)))


    ORDER BY node.lastcontent DESC
    LIMIT 500

    /**getSearchResults**/;

    MySQL Error : Unknown column 'starter.nodeid' in 'field list'
    Error Number : 1054
    Request Date : Monday, August 31st 2020 @ 11:27:23 AM
    Error Date : Monday, August 31st 2020 @ 11:27:23 AM
    Script : https://theforums.com/board/activity/get
    Referrer : https://theforums.com/board/forum/me...ity-stream-tab

Related Topics

Collapse

Working...
X