Upgraded to 5.7.5 now error

**glennrocksvb** · Sun 24 Sep '23, 8:42pm

"MySQL server has gone away" is a common MySQL error. There are a lot of topics posted about this here. Here's few of them:

Random "MySQL Server Has Gone Away" Errors - vBulletin Community Forum

https://forum.vbulletin.com/forum/vbulletin-5-connect/support-issues-questions/4483586-random-mysql-server-has-gone-away-errors

Since upgrading to 5.7.5, I've been getting DBError messages several times a day, and the timing/velocity doesn't seem to indicate anything like a Cron job or a backup failing. Tonight, I went ahead and ran the MyISAM -> InnoDB script as well as the UTF8mb4 conversion, and after that I still was getting some while

mySQL server has gone away - queries that take too long? - vBulletin Community Forum

https://forum.vbulletin.com/forum/vbulletin-5-connect/vbulletin-5-installations/4479003-mysql-server-has-gone-away-queries-that-take-too-long

Since upgrading to vBulletin v5.7.2 I have noticed a big jump in the number of database errors. I get an email each time mysql fails. The apparent failure inducing URL hangs the board for a few seconds while it fails. 2 large log files are also generated for each error, so I run out of disk space each week, and the host freezes

MySQL Error : MySQL server has gone away Error Number : 2006 - vBulletin Community Forum

https://forum.vbulletin.com/forum/vbulletin-5-connect/support-issues-questions/4408927-mysql-error-mysql-server-has-gone-away-error-number-2006

I've seen this a few times in the last 2 months. I've restarted the db, but has since returned. Thoughts? Invalid SQL: /** saveDbCache */ SELECT * FROM vb3cacheevent WHERE cacheid IN ('node_494069_lvl1data'); MySQL Error : MySQL server has gone away Error Number : 2006 Request Date : Monday, February 18th 2019 @ 04:30:48 AM

Lot of database errors since upgrade to 5.2.3 MySQL server has gone away - vBulletin Community Forum

https://forum.vbulletin.com/forum/vbulletin-5-connect/support-issues-questions/4350357-lot-of-database-errors-since-upgrade-to-5-2-3-mysql-server-has-gone-away

Immediately after the upgrade to 5.2.3 I started getting a dozen of these errors per day. They stopped for a bit, started up again now. I'd like to think it's just

**Wayne Luke** · Mon 25 Sep '23, 9:46am

Originally posted by GoHighVoltage

MySQL Error : MySQL server has gone away

I've experience this on large site upgrades because of the system cache. Though your site doesn't fit the large site profile, it may have the same issue.

Run these queries against the database and run the upgrade steps again.

Code:

truncate table cache;
truncate table cacheevent;

**UKCobra** · Wed 27 Sep '23, 3:41am

I have the same issue. Went from 5.6.9 on Saturday to the latest 5.7.5 with Security Patch.

Now I am getting these errors consistently throughout the day. My forum is very quiet, and not what I would expect to be considered large.
I have not yet run the code suggested above as I would not know where to do that.

What upgrade steps need to be run again ? The whole upgrade ? Why ?

**Wayne Luke** · Wed 27 Sep '23, 9:18am

The system won't run a "whole upgrade". It will run the final upgrade steps to rebuild internal caches (i.e datastore) plus rebuild your templates and language phrases. The upgrade system is smart enough to run these steps every time you run it unless it sees that new versions have been added since the last upgrade.

Doing it this way is a lot quicker than going into the AdminCP and editing a language and save it, then editing a style and saving it, then editing a usergroup and saving it, editing a page of options and saving it, etc… It is also a lot easier for customers to implement than using the individual steps in tools.php.

**UKCobra** · Thu 28 Sep '23, 2:40am

I will try the upgrade again, it does require my hosting company to increase the resources available to me, as in the past the upgrade would time out and not complete.

**Wayne Luke** · Thu 28 Sep '23, 9:44am

Run it from the command line. It will have less overhead and use fewer resources. It will also not be subjected to HTTP based timeouts or access limits. Plus it does the job a lot faster due to this.

Code:

cd /path/to/vbulletin/core/install
php upgrade.php

**UKCobra** · Thu 28 Sep '23, 10:17am

I am not able to run it from the command line as it is a shared hosting service, so I have to do it from the browser.

**Wayne Luke** · Thu 28 Sep '23, 11:14am

Really?

Most shared hosting services in the US still provide command line access. Either through a web-based terminal or SSH. I figured it was that way everywhere. Especially with RSA-Key verification available.

**UKCobra** · Sun 1 Oct '23, 8:47am

Upgrade run again. Still got the error. I ran the commands first, although it said there were no rows to process (I think)

Still getting this error :

Database error in vBulletin 5.7.5:

Invalid SQL:

(SELECT nodeid, oldid, starter, routeid
FROM node
WHERE oldid IN (437788) AND oldcontenttypeid IN (1))
UNION
(SELECT t.nodeid, t.postid as oldid, n.starter, n.routeid
FROM thread_post t
INNER JOIN node n ON n.nodeid = t.nodeid
WHERE t.postid IN (437788))

/**fetchLegacyPostIds**/;

MySQL Error : MySQL server has gone away
Error Number : 2006
Request Date : Sunday, October 1st 2023 @ 08:23:09 AM
Error Date : Sunday, October 1st 2023 @ 08:23:42 AM

**Wayne Luke** · Sun 1 Oct '23, 12:39pm

If you wait for the time out to clear and start the upgrade again, it should pick up exactly where it left off. Ugly but should let you get through the upgrade eventually.

You can also try smaller batches but that will extend upgrade time, not shorten it. To use smaller batches edit the [var]/core/install/upgrade_options.php file. Find this line: 'masterslider' => 1.0, and change it to 'masterslider' => 0.5,.

Finally, a professional upgrade will allow a tech to download a copy of your database and run it in a local environment from the command line. The upgraded database will then be restored on the server either by us or your hosting provider. Though future upgrades may have similar problems on you server.

**UKCobra** · Mon 2 Oct '23, 6:33am

Thanks for the reply.
I did this at 8am on Sunday. It was quiet, and the upgrade completed in about 10 minutes, much faster than going from 5.6.9.
The point being this :
I ran the commands as suggested, but I don't think they had any impact.
The upgraded completed without any issues.
I still get the errors.

When looking at the IP addresses and the timings, I do not think these are genuine users, but bots. The IP's tend to be outside of the UK (We are a UK based car club, with few overseas members).
I suspect that whatever they are doing is creating this.
Last night I was getting 2 of these issues per hour.

I really need help to stop these issues that have started occurring since the upgrade to 5.7.5 as a result of the Security Vulnerability I made you aware of.
Regards
Mark

**UKCobra** · Mon 2 Oct '23, 8:36am

The three failures I had around 2pm this afternoon, were all from Microsoft IP addresses and in the UK. So my suspicion is some sort of search engine bot is causing a load that the SQL Server under 5.7.5 is not able to cope with.

**Wayne Luke** · Mon 2 Oct '23, 9:22am

Well its a server configuration issue. If you are still getting the error then the server is still timing out on that node. What is the content of node 437788

Code:

select * from node where nodeid=437788;
select * from text where nodeid=437788;

How much memory do you have allocated to PHP in the PHP.ini file?

**eolesen** · Mon 2 Oct '23, 2:54pm

My multiple "SQL Server went away" problems stopped after I disabled caching on my site, but I also started blocking bots heavily in both Robots.txt as well adding deny rules to my .htaccess file.

Server's been up for three weeks without an issue now.

Might be a coincidence, or it might just be the consequence of high bot activity hitting the site and causing an inordinately large cache that eventually collapses MySQL...

Upgraded to 5.7.5 now error

Upgraded to 5.7.5 now error

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment