Issue: vw_proxy error after installing Version 4.0.23 Patch Level 1

Issue Tools
- View Changes

August 23, 2018 10:02 AM

Rick

New Member

vw_proxy error after installing Version 4.0.23 Patch Level 1

Every night at 8:12 PM it seems a cron job runs and creates this error

I have been getting this error every night at 8:12 PM
According to the task scheduler this is running /vault/helper/vb/cron/cleanup.php

Database error in vBulletin 4.2.5:

Invalid SQL:
SELECT * FROM `vw_proxy` WHERE dateline < 1534378322 ORDER BY proxyid ASC LIMIT 5000;

MySQL Error : Table 'flight_fsvb.vw_proxy' doesn't exist
Error Number : 1146
Request Date : Wednesday, August 22nd 2018 @ 08:12:13 PM
Error Date : Wednesday, August 22nd 2018 @ 08:12:13 PM
Script : http://SITE/vbfs/wiki_ajax.php?c=deferred
Referrer : https://SITE/content.php?1
IP Address : 142.112.225.91
Username : w9641432
Classname : vB_Database_MySQLi
MySQL Version :
Server : 198.50.213.69
User Agent :

Stack Trace:

#0 vB_Database->halt() called in [path]/includes/class_core.php on line 1395
#1 vB_Database_MySQLi->execute_query() called in [path]/includes/class_core.php on line 461
#2 vB_Database->query_read() called in [path]/vault/core/controller/db/vb3.php on line 283
#3 vw_DB_Controller_vB3->query_read() called in [path]/vault/core/model/db/mysql/vw.php on line 27
#4 vw_DB_MySQL_Model->select() called in [path]/vault/core/model/cron/cleanup/vw.php on line 543
#5 vw_Cron_Cleanup_Model->clean_proxied_images() called in [path]/vault/core/model/cron/deferred/cleanup/vw.php on line 52
#6 vw_Cron_Deferred_Cleanup_Model->run() called in [path]/vault/core/model/cron/deferred/vw.php on line 85
#7 vw_Cron_Deferred_Model->exec() called in [path]/vault/core/controller/ui/ajax/deferred/vw.php on line 23
#8 vw_UI_AJAX_Deferred_Controller->execute() called in [path]/wiki_ajax.php on line 54

Issue Details

Issue Number 5459

Issue Type Bug

Project VaultWiki 4.x Series

Category Install / Upgrade

Status Duplicate

Priority 2 - Fatal / Database Errors

Affected Version Unknown

Fixed Version (none)

Milestone (none)

Software DependencyAny

License TypePaid

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

August 23, 2018 11:21 AM
pegasus

VaultWiki Team
I believe this to be damage from this bug, which was fixed in 2016, but the leftover effects are still being noticed now: https://www.vaultwiki.org/issues/4489/

In order for this error to occur, the upgrade from 4.0.0 to 4.0.1 would need to skip the first 5 steps, and you would have needed to perform the upgrade using any upgrader included in 4.0.8 or earlier. Based on the 2016 bug, the first 6 steps of the upgrade were probably skipped. This suggests there is further damage than what you have already noticed (especially if other upgrades were performed before 4.0.9). As mentioned in that report, damage from a bug is not considered to be a separate bug, so this report is being marked as a duplicate.

To repair this damage, you must create the table manually via MySQL:

Code:

CREATE TABLE vw_proxy ( proxyid INT UNSIGNED AUTO_INCREMENT, challenge VARCHAR(40) NOT NULL DEFAULT '', mime VARCHAR(8) NOT NULL DEFAULT '', visible INT(1) UNSIGNED NOT NULL DEFAULT '0', dateline INT UNSIGNED NOT NULL DEFAULT '0', url BLOB NULL, PRIMARY KEY (proxyid), INDEX challenge (challenge) )

In light of this, I would recommend that you request Ticket Support perform an audit of your database to check for other inconsistencies (and repair them).
Reply

+ Reply

All times are GMT -4. The time now is 2:43 AM.

This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Learn more… Accept Remind me later

Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

Issue: vw_proxy error after installing Version 4.0.23 Patch Level 1

Issue Tools