Results 1 to 8 of 8
  1. #1
    Join Date
    Aug 2007
    Location
    Slovakia and Arizona
    Posts
    5

    apache2 - many "sending reply" slots

    We are using Apache 2.2 prefork on Debian GNU/Linux.

    Sometimes it happen to us that we have really lot of apache processes (slots) in state "sending reply". This is not freed for several hours. Server status looks like:



    The question is how it is possible that some apache process can be locked to one client for several hours. Other clients are being served by free slots, however what if we will have used all the slots and not freed them?

  2. #2
    Join Date
    Aug 2007
    Location
    Slovakia and Arizona
    Posts
    5
    for those who think that my post does not make sence - than yes, you are right, I had to snip half of the text, since forum software did not allow me to post that (even if I turned off "Automatically parse links in text"; I definitely did not mean to post any smiles, URLs or what)

  3. #3
    Join Date
    Jan 2006
    Location
    Athens, Greece
    Posts
    1,481
    Should be KeepAlive On (persistent connections)

  4. #4
    Join Date
    Apr 2007
    Location
    Everywhere
    Posts
    273
    What's your current httpd.conf settings? Timeout,maxclients,keepalive and what's your server spec's. I guess it needs optimizing.

    Thanks

  5. #5
    Join Date
    Aug 2007
    Location
    Slovakia and Arizona
    Posts
    5
    Keep alive is something different than locked apache2 process sending still ONE reply for several hours.

  6. #6
    Join Date
    Aug 2007
    Location
    Slovakia and Arizona
    Posts
    5
    Quote Originally Posted by Sys Admin View Post
    What's your current httpd.conf settings? Timeout,maxclients,keepalive and what's your server spec's. I guess it needs optimizing.
    Timeout 600
    ServerLimit 280
    MaxClients 280
    KeepAliveTimeout 7

    I do not see any place for optimizing, since any from these params most-likely does not influence behaviour I described in my original post.

  7. #7
    Join Date
    Oct 2004
    Location
    Kerala, India
    Posts
    4,771
    The question is how it is possible that some apache process can be locked to one client for several hours
    You mean some apache threads must be exclusively allocated for a certain Ip?
    David | www.cliffsupport.com
    Affordable Server Management Solutions sales AT cliffsupport DOT com
    CliffWebManager | Access WHM from iPhone and Android

  8. #8
    Try to search via google you will fine lots of related articles

    about me, I prefer apache1
    it's more stable
    www.alrutani.com
    Alrutani Web Hosting

    Find your self in alrutani web hosting
    It's more then a host, it's a network of minds !!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •