Hot News Portal getting MySQL errors.

When attenpting to goto the site you get the following error: "Error displaying the error page: Application Instantiation Error: Could not connect to MySQL."

I went to support on our website host and got the following response:

----START OF RESPONSE ----

I was able to duplicate the issue with the website at freespeechamerica.org/ I have uploaded a test database connection script at freespeechamerica.org/db.php and it's giving below error.

Could not connect: User kabram1 already has more than 'max_user_connections' active connections

The error you are receiving in your website is because your database user ' kabram1' has reached the limit of concurrent MySQL user connections which is set to 10. This limit cannot be raised on our shared platform. I would recommend checking with the documentation of the application you are using, as you may have an option of disabling persistent MySQL connections. You can also modify the queries/connection strings and disable all the plugins/components that you're using if any to avoid reaching the maximum limit. The biggest cause of this MySQL connection error is from poorly written code or applications that do not close the connection once the MySQL query or command has been ran.

----END OF RESPONSE ----

Other than normal articles, the only other thing we added was an article with a YouTube video using the "insert video" button. It didn't work right, so we took it off and replaced it with a picture of the video screen and a link to the video.

I don't know what is causing this and what to do to fix it.

I appreciate the help.

You can see the non-site here: www.freespeechamerica.org . At least it should be there...

If you imported database you also need to change database parameters in configuration.php , database username and database password.

That had been done when you folks installed the template for me. The website was running fine for a few weeks before these alarms started to pop-up.

As explained in the hoster's reply, the MySQL queries have exceeded the allowable limit and they attribute the overrun as possibly due to a module that is not closing the query after it is used.

That was the basis for my question; is this possibly due to code in a module, an increase in traffic, or something else?

Do you have some table with more that 40000 records?

Based on the time we have been on-line I doubt there are that many records, but I will check to get the information.