With that error message, it's unfortunately very difficult to say what's going on. But, it's safe to say that it's not a problem with the hypervisor, as we use MySQL connections extensively from our VDSes.
I agree. That is why I posted here to see if anyone else could try and help me figure this out. We love the responsiveness we get from NFO servers and their support so we are trying to run everything we have on NFO servers now.
Have you tested for packet loss between the VDS and your MySQL server?
Pinged from my server to the VDS for 25 minutes straight. Not one packets was dropped. I also checked my error log on the MySQL server. Nothing. Lastly, I did a tcpdump on port 3306 to see if any errors were being sent that were not being reported any way. Ran strings on the resulting output and there are no errors coming from the MySQL server at all.
Is the connection rate exactly the same before and now? If you are waiting longer between connections now, they might time out, and if there are far more, then extra threads might step on each others' toes if there are locking problems.
Yes. Server count has actually decreased from when we had it on the other box. Was 4 64 man and 2 32 man servers. Now it is just 2 and 2. Sometimes they work as expected. We get stats about 85% of the time. I would hate for it to miss someone that was hacking and now we don't have their GUID to ban them later on.
Can you think of any other troubleshooting steps that I could do. I'm really open to anything at this point because I'm not sure what else to try. Thanks in advance.