Not signed in (Sign In)

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

General Support: Plogger cannot connect to the database because: Too many connections

Bottom of Page

1 to 6 of 6

  1.  
    • CommentAuthorsergeglass
    • CommentTimeFeb 26th 2009
     
    I'm getting this error message on my index page to my site. I have Plogger on my index page. Another user commented about this same message. His problem went away. Could have been a mySQL server problem. Any ideas?
    •  
      CommentAuthorkimparsell
    • CommentTimeFeb 26th 2009
     
    Yes, that is a MySQL server error. You should contact your webhost and see what their limit is for database connections.
    • CommentAuthorsergeglass
    • CommentTimeFeb 26th 2009
     
    Hi there kimparsell. They said that I had exceed the limit of 10 concurrent db connections. My site is still down. Any advice to help me help my provider to reset?
    •  
      CommentAuthorsidtheduck
    • CommentTimeFeb 27th 2009 edited
     
    sergeglass,

    I would recommend you trying out the latest SVN code. My guess is that your server has a long timeout setting for sql connections (typical default is usually 8 hours) but a very limited amount of concurrent connections (10 vs. the typical default of 100). The previous code did not close the mysql connection at the end of each page, so the same connection would be available for a user multiple times during their visit to your page. However, if you have a long timeout setting, the connection remains active for however long your server is set to leave it open once that user leaves their session (again, this is set to 8 hours most likely). Where your server differs is the maximum connections of 10 concurrent connections (default is typically 100 concurrent connections), so it will only allow 10 people to connect to your site during the course of the timeout period (so in the default situation, it would be 10 visitors within an 8 hour period).

    The new code in the SVN closes the sql connection at the end of each page. This saves on your concurrent connections, but it takes a little bit more time as a new sql connection is created at the beginning of the code. You probably won't notice the extra time (possibly just a very few milliseconds), so it should work for you. Please let us know if this issue persists.

    Also, keep in mind that if you have a lot of traffic to your site, you may want to switch webhosts. Right now, you are limited to 10 people looking at your site at the same time. If that is fine with you, then you're golden. If not, you may want to look elsewhere for a host.
    Thankful People: sergeglass
    • CommentAuthorsergeglass
    • CommentTimeFeb 27th 2009
     
    Thanks sidtheduck for taking the time to write your advice. That was very helpful. It will take me a few days to get to this, but I'll keep you informed. The 10 concurrent issue and your explanation is most interesting!
    • CommentAuthorsergeglass
    • CommentTimeFeb 27th 2009
     
    My site is now back in all its glory -- just like kimparsell's experience.

    I'm checking on changing the concurrent default up from the measly 10. And it sounds as if I still need to install the SVN code. Thanks to kimparsell and sidtheduck for being here! Nice.

1 to 6 of 6

  1.