VB 5.1.9 Stuck on last step

[William Thomas Jr]

Says,

Status: Processing XML, Step 20 of 20

Then,
final Step #20
Fatal Error Occurred
MySQL server has gone away on /home/xxx/public_html/core/vb/db/query/update.php : 120

The site from I can tell is operating fine though?

[Mark.B]

MySQL server has gone away

This is a server error, and you should contact your host.

Ask your host to increase the max_packet_size to 16MB and the wait_timeout to at least 30 seconds.

[William Thomas Jr]

Host says the settings were already:

max_allowed_packet=16M
wait_timeout=50

I reran the upgrade script:
Upgrading to 5.1.9
Status: Processing XML, Step 20 of 20

A box appears which says:
Action Required
Unexpected Text:
<?xml version="1.0" encoding="UTF-8"?>

[Mark.B]

It's still a server error, your hosts should help you to get it solved. There's nothing we can do from the vBulletin side of things.

[William Thomas Jr]

Please clarify. I have upgraded Vbulletin throughout the last six updates and never had an issue. This upgrade hangs on step 20. Here's a screen shot, while I appreciate your help in communicating what I need to convey to my host.

Here's the result of the last upgrade which started from step 20 and right before being aborted. Last question, what happens if step 20 is not completed?

[William Thomas Jr]

Had the host increase to:

max_allowed_packet=64M
wait_timeout=60

Same error: Fatal Error Occurred
MySQL server has gone away on /home/xxx/public_html/core/vb/db/query/update.php : 120

I noticed in the Tracker there is an issue: http://tracker.vbulletin.com/browse/VBV-14672

Is this related, though I am on a cloud server, and haven't any upgrade errors in previous upgrades.

Thanks
William

[Mark.B]

Put the site into debug mode (both config files) then log into the admincp and set css to be stored inline.

Then run the upgrade script again.

[William Thomas Jr]

Put the site into debug mode (both config files) then log into the admincp and set css to be stored inline.

Then run the upgrade script again.

Done:

Debug Information

Page ID: 1
Parent ID: 0
Page Template ID: 1
Route ID: 4
Page Type: default
Screen Layout ID: 2
Screen Layout Template: screenlayout_display_wide_narrow
Channel ID: 1
Node ID:
Database Asserts: 228 (?)
AJAX Requests: 4
Facebook Active: No (Not enabled or no appid & secret set)
Style ID: 23
Templates/Renders: 39/141
CSS Templates: 9
JS Files: 7
Current Time: Wed, 26 Aug 2015 12:26:08 -0500


Fatal error: Uncaught exception 'Exception' with message 'invalid_query_parameters for saveDbCache' in /home/religio9/public_html/core/vb/db/query/method.php:170 Stack trace: #0 /home/religio9/public_html/core/vb/db/assertor.php(283): vB_dB_Query_Method->execSQL() #1 /home/religio9/public_html/core/vb/cache/db.php(384): vB_dB_Assertor->assertQuery('saveDbCache', Array) #2 [internal function]: vB_Cache_Db->shutdown() #3 /home/religio9/public_html/core/vb/shutdown.php(91): call_user_func(Array) #4 /home/religio9/public_html/core/vb/vb.php(459): vB_Shutdown->shutdown() #5 [internal function]: vB::shutdown() #6 {main} thrown in /home/religio9/public_html/core/vb/db/query/method.php on line 170

[William Thomas Jr]

Now I can't remove the Fatal errors on the footer! I disabled the debug mode but it is still there!

[Mark.B]

Have you done all the steps I mentioned?

You need to set css to be inline, then run the upgrade script while in debug mode.

[William Thomas Jr]

Done. I set the css to be inline. If you meant to go to admin cp styles and languages and choose css as files?

Set the debug on two files to true

Ran upgrade.

Now I have errors reported on bottom of screen. www.christforums.org

[William Thomas Jr]

I'd like to forget this upgrade. I have reverted the debug config files. Deleted the install directory and clicked in admin cp to store css files as default.

I now have errors on the bottom of my page. How do I get rid of them?

https://www.christforums.org

[In Omnibus]

You need to turn off debug mode once you have followed the steps Mark gave you.

[William Thomas Jr]

Ya, I did that. The templates were messed up. I ended up restoring the site. I'll pass on this update.