Repeated SQL Errors

Avatar
  • Answered
Over the past few months, I have been having recurring errors when trying to connect to my forums. I run IP.Board 3.2.3 and at least once a week I receive the following error when trying to access the forum:

SQL Error
An error occurred with the SQL server:
[There is a white box below the above that presumably would typically include an error message but never does for me. I believe this might be an issue with the forum software.]
This is not an error with IP.Board but rather with your SQL server. Please contact your host and copy the message shown above.

After the error apparently resolved itself and I was able to connect to the forums and access the ACP to view the SQL Error Log, it revealed that it was an Error 1040: Too Many Connections.

About a year ago, I received a Large Account Move Notification. It was suggested that if I were able to delete some files, I might not need to move. By the time I replied to the message about ten hours after I received it and said I would try to reduce the number of files, the move had already been completed. I don't know if the two are related, and I cannot recall if I got similar error messages before the move.

I would assume based the SQL error that my account has some sort of cap that we've been inadvertently exceeding. What are my options to lift the cap and stop this error from occurring, aside from (or in addition to) reducing traffic? In researching this particular error, it has been suggested that I might need to upgrade to VPS and that the error is caused by a cap on the amount of CPU we're taking up on the shared server. Is this the case? If so, why was I not contacted directly about this issue?

My annual renewal date is coming up, and I would like to know what my best option is for reducing the frequency of this error and my forum's downtime as a result of the error before I decide how to proceed.
Avatar
Scott
Hello elletu, Thank you for your question on Repeated SQL Errors. The max_connections variable is a global setting for all our shared servers. It allows up to 30 simultaneous connections per user. Since the setting is the same on all servers, the fact you began getting it after the move is likely a coincidence of timing. It is rare for that error to occur, but is possible. Usually it is due to an inefficiency in a db connection script in the particular application. Our Tier 2/Systems team can help evaluate and see what specifically is causing the issue. You will want to contact them as soon as possible when the incident occurs. It does not need to be occurring at the time of contact, but as soon after as possible so the server logs are a little easier to go through. To do so, you would need to contact our Live Support department at [email protected] with that request. Be sure to validate your account with either the last 4 digits of the credit card on file, or the current Account Management Panel (AMP) password. Best Regards, Scott M