MYSQL has gone away.

to a better place no doubt.

[txbakers]

But that doesn't help my users any.

I looked through the mysql manual for help on this and it doesn't seem to help.

I thought it was max_connections, which was set to about 1500, so I raised it up to 5000. I did a reboot and it went back to default, when I remembered - duh - to put it in the ini file on startup.

so I rebooted and the max_connections was set to 2800, not the 5000. So I made it 5600 in the ini file for next reboot. Perhaps it needs to be a multiple....

The timeout suggested by the manual just doesn't make sense. We have a very robust app, and each screen makes a connection when it loads. So the timeout doesn't make sense in this case.

What other stuff have you found that would cause this, and what ultimately fixes this?

Thanks all.

[coopster]

What OS are you running and how are you connecting? Are you using ODBC?

[txbakers]

Windows 2003 Server
It's a direct ConnectionString rather than ODBC. (DSNless)

I *think* the problem isn't with mySQL at all, rather it might be the IIS crashing and causing that message. I have a post in the IIS forums as well for that problem.

This morning it "went away" again so rather than reboot the machine I rebooted the MYSQL service, which didn't fix the issue. So I rebooted the WWW service and that DID fix it.

Odd, eh?

[txbakers]

OK, I'm convinced it's definitely an IIS problem , not sql.

It just happened again, and instead of rebooting the SQL service, I only rebooted the IIS service and it fixed the problem.

SO something is corrupting the IIS.