The MU forums have moved to WordPress.org

Persistent SQL conenctions kill the server (5 posts)

  1. Farms2
    Member
    Posted 15 years ago #

    Hmmm... so am struggling with persistent SQL connections at the moment on one server with quite a few accounts on it.

    What's happening is that we're getting a maxing of connections (I've set the server max to 40 for any one account) and a staying there which only seems to be cured by restarting apache.

    There is absolutely no way that there are 40 people concurrently accessing a v. small site like eslblogs.org.

    And cache is on for them too.

    Also, in the error log we find: "maximum number of internal redirects reached"

    So - I have a look around and was wondering if WPMU is sending some infinite loops out and if reducing loops like from 10 to this:

    RewriteOptions maxredirect=3

    Might help.

    (taken from here: http://www.sitepoint.com/print/mod_rewrite-no-endless-loops)

    Any ideas how to knock off these connections / stop them from destroying teh server?

    Cheers, James

  2. kingler
    Member
    Posted 15 years ago #

    Are you talking about two problems here?

    "maximum number of internal redirects reached" error is an Apache problem, right? But why are you complaining about MySQL as well? Any error log from MySQL?

  3. Farms2
    Member
    Posted 15 years ago #

    Nope - just generally stuffed :(

  4. drmike
    Member
    Posted 15 years ago #

    max_connections to 40 or max_user_connections to 40?

  5. kingler
    Member
    Posted 15 years ago #

    You can check the Apache error.log along with the access.log, and you will be able to find when this maximum redirects happened, and the file Apache is trying to serve.

About this Topic