[Suite] Fatal error, my site is down. No response to ticket in 5 hours

[Microlight]

I have tried to upgrade my board and have got a fatal error. Now my board is down and I don't know what to do.

I posted a ticket and have not had a response to it in 5 hours.

I installed over my previous board. Then went to run the upgrade...

1 of 12 OK
2 of 12 OK

Failed at 8 of 12.

MySQL Error : Got a packet bigger than 'max_allowed_packet' bytes (then a load of gobbledygook)
Error Number : 1153
Request Date : Tuesday, December 22nd 2009 @ 03:03:40 PM
Error Date : Tuesday, December 22nd 2009 @ 03:03:41 PM
Script : http://www.microlightforum.com/insta...=8&startat=206
Referrer : http://www.microlightforum.com/insta...=8&startat=180
IP Address : 90.201.91.53
Username :
Classname : vB_Database

Please help me resolve this problem.

[mmcgann11]

Did you try restarting running the upgrade.php?

There's a glitch in some upgrades -- which showed up for me in RC2 and continues through Gold -- that causes a memory error. Rerunning domain.com/forums/install/upgrade.php seems to solve it.

I don't know if this is the same issue and it could send your server into a deep, dark hole of despair. Or it might work. Assuming your DB is backed up, though, it might be worth a shot if support doesn't get back to you.

[Microlight]

Thanks for the input, It was worth a shot. It just goes straight to the problem part again.

[zoglair]

If you have access to your mysql's ini file, you can try increasing that value (max_allowed_packet), as explained here.

[melbo]

Did you backup first?

I'd never have the nerve to test a milestone version update with known issues on anything other than a test site before going live.

[Trevor Hannant]

Support staff are working through tickets as fast as they can...

[argothiusz]

SSH via Putty - Locate mysql.ini (usually inside /usr/local/var/ I forgot where it was lol) - cd to the folder - vi mysql.ini - type this in max_allowed_packet=32M - Save and you are ready to go. If you don't have SSH access then ask your host to do it.

[Microlight]

Thanks for your replies. I've deleted the offending files and sorted it out.

[s0lidgr0und]

Support staff are working through tickets as fast as they can...

I can imagine. I don't envy you guys at all. Thanks for your hard work.

[s0lidgr0und]

Thanks for your replies. I've deleted the offending files and sorted it out.

That's the only way I was able to get through part of my upgrade, too.

[Hotpuppy]

You may to have to regress to pre-upgrade. I've seen documentation that you shouldn't re-run the changes to the database.

[s0lidgr0und]

Never seen that said and I've never had a problem re-running upgrade.php.

[mjp]

Thanks for the input, It was worth a shot. It just goes straight to the problem part again.

I had to run one upgrade four or five times before the memory error was skipped. It seems like a bigger problem on a shared server, but if you're patient you can get around it without editing php.ini.